Chat-based control for Claude Code, Codex, and OpenCode: run sessions on your machine, drive them from your phone (no terminal)

A practical comparison of Telegram/Slack bots vs browser UIs vs phone-first dashboards, and a workflow for approvals + follow-ups that doesn’t require SSH.

Based on
CLI
0.2.17
Preview ref
a2c45c8

A common pattern looks like this:

A session starts on a computer (Claude Code, Codex, OpenCode).

Then you step away from the keyboard.

And you want to do three actions from your phone, fast:

  • check whether it’s still running
  • answer anything it needs (approvals / questions)
  • send one follow-up instruction

A lot of people reach for SSH here.

It is the source of truth, after all.

But SSH on a phone turns into doing real terminal work on mobile, and that is a poor default.

So this guide is about the “no terminal” control plane options that actually exist today.

TL;DR

  1. Decide how much UI you need:
    • chat-only (Telegram/Slack): best for status + nudges
    • browser UI: better context, still light
    • phone-first dashboard: best for approvals + diffs + routing
  2. If you mostly need “is it stuck?” and “send one message”, chat bridges can be enough.
  3. If you need to approve risky actions or review changes, prefer a UI that can show the request in context.
  4. Happier is one option that works well when you want phone-first approvals and session-aware notifications (without living in SSH).

The problem

The reason “chat-based control” is appealing is not that people love Telegram.

It’s that chat has one killer feature:

it’s already on your phone, and it’s already good at notifications.

But chat is also low bandwidth.

It’s great for:

  • “what’s the status?”
  • “stop and summarize”
  • “continue with step 2”

It’s weak for:

  • reviewing diffs
  • browsing files
  • making careful approvals

So the real question is: what are you trying to do from your phone?

Common approaches and their trade-offs

  • SSH from phone: works, but it’s heavy.
  • Chat bots: great for status and nudges, but approvals often need more context than a chat message gives.
  • Browser UIs: better, but you still need correct routing (right machine, right session).

If you want a phone-native dashboard instead of a chat transcript, Happier is an open-source app that lets you run and orchestrate Claude Code, Codex, OpenCode and other agents cross-device, from your phone, desktop or the web.

Option A: chat bridges (Telegram / Slack)

This is the “lowest friction” approach.

You wire something up that can:

  • list sessions
  • show basic status
  • forward a message into a session

The trade-off is that rich workflows (approvals, diffs) become awkward quickly.

Option B: official browser remotes (when a provider has them)

For Claude Code, Remote Control is a real option.

This is closer to “a UI for the session” than “a bot”.

Trade-off: it’s provider-specific.

Option C: a phone-first dashboard (Happier)

If you want the phone workflow to be:

  • notifications bring you to the correct session
  • approvals are durable (you can review later)
  • you can keep going without guessing which machine/server you’re on

…then you want a dashboard, not a chat transcript.

If you’re new to Happier

If you haven’t seen Happier before: it’s an open-source companion app (mobile/web/desktop) for sessions like Claude Code, Codex, and OpenCode.

The workflow is: sessions run on your machine, and Happier is where you keep them moving from your phone without living in SSH.

Get set up:

A workflow that works (phone control loop)

1) Make “what needs attention” visible

The biggest win is not being able to send messages.

It’s knowing when you should.

In Happier, Inbox is the dedicated place for “things that need your attention” (approvals, permission/user-action requests), even across sessions.

2) Make notifications land you in the right session

When you tap a notification, the failure mode is landing on the wrong session/server.

Happier’s notification routing model is strict about:

  • opening the targeted session
  • switching server profiles if needed
  • avoiding auto-approving on unknown servers

3) Use chat as an input method, not as your only UI

A pattern that works well:

  • use chat for quick “nudge” messages
  • use a dashboard UI for approvals + review
mobilechatremoteclaudecodexopencodeworkflows
Last updated: 2026-10-26