After the loop (not a sixth stage of the agentic development lifecycle) · run with
/ship.What goes in, what you type, what comes out
Ship takes an agent from “passes its checks” to “running for your users”. It opens the pull
request, writes the changelog, and asks you before it merges. After the merge it follows CI, and
once the agent is deployed it compares the agent’s new traces with the ones from before the
release.
- Only you can start it. Ship never runs on its own and is never started by another step.
- It asks before merging. Nothing is merged without your confirmation.
- It recommends, it never rolls back. When the watch finds a regression, you get the evidence and a recommendation. Rolling back stays your decision.
- The watch ends. It runs for 5 minutes after the deploy by default, then stops. Set the length
with
--watch <minutes>(at most 30), or skip it with--no-watch.
Before you start
- The latest Evaluate verdict is
pass(no failed critical or high-severity criterion), and it was run on the commit you are shipping. Otherwise/shiprefuses; there is no override. - The changes are on a branch pushed to your GitHub repository.
- The GitHub CLI is installed and signed in:
gh auth statusexits 0. Ship opens the pull request and follows CI withgh. - CI runs on pull requests. CI must be green before Ship asks to merge.
- A trace source is configured for the agent (see Supported integrations), so the watch can compare traces.