Documentation
Recall

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.

4 min read
Turn it on in Agent features

A new agent session usually knows only what you type into it. With Stable context on, it starts with a short list of what you and your team have been working on: recent sessions, each with its title, who ran it, where it stands (working, waiting on someone, done) and how it began. A fresh session can see that a teammate's agent is halfway through the same part of the code before it duplicates the work, and "pick up where we left off yesterday" works without explanation.

The list holds pointers to sessions, not the conversations themselves. When one matters, the agent opens it and reads the details, the same way it looks things up with Memory.

A conversation whose top line reads "Started with 15 session pointers from the team feed", opened to a row of session cards
The sessions a conversation started with. Each card opens that session.

Turn it on

  1. Open Settings (⌘,), then Agent Features under Machines, and pick the computer your agents run on.
  2. On the Stable context card under Context, pick how much it shares:
    • Solo: your 10 most recent sessions from the last 7 days.
    • Team: the team's 15 most recent sessions from the last 14 days.
    • Off: new sessions start without a list.
  3. Switch on All projects to draw the list from everything you work on, not only the folder the session starts in.
The Context section of Agent Features: the Stable context card with Solo, Team and Off and the All projects switch, beside the Memory card
Stable context sits under Context, beside Memory.

New sessions on that computer use the setting from then on. It works for Claude Code, Codex, Cursor, opencode and Grok sessions.

Solo keeps up to 10 sessions from the last week, Team up to 15 from the last two. A session you leave out gives its place to the next one.

Change it for one session

When you start a session from the app, the new session screen shows a Context line with the choice and how many sessions it will start with. Click it to see the cards. Pick Auto to follow the computer's setting, or Team, Solo or Off for this session only, and click the × on a card to leave that session out.

The new session screen with its Context line opened: an Auto, Team, Solo, Off choice above a row of session cards, each with an ×
The new session preview. Change the choice or drop a card before the session starts.

On the iPhone, the new session sheet has the same choice in its Context row.

The phone's new session sheet with its Context row
On the phone, tap Context to pick Auto, Team, Solo or Off.

See what a session started with

At the top of a conversation, a line reads Started with 15 session pointers from the team feed. Click it to open the cards: exactly what the agent knew when it began, each a link to that session. Sessions started with Stable context off have no line.

What changes

  • Fewer "what were we doing?" openings. Ask a fresh session what you worked on yesterday and it already knows.
  • Less duplicated work. An agent sees that another session is on the same thing and can read it first, or, with Messaging on, ask it directly.
  • Stuck work stands out. The list marks sessions waiting for input, so an agent can tell you when work it depends on is stalled.

Limits and privacy

  • Only sessions you can see. Team lists a teammate's sessions only when they are shared with the team; see Team sessions. Solo lists only yours.
  • It never holds a session up. If the list can't be fetched (you're offline, say), the session starts without it.
  • It is a snapshot of the moment the session started. Later work by other sessions reaches it only if the agent looks.

When something is off

What you noticeWhat to do
No Started with line on new sessionsCheck that Stable context isn't Off for the computer the session runs on
A teammate's work is missingPick Team, and check that their folder is shared with the team
The list is full of unrelated projectsSwitch All projects off so it sticks to the session's folder
One irrelevant session keeps showing upLeave it out with its × on the new session screen
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.
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.
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.
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