Session Chat

One chat window for every agent session, on your phone too.

@agentik/session-chat by Agentik

chatsessionsdeveloper-tools
A finished session as a chat thread, with a reply that has bullet points, inline code and a markdown table, then a Done card and the composer belowThe same thread on a phone screen, with a compact header, the reply table, the Done card and the composer at the bottomThe new session dialog with the harness list open, showing Claude Code, OpenCode and other harnesses, above fields for model and accountThe sidebar filtered to two finished sessions, one from Claude Code and one from Codex, with recently used harness and model shortcuts aboveThe Stats tab beside the thread, listing the session's model, cost, turns, tool calls, duration and context usedThe notifications bell open over the sidebar, with two entries named after their sessions, "Export invoices to CSV" and "Add VAT and discounts to invoice-cli", each marked Done with how long ago

Your agents run in many harnesses, terminals and machines, and it is easy to lose track of them. Session Chat puts every session on your daemon in one chat window.

From your phone

Session Chat installs as a web app on your phone. Open it over the daemon's remote tunnel to read a session, answer the agent or send a new prompt from anywhere.

Any harness, one place

Start a session with the harness, model, account and location you pick: this machine or a sandbox. The sidebar follows sessions from every harness, such as Claude Code, Codex and OpenCode, so you read them all the same way.

What each session costs

Open the Stats tab on a session to see its model, cost, turns, tool calls and how much of the context window is used. Token counts show up when the harness reports them.

Know when work finishes

The bell lists what happened on your daemon: sessions that finished or failed, pull requests opened and merged, and push checks that passed or failed. You get notified without keeping a terminal open.

Pick who pays

Choose the account for each session when you start it, so a job runs on the subscription or API key you want it to use.

And more

  • Change posture and effort in the middle of a session.
  • Schedule sessions to run on their own.
  • Queue prompts while the agent is still working.
  • Approve or deny permission requests right in the thread.

Requirements

Session Chat talks to your local agentproto daemon. Its bundled agent runs on the mastra-agent adapter: install it first with agentproto install mastra-agent.

Screenshots

A finished session as a chat thread, with a reply that has bullet points, inline code and a markdown table, then a Done card and the composer belowThe same thread on a phone screen, with a compact header, the reply table, the Done card and the composer at the bottomThe new session dialog with the harness list open, showing Claude Code, OpenCode and other harnesses, above fields for model and accountThe sidebar filtered to two finished sessions, one from Claude Code and one from Codex, with recently used harness and model shortcuts aboveThe Stats tab beside the thread, listing the session's model, cost, turns, tool calls, duration and context usedThe notifications bell open over the sidebar, with two entries named after their sessions, "Export invoices to CSV" and "Add VAT and discounts to invoice-cli", each marked Done with how long ago