Approval gates for Claude Code

The two default gates

A gate is a place where the pipeline waits for your approval. The default pipeline has these two gates, using the same buttons and hints as the Inbox:

before Plan

Request plan

Requesting lets dev write a plan. Then continue in your coding client. Nothing changes in the code yet.

before Implement

Approve implementation

Approving lets dev change code. Then continue in your coding client.

Opening a gate gives the session permission to continue. It does not run the agents on the server.

Edit a pipeline

The Pipeline tab lists named pipelines. Choose a default, route item types to a pipeline, or select a runnable pipeline when putting an item on the board.

Pro and Max can edit steps and gates, reuse a pipeline as a block, and repeat Doc audit or Scout steps. Repeated steps keep separate names, such as Doc audit #2 and Scout #2.

The expanded pipeline that runs an item must contain Plan → Implement → Accept exactly once in that order. A reusable block can contain only part of that sequence. Verify, Implementation check, and QA depend on your plan and chosen steps.

Saved changes apply to newly proposed items. An item already running keeps its execution version. The web can change a Proposed item's pipeline only while its run is still open and no agent has started work for that run.

Open gates in the Inbox or your session

The project must also be available for use. A disconnected or not selected project remains read only.

A session approval uses a separate owner token. Implementation approval from a session also requires a validation record and the exact plan commit being approved. The Inbox can approve without those two extra conditions. Both paths check the current gate and execution entry.

If an error says the gate approval was recorded but the next instruction could not be loaded, read the current pipeline state before trying again. Do not repeat the approval blindly.

Understand the owner connection and token permissions.

A pipeline can have no gates

With no gates, planning and implementation can start without your approval. Saving such a pipeline asks you to confirm that choice. Acceptance is still required; removing gates does not remove its checks or records.

Send back, hold, reopen, and discard remain web actions. Agents cannot add approval permissions to their own connection. See the other reasons a pipeline may wait.