Skip to main content
For Claude Code, Codex and OpenCode sessions, the server keeps your last message to the agent and the agent’s latest reasoning, tool call or reply, for the local HTTP API and the phone app to show. A slash command shows as /name args. Signed in, the session’s name comes from what you asked the agent: see AI session titles.

Where they come from

The server reads them from the agent’s own conversation, on your machine, at most once a second while the terminal shows output:
  • What’s taken: your last typed message (and the agent’s latest entry, which the local API and the phone app show), each cut to its first line, at most 240 characters, without control characters.
  • What isn’t: tool output and subagents’ messages are never taken, and the agents’ own insertions (reminders, notifications, command output) are skipped.
  • Where it goes: to Rakumux’s own clients, like the rest of the session’s details: the local HTTP API and the phone app. It isn’t sent anywhere else, except that while you’re signed in with AI session titles on, your last message and the agent’s messages since are sent to name the session.
This needs a server that reads agents’ conversations. After an update, if the running server is older, Rakumux says it lacks “each agent’s latest output” and offers to restart it in place; sessions keep running.
Without the OpenCode plugin, two OpenCode sessions in one folder show the same conversation’s messages. Install it with rakumux-mcp opencode-plugin --install; see Activity hooks.