The Build tab
The Build tab is the last tab of a build packet, after Proposal, Design, Requirements and Tasks. It is where you start a build in your coding agent and then follow it: who is building, on which branch, which pull requests exist, and what was built. This page walks through the tab in each state, on the Mac and on iPhone.
The tab appears once the packet is Ready to build, and stays through Planned, Building, Built and Archived. It is not shown while Retain is still writing the design, or for a dropped packet.
Before a build starts
The heading reads "Build" followed by the packet's name and "in your coding agent". The tab shows what to type, ready to copy.
On the Mac:
- Choose the agent. A menu offers Claude Code or Codex. The Mac remembers your choice.
- Already in your agent. Copy the command and paste it into a session that has the repository open. For Claude Code it may be two lines when the packet's files are kept outside the repository, the first giving the agent access to that folder. Codex asks for that folder the first time it writes there.
- From Terminal. Copy a one-line command that changes into your repository's folder, starts the agent with access to the packet and asks it to apply the packet. Paste it into Terminal.
- Where things go. A note says which folder the build runs in, the one you connected for this repository, and where the packet's files are written. If no folder of the repository is connected on this Mac, it tells you to run the command from your checkout.
On iPhone the tab shows the command for each agent, each with a Copy button. There is no Terminal command, because a folder path means nothing on a phone. Paste the command into a coding session that has the repository open, such as a remote Claude Code session.
While it builds
The heading changes to "Keep building" and the start commands fold away under "How to start a build". Above them the tab shows what the agent has reported.
- Who is building. A green dot and a line such as "Claude Code is building this, on MacBook, 2 min ago" appear while the agent itself has reported in the last 10 minutes. After that the dot goes grey and the line reads "Last synced from MacBook" with how long ago. A push or sync from a terminal or the Mac app counts as a sync, not as building.
- Each build. The branch, with "No branch reported" when there isn't one, and the pull request it opened. The Mac lists the folder the build runs in as well.
- The session. A link back to the agent's session when it has one. Otherwise the tab shows the command that reopens it, which you can copy on the Mac.
- Progress. The count of tasks done, such as 6 of 25. On iPhone it sits under the packet's name with a bar.
More than one agent can build the same packet from different worktrees, and each appears as its own build.
Pull requests
The packet lists its pull requests with the number, the title and a state: Open, Draft, Merged with how long ago, Closed, or Not read yet. Each says how it was found: reported by a build, found by its branch or commit, suggested by Codex, or added by you.
A suggestion has a dashed border and a reason. Choose Confirm to keep it or Remove to drop it. Add links one at a time by pasting a pull request's address. On the Mac, opening the tab reads the status of pull requests that are not merged, at most every five minutes, and Find pull requests looks for ones the agent didn't report. If that finds none, Look harder with Codex asks Codex for suggestions to confirm.
Dependencies
When a packet builds on others, or others build on it, the tab adds "Depends on" and "Needed by" sections. They are read-only. See Dependencies and stacked pull requests.
After the build
Once every task is done the heading reads "Built" and the tab drops the start commands. It lists what was built:
- Built from one commit to another.
- How many files changed.
- How many tasks were left open, if any.
The packet's pull requests and the builds that made it follow. On the Mac an archived packet adds a line saying it is a read-only record of what was built.
To pick the next packet to build instead of opening one yourself, see Picking what's next.
Need help?
Can't find what you're looking for? Contact our support team for a quick reply.
Contact Support