Blog
Notes on agent memory, attribution, and steering coding agents at team scale.
- 6 min read
What 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 dry run, and one command that shows the whole picture.
Read - 6 min read
The 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.
Read - 6 min read
Agents 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.
Read - 5 min read
A URL for everything your agent makes
Reports, dashboards, design proposals — agents produce them daily, and chat transcripts bury them. cast publish turns a file into a live page with versions, comments, and a link you can actually send.
Read - 5 min read
This 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.
Read - 5 min read
Your 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.
Read - 5 min read
An 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.
Read - 6 min read
git blame for AI agents
When an agent writes the line, the author column goes blank. cast blame fills it back in — with the conversation that wrote it.
Read