Guides
Set up coding agents, harnesses and assistants to hand work to SHIP, step by step.
Latest
Connect GitHub's and Linear's MCP servers to your coding agents
Bind GitHub's MCP server with a scoped token and Linear's with an OAuth sign-in. Keep review and QA read-only, and see each call on the run.
MCP servers for coding agents: bind them once, keep the keys out of the sandbox
Give your planner, builder, reviewer and QA agents the MCP servers your repository already declares, with credentials that never enter the agent's sandbox.
Run the pi coding agent headless on real tickets, in a sandbox
Run the pi coding agent as SHIP's builder in an isolated sandbox, on an open-weight model through your own OpenRouter key, with review and QA around it.
Codex code review for Claude Code: set up a second-provider reviewer
Keep Claude Code on the builder and put Codex on the reviewer, in ship.yml or for one mission, so a second provider reads every diff before you do.
Claude Code on Linear: assign an issue, get a tested pull request
Assign a Linear issue to SHIP and Claude Code plans it, builds it, clears your CI, reviews it and tests it on a preview before the pull request reaches you.