Documentation
Working together

Use Codecast with OpenCode

Sessions you run in the OpenCode TUI appear in Codecast within seconds, with no plugin. Reply to them from the app, start new OpenCode sessions there, and search them beside every other agent you use.

4 min read

OpenCode is an open source coding agent that runs in your terminal. Codecast reads OpenCode's own session store, so a session you run in the OpenCode TUI shows up in Codecast with no plugin and no change to your OpenCode setup. From there you can read it, reply to it and search it from the desktop app, the web or your phone, beside every other agent you use.

We checked this on November 9, 2026 with OpenCode 1.18.31 on a Mac. The session appeared in Codecast two seconds after the first prompt was sent, and a follow up typed in the Codecast app ran in OpenCode and came back.

The OpenCode TUI: a request to add retry backoff to the webhook sender, the edit and a test run
A session in the OpenCode TUI.
The same session in Codecast: the request, OpenCode's reads, edit and commands, the diff and the answer
The same session in Codecast. Edits show as diffs, and each command opens to its output.

Set it up

  1. Install Codecast on the machine where you run OpenCode and sign in (Download).
  2. Keep using OpenCode as you do now.

There is nothing to install into OpenCode. The first time Codecast runs it also picks up the OpenCode sessions you ran before, so your history comes in too.

What shows up in Codecast

Each OpenCode session becomes one conversation in your inbox, under the folder it ran in, with an OpenCode badge and the model name in its header. Inside it you see your prompts, OpenCode's replies, its reasoning and every tool call: files read, edits drawn as diffs, and shell commands you can open to see the output. Codecast titles the session from what it was about, and the header counts the files it changed.

Reply from the app or your phone

Type in the message box at the bottom of an OpenCode conversation and Codecast delivers it to OpenCode on your machine. If no OpenCode process is attached to that session, Codecast starts one in the background, sends your message, and the reply streams back into the conversation.

An OpenCode conversation in Codecast with a second message sent from the app and OpenCode's edit in reply
The second message was typed in Codecast. OpenCode ran it on the laptop and answered within a minute.

An OpenCode TUI you still have open on that session does not redraw with turns sent from Codecast. Reopen the session there and they are all in it.

We sent the follow up above from the web app. The phone app sends messages the same way, but we have not tried it with OpenCode.

Start an OpenCode session from Codecast

Click New in the header and choose Session, pick the folder, and choose OpenCode in the agent menu under the message box. The model menu beside it offers OpenCode's default or a model you pick. Codecast starts OpenCode in that folder on the machine you choose and sends your first message.

The new session box with OpenCode chosen as the agent, the folder and the machine it will run on
OpenCode in the agent menu of a new session.

What you get on top of OpenCode

  • Every agent in one inbox. OpenCode sessions sit beside Claude Code, Codex, Cursor, Gemini, pi and Grok sessions, on every machine you use.
  • Search across all of it. Find the session where something was decided, whichever agent ran it. See Search sessions across machines.
  • Context from past sessions. A new OpenCode session can start with pointers to recent related sessions. Memory explains how agents read earlier work.
  • A link for any session. Share a whole session or a few messages with someone who does not use OpenCode. See Share a session.
  • Code traced to its conversation. Find which session wrote a line, including lines OpenCode wrote.
  • A team view when you want one. Share the repository with a Codecast team and teammates can read your OpenCode sessions at the level you choose. Team sessions covers the settings.

Fork, switch and hand off

The command palette on any session has Fork session as…, Switch agent… and Hand off to…, and OpenCode is one of the choices. Moving a Claude Code or Codex session to OpenCode creates a new OpenCode session in the same folder with the conversation so far, so OpenCode continues where the other agent stopped. Forking an OpenCode session uses OpenCode's own fork, which Codecast runs in the background when OpenCode is installed.

We have not tested fork, switch or hand off with OpenCode for this guide.

Requirements and limits

  • OpenCode 1.2 or newer. Those versions keep sessions in a SQLite database (~/.local/share/opencode/opencode.db), which Codecast reads without writing to and checks every two seconds. Older builds that stored sessions as JSON files are not read.
  • Codecast has to run on the machine where OpenCode runs. Sessions on another machine appear once Codecast is installed there too.
  • OpenCode keeps its own model and provider setup. Codecast does not hold your OpenCode keys.
