Seats
Loading seat usage...
Loading plan details...
Organization
Invite members, change roles, and manage billing from the organization's profile. Solo supports one human. Team includes three humans and adds seats as the team grows.
Progress report
A windowed, org-scoped summary of runs, verdicts, agent-human agreement, findings, and flaky checks. Visible to owners and admins.
Open reportsOrganization admin workspace control
Start a fresh Signoff workspace
Archive and permanently lock every existing project and board, then make one new Signoff project the active default. Existing QA history, evidence, memberships, billing, and agent keys are preserved. Public forms and guest links attached to the archived work are disabled.
Prepared archive inventory
Manifest fingerprint:
The fresh workspace is active. Archived projects remain readable and immutable.
Open the fresh Signoff projectEmergency rollback
Rollback restores the prior active workspace and archives the replacement project. It does not delete anything.
MCP API keys
Your agent keys inherit exactly the boards you can access. A key is shown once at creation and cannot be recovered later.
Connect your agent
Use this MCP endpoint with an API key from below. Send the key as the X-Api-Key header.
Loading this deployment's MCP endpoint...
Add this to AGENTS.md or CLAUDE.md
This makes Signoff part of the project's definition of done.
Loading the current short agent instructions...
Install the Signoff QA planning skill
The skill teaches an agent to map product slices, focus on At Bat, and verify the matching real product surface: browser, app, device, public API, or CLI.
Set up Signoff on another agent
Paste this prompt into your existing AI system. It connects MCP, installs the skill, adds the short project trigger, and retires the old cadence hook if present.
Loading the setup prompt...
Planning companion
Pair Signoff with Ref
Use Ref for persistent implementation plans, comments, documentation research, agent handoff, and pull request progress. Signoff remains the source of truth for build-pinned QA, evidence, and verdicts.
Ref is an independent third-party service with its own account, API key, terms, and possible credit usage. Signoff never collects or proxies your Ref key.
Loading the Ref setup prompt...
Default code intelligence
Pair Signoff with RepoWise
Give coding agents local callers, dependency impact, git history, ownership, decisions, health, and change risk before they edit. Signoff history anchors the behavior, and real-product evidence still decides every verdict.
Telemetry disabled. The local-first setup requires no hosted indexing or LLM provider. RepoWise is independently maintained under AGPL-3.0; embedding it in a product requires separate licensing review.
Loading the RepoWise setup prompt...
Local infrastructure companion
Pair Signoff with WorkerBee
Give your AI a local cloud-native workbench while Signoff remains the source of truth for user-facing QA. The handoff covers macOS, Linux, WSL2, Codex, Kimi Code, and OpenCode.
WorkerBee branding is used from the open-source project under the Apache License 2.0.
Loading the WorkerBee setup prompt...
Compose your agent stack
Signoff + the pillars you choose
Choose the companions you want to use, then copy the configuration and short agent instructions. Build and verify a meaningful slice early, then repeat the feedback loop. WorkerBee establishes runtime facts; Signoff records relevant, current-build behavioral evidence. Agent evidence stays agent-attributed. Existing private-local configurations should be preserved.
Replace <SIGNOFF_API_KEY> (create one above) and <REF_API_KEY> (ref.tools/keys) after pasting.
Loading companion stack...
Loading companion stack...
Loading your agent keys...
Webhooks
Signoff POSTs run and finding events to these HTTPS endpoints, signed with an HMAC-SHA256 signature. A signing secret is shown once at creation and cannot be recovered later.
Checking webhook access...
Only org owners and admins can manage webhooks.