Documentation

Open the Command center (requires an account). Paste a product idea, roadmap request, spec, or product brief. Run the planner to generate tasks, risks, acceptance criteria, implementation prompts, and the first suggested PR sequence.

Each successful run saves the latest plan for your workspace so you can refresh without losing work. The MVP direction is to attach every plan to agent runner events: branches, PRs, QA results, blockers, and next actions.

Try ideas without an account in the public Sandbox (rate-limited per IP).

Use Timeline as the product operating view: idea scope, build lane, PR sequence, QA gates, blockers, cost guardrails, launch actions, and the latest visual preview of how the web/app is coming together.

The current UI includes a preview placeholder; production runners should attach real artifacts such as screenshots, deployment preview URLs, PR links, test output, and QA comments so the customer can verify progress without reading raw logs.

QA hub ties compliance-style checks to your workspace. Connect GitHub under Integrations so repo context and scans use your organization's OAuth token—not a shared server secret.

Use coaching and optional AI narrative to interpret findings; treat automated output as a draft and apply your team's standards before merging.

In Settings → Integrations, connect GitHub, validate your AI provider key, and pair a dedicated agent runner. Disconnect revokes stored credentials for that workspace. Tokens are encrypted at rest.

For the MVP, prefer a dedicated runner per workspace or a customer-hosted Mac mini/server. Do not share powerful tool access across tenants unless filesystem, secrets, network, and process execution are clearly isolated.

Invite colleagues from Members. Owners can rename the workspace, export data, transfer ownership, and review customer-owned setup readiness from Workspace.

Create scoped tokens under API tokens. Use them as Bearer on the REST API (e.g. execution analyze, latest plan, QA review—see scopes when creating a token).

Webhooks notify your systems when relevant events occur; store the signing secret safely—it is shown only once.

Enable two-factor authentication under Security. Update password and profile from Account.

Manage plan and invoices in Billing. Usage and budget controls for agent runs are under Usage and the immutable activity stream under Audit log.

The live execution snapshot is stored as JSON on the server filesystem or in S3 when PM_DATA_S3_BUCKET is configured. Without a shared bucket, a plan generated on your laptop is not the same file your production host reads—use the same storage configuration if you need parity across deploys.

Your database (users, workspaces, integrations, audit events) follows DATABASE_URL per environment.

• Prompter — agent-style prompt snippets
• Changelog — release notes
• ROI case — sample narrative
• Contact — sales or support requests
• Email: info@sprintpilot.xyz