Operate Managent.

Setup

Invite emails contain a private install URL and license key. Node 22.13+ is required. The server binds to loopback by default; expose it through your own TLS-terminating proxy.

npm install -g "https://get.managent.tech/d/<token>/managent-latest.tgz"
mkdir managent-data && cd managent-data
managent init acme/webapp /path/to/local/clone
managent server

Integrations

The CLI wraps any agent command. MCP is the primary Claude Code path. The TypeScript SDK and GitHub Action use the same acquire → heartbeat → release lifecycle; Cursor, Codex, Devin, and Windsurf adapters are documented as invocation-boundary wrappers, not undocumented platform hooks.

export MANAGENT_API_URL=https://managent.example.com
export MANAGENT_API_KEY=mgt_live_...
managent run --repo acme/webapp --task "fix retries" \
  --paths src/billing/** -- claude -p "fix retries"

Migration

1. 1. Run one repository in observe/shadow mode and record current workflow boundaries.
2. 2. Gate one CI agent through a lease while keeping the rest of the workflow unchanged.
3. 3. Add MCP or SDK acquisition at each agent's file-editing boundary.
4. 4. Review queue wait, drift, and merge-replay evidence before expanding.

Rollback is operationally simple: stop invoking the wrapper/action and keep the server database for audit. Coordination is advisory plus drift detection and verification unless the optional git guard is enabled.

Security

API keys are hash-only and repository-scoped. GitHub ingress verifies HMAC-SHA256. OIDC, SAML, and SCIM are available for workspace identity, with provider secrets held in environment variables. Managent is not SOC 2 or ISO 27001 certified, and no third-party penetration test is claimed.

ROI evidence

The ROI endpoint reads observed pair and conflict counts from persisted, de-duplicated verification_runs. It also exposes queue wait and scope metrics from persisted tables. Dollar impact is not measured: the caller supplies a cost-per-conflict assumption, which is echoed and labeled in the response.

Counterfactual conflicts are an estimate produced by applying a baseline rate to observed pair count. Treat that baseline and the cost input as assumptions—not customer evidence. The persisted observed conflicts remain the auditable fact.

Troubleshooting

Empty dashboard

Run init and server from the same directory, or set one absolute MANAGENT_DB path.

Verification remains at zero

Confirm the configured local clone can resolve both PR refs. An unresolved ref is reported as a skip, never a clean replay.

Queued lease

Do not write yet. Inspect the territory map, wait for FIFO reassignment, or reduce scope through checked paths.

API reference

Generated from product/docs/openapi.yaml · Managent Coordination API v0.1.0. The source contract currently defines 15 operations; this page intentionally does not fill gaps from marketing copy.