Keep required review checks enforceable

Preserve required skills and checks for a fixed code snapshot; the server keeps incomplete review evidence from becoming a passing gate.

The effective contract preserves required team/template/project/repository constraints and pins complete bundles. Workflows exposes execution, review, automation, hook and per-account settings. Hook outbox records require durable controller acknowledgement; unknown Git configuration contexts require manual integration. Native vendor/model attestation is limited: strict policy blocks unknown identity. Agent-reported approval or claimed tool execution cannot replace trusted checks. External merge enforcement also needs repository required-status rules and an authorized publisher. Paid reviewer execution, root/Linux identity switching and native Windows automatic hook installation have not been verified.

How it works

  1. Open project Workflows

    Open Workflows from Projects or Sessions with Shift+W, or use the browser action.

  2. Configure and start work

    Choose accounts, hosts and limits, then start a task, request review or connect a tracker. CLI and scoped MCP tools expose the same operations.

  3. Keep live actions explicit

    Live actions require configured permissions, accounts and budgets; the demo only reads sample records.

  4. Review hook installation

    Automatic review hooks require a verified native local Git context. Ordinary global/system configuration, managed hosts and external hook managers require manual integration.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.