Sophon

iOS app

Sophon is the phone UI for agents you already run. The iOS app is not a marketplace and it does not host runtimes. It gives your connectors a native chat surface: sessions, streaming bubbles, tool cards, approvals, and durable history.

Chat list

Each paired connector appears as an installation in the app. You can pair multiple machines or runtimes under the same account:

  • Work Mac running OpenClaw.
  • Home Mac running another bridge.
  • A VPS running a custom connector.
  • A hosted service connected through your own bridge.

The chat list groups sessions by installation and shows the latest message snippet, health state, and pending approvals when relevant.

Sessions

A session is one chat thread with one installation. It has a title, message history, archived/deleted state, and live streaming state.

Sessions are scoped to an installation. A chat with your work-Mac OpenClaw is not silently moved to a different connector.

Streaming bubbles

When the user sends a message, the connector opens an agent bubble, then streams deltas into it. iOS renders:

  • the user bubble immediately,
  • a placeholder agent bubble while the runtime starts,
  • token deltas as they arrive,
  • final canonical text when the run completes.

If the app reconnects during a turn, Sophon replays recent events and reloads durable history so the bubble reconstructs.

Tool cards

Connectors can forward tool activity as tasks. iOS renders these as native cards inside the agent turn:

  • command or tool name,
  • arguments,
  • progress,
  • result or error,
  • collapsed summary for multiple tools.

Tool cards are not just live UI. They are persisted in the message so old chats still explain what the agent did.

Approvals

For risky actions, the connector can pause and ask the user:

  • Allow once.
  • Allow always.
  • Deny.

Approvals are part of the protocol, not a local-only UI trick. The user decision is sent back to the connector, which unblocks or denies the runtime.

What iOS does not do

  • It does not run your agent.
  • It does not store your model provider keys.
  • It does not expose local tools directly.
  • It does not decide whether an action is safe. The connector requests approval, and the user decides.

Read next