Start a mission from a Slack thread and get back a verified pull request

SHIP plans, builds, reviews and tests the change a Slack thread describes. You get a pull request that passed your CI.

For: Engineering teams that discuss bugs and requests in Slack and want a tested pull request back.
Instead of: A bot that opens a draft and leaves every check to you.

Runs today: Linear and GitHub Issues work today. Assign the issue in Linear, or comment @SHIP on a GitHub issue. From a terminal, ship delegate plan builds from a spec you wrote.

Join the early-access list Read the ways of working

Answer 4 questions. SHIP emails you when it opens to you.

How it works

Move a thread to a pull request in three steps

Step 1

Connect Slack and GitHub

Authorize your Slack workspace and install the SHIP GitHub App on your repositories. A project pins one Slack channel and one repository.

Step 2

Describe the work in the thread

Write what done looks like as a checklist in the thread. The Tester checks the change against it on a preview.

Step 3

Mention SHIP in the thread

Tag SHIP in the thread. The plan, the review verdict and the test result come back as replies while the mission runs.

Capabilities

Get more than a status update in the thread

Plan before any code exists

The Planner reads the thread and the repository and writes a plan. A checkpoint can hold the mission until you approve it.

Gate every change on your CI

A failed check goes back to the Builder with its logs. The pull request reaches you only after your CI passes.

Review with a second agent

A Reviewer that did not write the code reads the diff against the plan. It lists the fixes it requires and the ones it only suggests.

Report status back in the thread

Every stage posts its status as a reply in the same thread, from the plan to the finished pull request.

Evidence

Check the loop on 260 missions

In the SWE-in-a-team study, 260 missions went through the loop that early access brings to Slack. The loop sent 46 runs back and corrected 40 of them without a person.

Read the SWE-in-a-team study

Comparison

Compare SHIP with the agents Slack already starts

What each product's own pages say. Last reviewed October 15, 2026. Check the vendor's page before you buy.
Claude Code in Slack	Starts a cloud coding session when you invite it to a channel and mention it with a task. It posts status in the thread and can open a pull request when the session finishes. Claude Code in Slack
Claude Tag	Runs the same assistant for a whole organization on a Team or Enterprise plan. A bug reported in the channel comes back as a draft pull request from an ephemeral sandbox. Claude Tag overview
SHIP	In early access Takes the thread's request through a Planner, your CI, a Reviewer and a Tester before the pull request reaches you. Posts the plan, the review verdict and the proof from the test back in the thread. Generally available Runs each role on the harness and model you choose, on your own provider keys. Schema

FAQ

Frequently asked questions

Is SHIP for Slack available today?

Not yet. Slack is in early access, and SHIP works with Linear and GitHub Issues today. A team can start a mission from a terminal with ship delegate plan and a spec file.

Ways of working

When is Claude Code in Slack or Claude Tag the better fit?

They fit a team that wants a bot to post status in a thread and open a draft pull request by hand. SHIP fits a team that wants the plan, CI, review and a preview test done first.

Which coding agents does SHIP run?

SHIP runs claude-code, codex, pi, kilo-code and open-code. You set the harness and the model for each role in ship.yml, on your own provider keys.

Schema

What happens when I join the early-access list?

You answer four questions about your team and the coding agent you use. SHIP emails you when the Slack integration opens to your team.

Join early access for Slack

Join the list, and get your first Slack thread back as a verified pull request.

Join the early-access list

Answer 4 questions. SHIP emails you when it opens to you.