Score8.1
Popularity82.0
Risknone
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum8.0
Maturity8.1
Open-source/build8.4
Evidence7.2
Workflow potential9.6
Setup ease8.8
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers running Claude Code / Codex / OpenCode who want to reach their agent from a phone, a chat app, or a second laptop without exposing a tunnel to their machine. Install via the included docker compose, point your preferred chat bridge at the local API, and confirm the agent still runs the official CLI binary before adopting it for real work.
Who should use it
developers running Claude Code / Codex / OpenCode who want to reach their agent from a phone or a chat app without exposing a tunnelteams who want a uniform API across Claude Code, Codex, and OpenCode so they can switch backends without rewriting their workflowremote-first teams who want to monitor their agent's progress from Slack/Discord without RDP-ing into the laptopanyone who wants their agent to keep running locally instead of being uploaded to a third-party cloudusers in China/SEA who need a WeChat or Lark bridge alongside the usual Slack/Discord/Telegram
Who should skip it
Skip if the source link, docs, or setup requirements do not match your workflow.
Risk explanation
No inherent user-impacting risk is flagged from the captured evidence.
Evidence links
Closest alternatives / related signals
agent-oslocal-firstclaude-codecodexopencodebrowserslackdiscord