Documentation
PWR documentation
How PWR works today. Where something is implemented but not yet verified against a live service, the page says so.
Pre-launch documentation
These pages describe the current platform build. Status notes mark behavior that is still being verified.
Tutorials
Run your first task
Account, project, repository, agent, task, review.
From task to reviewed pull request
Branches, validation, the independent review and the merge gate.
Raise coverage on an existing codebase
Baseline, plan, generated tests, re-measure.
Execute a sprint with agents
Board, sprint, approved tickets, report.
Start here
- Getting startedWhat PWR is and the first-run path from account to a reviewed pull request, with an honest note on what is verified today.
- Account creationHow sign-in, organizations, members and the five membership roles work in PWR Studio, including current limitations.
- Billing and creditsHow PWR credits, plans, pre-flight estimates, budgets and top-ups work. All prices and credit values are drafts until launch.
Core
- PWR AutoHow PWR Auto routes each run to a third-party model by purpose, cost and context, and which providers are executable today.
- GitHub integrationInstall the PWR GitHub App, connect a repository, and follow a task from branch to pull request, review, approval and the merge gate.
- Workflow templatesThe PWR workflow library and agent roles, what each template actually launches, and which gates the platform enforces.
Game development
Project management
Quality
Reference
- Security and permissionsRoles, tenant isolation, credential encryption, run sandboxing, the tool gateway and approvals in PWR, with known residual risks.
- TroubleshootingError codes and workflow states you may see in PWR Studio, what each one means and what to do about it.
- FAQsShort, direct answers about what PWR does today, what is still unverified before launch, pricing, models, security and game engines.