Wire an agent in about a minute.
GateBolt sits between your agent and your git history. You run one command; after that nothing is typed by hand again.
Quickstart
You need Node 20 or later, a git repository with an origin remote, and a GateBolt account. Install the CLI globally (npm i -g @gatebolt/cli) — the hooks GateBolt writes are committed to your repo, so gatebolt has to resolve on every machine that clones it.
init just wrote.Commands
| Command | What it does |
|---|---|
gatebolt init | Link the repo, wire the agent hooks, install the pre-push backstop |
gatebolt login | Browser-approved device flow; mints an org-scoped key |
gatebolt link | Link this repo only — writes .gatebolt |
gatebolt declare | Open a declaration of intent |
gatebolt observe | Derive the diff, reconcile it, seal the result |
HTTP API — custom agents
The CLI is a convenience, not a requirement. Anything that can make an HTTP request can write to the ledger. Authenticate with an org-scoped key (gbolt_…) as a bearer token; inputs and outputs are wrapped in a json envelope.
| Endpoint | Purpose |
|---|---|
POST /v1/trpc/repository.link | Find or create a repository |
POST /v1/trpc/change.declare | Open a declaration before editing |
POST /v1/trpc/change.observe | Submit the real diff, get the reconciliation |
Enforcement modes
Set GATEBOLT_ENFORCE, or pass init --enforce strict to write it into the tracked settings. lenient records and scores undeclared edits; strict blocks them at the hook before they reach disk.