Documentation
Tracking and automation

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.

5 min read
Turn it on in Agent features

A pull request lives on GitHub, and the agent that wrote it lives in a conversation. Usually a person sits between them, copying review comments into a prompt and telling the agent when a check went red. In codecast every pull request in a connected repository has a page with its checks, reviews and threads, and the session that opened it stays attached as its shepherd. When a reviewer asks for changes or a check fails, that session wakes up, fixes it, pushes, and answers on the thread.

Issues work the same way. Connect Linear or GitHub Issues and each issue becomes a codecast task that stays in step with the original.

A pull request page in codecast
A pull request with its shepherd, linked sessions and task, checks, review and merge state.

Turn it on

  1. Open Settings, Integrations, connect GitHub and give the codecast app access to your repositories. Pull requests already open there come in when you connect.
  2. Open Agent features (under More in the sidebar), pick the computer your agents run on, and switch on Pull requests under Tracking & automation.
The Pull requests card in Agent features
Click How it works on the card for what it adds and a request to try.

Reviews with a verdict go out under your own GitHub name, so your account needs GitHub connected too. Without it, codecast says so and offers to connect, or you can review on github.com.

Ask for it

  • "Open a pull request for this and look after it until it merges."
  • "Review PR 482 and request changes if the migration is unsafe."
  • "Answer the open review threads on my pull request and resolve the ones you fixed."
  • "Why is CI red on the webhook retries PR? Fix it."
  • "Merge it once checks are green." (Agents never merge unless you ask.)

The pull request page

Open a pull request from a conversation, a task, or Code in the sidebar. The header shows its state, author and branches, the Shepherd line, and the sessions and tasks linked to it. Below that, Checks, Review, Merge, Open comments and Diff sit at a glance, above tabs for Conversation, Files, Commits and Checks. The arrow next to the number opens it on GitHub.

The top of a pull request page
Checks passed, one open comment, and the shepherd line above the four tabs.

Review it yourself

A review in codecast works like one on GitHub, and the result goes to GitHub:

  1. In Files, hover a line and press + to write a note. Choose Start a review to hold it, or Post now to send it straight away.
  2. Held notes are yours alone until you finish. A bar at the bottom of the page counts them: 2 notes not sent yet.
  3. Click Review (or press r). Your notes are listed, each linking back to its line. Add a summary, pick Comment, Approve or Request changes, and click Submit review.
The review panel with held notes and a verdict
Held notes, a summary and the verdict, ready to submit.

The review lands on GitHub as one review under your name, and the shepherd gets it as one message: your verdict, your summary and every note. When the agent answers a note, the note links to its reply. If the pull request has no shepherd yet, the same panel offers Send the notes to a session that worked on it.

GitHub doesn't let you approve or request changes on your own pull request; you can only comment.

The shepherd

The Shepherd line names the session that owns the pull request. Agents that open a pull request through codecast usually take this on themselves. On a pull request without one, click Assign a shepherd session and pick a session. Switch it between Wakes on changes and Paused on the same line.

The shepherd wakes for things that need the author's hands, and stays quiet otherwise:

What happens on the pull requestWakes the shepherd
A check failsYes
A reviewer requests changes, or leaves a review with commentsYes
Someone comments on a lineYes
The branch no longer merges cleanlyYes
The branch falls behind mainNo, it's only noted
Checks go green, new commits, a review is requestedNo

Comments from bots and from the pull request's own author don't wake it. When it wakes, the agent fixes what's outstanding in one pass, pushes to the same branch, replies on GitHub to each point it addressed and resolves those threads. It doesn't merge unless a person asked it to. When the pull request merges or closes, the shepherd is released.

On your phone

The iPhone app opens a pull request with its state, review decision, checks (failures first), reviews and the sessions that worked on it, so you can see where it stands away from your desk. The diff and line comments open on GitHub.

A pull request on the iPhone app
A pull request on the phone: the failing check first, then the reviews.

Issues as tasks

Under Settings, Integrations, the Linear and GitHub cards each have an Issues as tasks section. Click Import, pick a Linear team or project or a GitHub repository, and the codecast project its issues should go into. Each issue becomes a task with a link back to the original.

Issues as tasks on the GitHub integration card
One repository importing into a project, with its delegate label.
  • It stays in step both ways. Title, description, status, assignee and labels follow each other. A comment on the task posts on the issue, and marking the task done closes it. Priority syncs with Linear (GitHub issues have none).
  • Hand an issue to an agent from the tracker. Set a Delegate label (for example agent) or a Delegate assignee, and turn on Spawn a session on delegation. Labeling or assigning an issue that way starts a session on it, and the issue gets a comment linking to that session.
  • Issue text is the task, never instructions. Anyone who can open an issue can write text an agent will read, so agents do the work an issue describes but never let its text override their own rules.

When something is off

What you noticeWhat to do
A pull request has no page in codecastGive the codecast GitHub app access to that repository under Settings, Integrations
Submitting a review fails with a note about your GitHub accountConnect GitHub to your own codecast account, or review on github.com
The shepherd didn't react to a reviewCheck its line reads Wakes on changes, not Paused. Reviews from bots and from the author don't wake it
GitHub refuses a mergeThe branch is behind, conflicted or blocked by a rule. GitHub's reason is shown; ask the shepherd to update the branch
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.
Let Claude, Cursor and Codex read your codecast
Add codecast.sh/mcp to an agent that runs outside codecast, sign in once, and it reads your docs, tasks, plans, pages and sessions as you, read only.
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.
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.
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