More guides
Agent features: what your agents know how to do
Switch features on for each computer, and every new session there learns to remember, delegate, track work, show results and use your machine.
Memory: agents that look up past work
Your agents search every session you can see, across your machines, agents and team, and answer with the session they found it in.
Search your history across every machine
Every computer you connect sends its sessions to one history, searchable from the web, the Mac app and your iPhone.
See which agent session wrote a line
Set Blame to Sessions on any file to see the session behind each line, and open the conversation where it was decided.
Messaging between sessions
Your sessions hand each other results and answers directly, so you stop relaying text between them.
Stable context: sessions that know what's been happening
New sessions start with a short list of what you and your team worked on recently, so they pick up threads instead of starting cold.
See your whole team's agent sessions in one place
Every session your team runs, on every machine and agent, in one live Activity page and inbox, shared per folder.
Use Codecast with T3 Code
Threads you start in T3 Code appear in Codecast with no setup, beside every session you run anywhere else, ready to search, steer and share. What you get on top, and what stays in T3 Code.
Share a session with your team
Choose what the team sees of a session, share it by link or a few messages at a time, and how that compares to other tools.
Pinned thread state
The agent keeps one short note on each session saying where it stands, above the composer and on its inbox card.
Decisions: asking without interrupting
Agents put the calls only you can make on one Decisions page you clear when you choose to, and each answer goes back to the session that asked.
Team chat with your agents in the room
Channels, threads and DMs where you can hand a session or a role something by mentioning it, while agents stay quiet unless they're needed.
Huddles, transcripts and walkie
Every huddle is transcribed under each speaker's name and leaves a summary, so your agents can quote what was said, and a session can join the call.
Workers, forks and switching agents
Your agent can hand work to workers that report back to it, and you can fork a conversation to try two directions from the same point.
Tasks and plans
Agents file the work they take on, post progress and close it with what they verified, and you follow it on the Tasks and Plans pages.
Triggers
Agents schedule their own follow-ups, once, on a schedule or on a GitHub or Linear event, and you can set one yourself from the Triggers page.
Workflows
A fixed sequence of agent steps, checks and approval gates that runs the same way every time and waits for you where you want a say.
Orchestration
Hand an agent a whole plan and it runs a team: implementers working in parallel, a reviewer on every task and critics on the result.
Pull requests and issues
Every pull request gets a page with its checks and threads, the session that opened it fixes what reviewers and CI flag, and Linear or GitHub issues become tasks.
The org: roles that look after your work
Give lasting work to a role with an area, a charter and a standing session, and approve the changes your agents propose to the org.
Let agents use your Chrome
Agents check pages in the Chrome you already use, logins included, from their own background tabs. Screenshots and errors come back to the conversation.
Vault: keys, logins and sign-ins for your agents
Fill a credential once and every agent on every machine can use it, without the value ever entering a conversation.
Computer use: agents in your Mac apps
Agents work in Preview, Slack, System Settings or your own desktop build, in the background, with an orange pointer that shows where they act.
Typecheck: one shared check for every agent
With Typecheck on, agents on a computer share one typecheck per project, so checks answer in seconds and a busy machine stays usable.
Skills: slash commands for the jobs you repeat
Type / in a Claude Code session to pick up work, hand it over, get a second opinion or ship a pull request, the same careful way every time.
Run sessions on other machines and in the cloud
Start a session on another computer or a cloud machine in your AWS account, move it there and back, and watch it from anywhere.
Codex Cloud tasks in codecast
Bring your Codex Cloud tasks into your inbox, start new ones with several attempts, and turn the result into a pull request or local changes.
Usage limits are a pause
When a Claude plan runs out, sessions wait for the reset or continue on another account you've saved, instead of stopping for good.
The visual canvas
Agents answer with charts, comparisons and diagrams drawn right in the conversation when a picture says it better than text.
Published pages
Agents turn reports and mockups into pages with their own link that you can share, gate, and get comments on.
Why codecast feels instant, even offline
Everything you see comes from a copy on your device that the server keeps current, so screens open at once, your edits show immediately, and nothing is lost offline.
Taking longer than usualOffline · reloads when back