Developer docs

One CLI. One portal. Everything on the record.

AutoDevOps records what AI coding agents do, gates risky actions behind policy and human approval, and keeps an auditable record in your own cloud. It ships as the verifier CLI (npm: @autodevops/verifier) plus the verification portal, the review surface where your team approves actions and exports evidence. These docs cover the surfaces that exist today.

Validated path

AWS Cloud + Amazon Bedrock

Data boundary

Customer-owned BYOC install

Capture model

Ingested events, not an LLM proxy

Start here

Install the CLI from npm, then wire it into the coding agents your team already uses. verifier harness plan shows exactly what would be written before anything is installed.

bash

npm install -g @autodevops/verifier

verifier harness plan --harness claude-code   # preview, no writes
verifier install --harness claude-code        # hooks + MCP registration
verifier harness doctor                       # verify the install receipt

Working from the monorepo instead?

The repository’s dry-run golden path proves the full loop with zero secrets configured: npm install && npm run platform:golden-path. It validates payload shape, provenance, redaction, and approval evidence without a live portal.

What this proves

The golden path emits a governed connector transcript with session.started, tool.started, approval.requested, hook.blocked, agent_run_audit.source_snapshot, and session.finished events. Live mode posts the same shape through portal ingest.

Docs map

Organized by what you're building, not by package name.

Golden path

Run the governed capability proof in dry-run or live portal mode.

Open

JS/TS connectors

Emit signed agent activity from internal agents and custom tools.

Open

Event schema

Canonical agent_activity.v1 examples and compatibility rules.

Open

Approval bridge

Request and poll portal approval for sensitive custom actions.

Open

Hook packs

Install provider-native lifecycle telemetry and enforced PreToolUse hooks.

Open

Private registry

Customer-owned registry for connectors, capabilities, policies, analyzers, and exporters.

Open

Plugins and manifests

Trust levels, permission manifests, and reviewable governed plugins.

Open

Provenance

How connector and capability metadata lands in sessions, approvals, audit, and exports.

Open

Commands and env

CLI commands, environment variables, and validation gates.

Open

What’s built today

Status for each surface, and where to start.

Surface	Current status	Developer path
Signed event ingest	Implemented for legacy verifier telemetry and generic `agent_activity.v1` events with automatic SDK-boundary secret redaction (cloud keys, tokens, JWTs, private keys) through the portal ingest endpoint.	Read the event schema
JS/TS connector helper	Implemented in `@autodevops/verifier-portal-client` with dry-run validation, signed posting, idempotency, SDK-boundary secret redaction, and provenance.	Build a connector
Portal approval bridge	Implemented for signed approval request/status polling. Governed actions fail closed when approval cannot be reached.	Wire approvals
Hook packs	Lifecycle telemetry for the Claude Code, Cursor, and Codex harnesses, plus opt-in enforced PreToolUse guards. Live customer walkthrough still pending.	Install hook packs
Cloud deployment	AWS + Bedrock is the validated path. Azure and GCP adapters exist in the codebase but are roadmap, not validated customer paths.	Read commands and env