Under the hood
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.
3 min read
Codecast keeps a copy of your workspace on your own device: sessions, conversations you've opened, tasks, plans, docs and projects. Every screen draws from that copy first, then the server keeps it current in the background. That one choice is why the app behaves the way it does:
- It opens instantly. The inbox, your board and the conversations you've read appear straight away from what's already on your device, instead of a loading skeleton while the server answers. You see a skeleton only the very first time a screen has nothing stored yet.
- Your changes show the moment you make them. Mark a task done, move a session, rename a plan: the screen updates as you click, and the save goes to the server behind it. A slower answer from the server can't flip your change back.
- Nothing you do is lost to a bad connection. Changes you make while the connection is down are kept on your device and sent when it returns, even if you reload or close the window in between.
- Busy workspaces stay light. Only what changed travels to you. A team with hundreds of agent sessions sending updates every second doesn't resend your whole inbox each time.
Several windows, one picture
In the Mac app you may have the main window, a few tabs pulled out into their own windows, and the command palette open at once. One window does the syncing and the others share what it receives, so every window shows the same thing at the same time. A change you make in one window appears in the others right away, without waiting for the server. Close the window that was syncing and another takes over on its own.
The sync light
A small light in the header tells you whether what you see is current. Hover it for detail.
| The light | What it means |
|---|---|
| Green | Up to date. Everything on screen matches the server |
| Cyan, pulsing | Syncing the latest data. A screen is loading for the first time on this device |
| Amber, pulsing | Sync is slow. Catching up has taken more than about 20 seconds. Your changes are safe and will be sent |
| Amber, Reconnecting | The link to the server dropped. You're looking at your stored copy, and it will sync when the link returns |
| Offline | This device has no network. Everything you've opened before is still there to read, and changes wait until you're back online |
Coming back after hours or days away, the app catches up on just what changed while you were gone. After a long absence it rebuilds the stored copy quietly in the background, adding what's missing without emptying what you already see.
Who can see what
Your device only ever receives what you're allowed to read. A task kept private inside a team stays on its owner's devices, and when someone's access to something is removed, it disappears from their copy too.
When something is off
| What you notice | What to do |
|---|---|
| The light stays amber | Check your connection. If it's fine, reload the window; nothing you changed is lost |
| One window shows something different from another | Reload the window that looks stale. Windows normally agree within a moment |
| Something still looks wrong right after codecast updated | Reload once so the window runs the newest version |
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 feed 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 into one queue 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.