Coding agents

Setup by an agent, and four opt-in features that run a model.

Works

• An agent can run the setup and stops at a pull request; it never applies or approves
• A read-only MCP server over the estate, the audit trail and the delivery metrics, running no model
• Four opt-in features run a model, each off until you set it up with a model API key

Differs

• On GitLab the agent comment and drift fixes are refused, and the review runs through the comments schedule.

First step

Set up with a coding agent

You can count on

• A plan note on every pull request
• Gated applies of the plans you approved
• No overlapping or stale applies
• Re-plan from a comment
• Scheduled drift checks
• OIDC roles, one to plan, one to apply
• Policy on every plan
• An audit trail in your bucket
• Secrets kept out of notes and logs
• Your state backend, as is
• Your own runners
• Your forge's sign-in and permissions

Then read

Tasks

Agent changes to a pull requestAgent drift fixesModel review of a pull requestRefused wave summariesThe estate over MCP

Background

Architecture

Details

CLI commands