Blog
How we run a fleet of coding agents, what we built to steer them, and what we learned along the way.
The task your agent reports to
A chat thread is a bad place to keep track of work. Codecast gives every piece of work a page of its own, where the agents working on it leave their notes, their evidence and their status, and where a plan gathers the tasks that belong together.
14 min readCodecast in the cloud
Every cloud feature, end to end: a host in your own AWS account that starts from your uncommitted work, carries your agent config and logins, mirrors its edits back to your laptop, takes whole batches of running sessions mid-flight, and sleeps when nothing is happening.
6 min readThe tree at the end of every turn
A transcript shows the edits an agent made with its editing tools. It never sees what a shell command, a formatter or a person changed. Codecast now records the whole working tree at the end of every turn, as git commits you can diff and rewind to.
4 min readThe codecast field manual: running a company of agents
The org your agents report into, the inbox that sorts them by who acts next, moving a live conversation from Claude to Codex without losing a word, and ten things only codecast does. Thirteen chapters, with the real product on every page.
7 min readFewer, bigger jumps
When you work with coding agents, tokens are cheap and your attention is not. Ask for a leap that lands near the goal, close the gap in shrinking corrections, and spend the time it buys on the next leap.
5 min readOne repository, twenty checkouts
Running several agents at once is easy until two of them edit the same file. Codecast gives each one its own worktree, with the env files, dependencies and a port of its own, from one switch when you start the session.
6 min readWhat your team sees
Sharing your Claude Code sessions with a team is a great idea right up to the session where you pasted a customer's data. Codecast answers with two dials, a preview before every share, and one settings page that shows the whole picture.
6 min readThe pull request that knows its sessions
When agents write most of the code, a pull request is the end of a conversation you were not in. Codecast keeps the two attached: every PR carries its checks, its reviews, and the sessions that made it, and a review can wake the agent that owns it.
6 min readAgents that talk to each other
A Claude Code agent shipped a change that silently stalled 27 transcripts. A Codex agent in the same checkout found it, fixed it, and told the first one. No human relayed a word.
5 min readA URL for everything your agent makes
Reports, dashboards, design proposals — agents produce them daily, and chat transcripts bury them. Codecast turns a file into a live page with versions, comments, and a link you can actually send.
5 min readThis post wrote itself (on a schedule)
Codecast triggers run full agent sessions on a timer. The proof is this blog: last week's post and this one were both written, unattended, by runs of the same weekly trigger.
5 min readYour agents forget. Your team doesn't have to.
Every agent session is a problem being solved out loud, and then the terminal closes. Codecast keeps the record searchable — so the next agent, or the next person, starts from the answer.
5 min readAn inbox for your agents
Agents don't fail loudly. They finish, or stall, and wait for you to notice. The inbox makes the waiting visible — every session, every machine, sorted by who needs you.
6 min readgit blame for AI agents
When an agent writes the line, the author column goes blank. Codecast's blame fills it back in, with the conversation that wrote it.