Keep the reasonbeside the change.

A product decision becomes a Task. The Task becomes a branch. The branch comes back as a Change Request your team reviews with the decision one click away.

Join the open beta Explore Projects

One change at Morrow

A diff shows what changed.The Task remembers why.

Martin wants gift wrapping at checkout on morrow.shop. The decision, the work and the review stay linked, so nobody has to retell it at review time.

Tasks

The Task carries the context

Write the outcome, link the decision and pick the Project. Assign the Task to an agent and the Run starts with all three.

Library

Decisions worth keeping

A decision you will reuse is a Knowledge page with revisions. The review comment stays on the Task.

Agents

A builder and a reviewer, one job each

Each agent has its own instructions, its own Roles and its own history of Runs.

Threads

Steer while it runs

Reply in the Task's thread and the agent picks it up at its next step. You do not start over.

Projects

One repository, one branch per Task

A Project is bound to one GitHub repository. The agent pushes to a branch named after the Task, and the pull request appears on the Task as a Change Request.

A scoped change.On a machine you control.

Scope

The Run works in the Project's repository

The branch belongs to the Task and the Run gets the repository its Project is bound to. A change somewhere else needs its own Project and its own Task.

# MORR-22 in Project morrow.shop repository morrow/shop branch morr-22/gift-wrapping push to this branch publish needs Publish Change Requests

On your machine

Claude Code or Codex does the work

Agents run on a Work Machine you connect, under your own plan or API key. See how Claude Code and Codex fit in.

# Work Machine: studio-linux ready Claude Code ready Codex 2 / 5 running jobs

Review with evidence.Publish with proof.

The Change Request shows what GitHub and your hosting actually reported for the commit under review.

Checks

What your CI reported

The checks on the Change Request are the ones GitHub reports for the head commit. No checks reported is shown as exactly that.

Checks passed

Preview

The version you are looking at

A preview counts only when it was deployed from the commit under review. If the branch moves, approval is asked for again.

Preview ready

Publish

Published means running

After the merge the Change Request waits for a successful production deployment that contains it. Only then does it say Published.

Awaiting deployment

Before you assign the first change.

Does this replace GitHub?

No. Your code, pull requests and CI stay in GitHub. Autopilot connects through the GitHub App, binds a Project to one repository and shows each pull request as a Change Request on its Task.

Can an agent merge its own work?

If its Role in that Space holds Publish Change Requests, yes. With the seeded Roles a Member does. Give publish to the people who should decide. An agent without it asks, and the request waits for someone who has it. The approval is tied to the commit that was reviewed.

Does writing a decision start any coding?

No. Work starts when you assign a Task to an agent or mention the agent in a thread. A page in the Library is context, and nothing runs because of it.

Which coding agents can we use?

Claude Code and Codex, running on a Work Machine. Linux x64 works today, macOS is in progress and QUESTPIE Managed is available on request during the beta. Bring your AI explains the options.

Do we pay per developer or per agent?

No. Plans are per company with unlimited people and agents. It is free during the open beta, and plans start at $65 a month from launch. See pricing.

Ship the change with its reason.

Start with one bounded change your team can review. Free during the open beta.

Join the open beta Running Claude Code or Codex?