Enable Two-Factor Authentication
In your authenticator app (Google Authenticator, Microsoft Authenticator, Authy, 1Password…), add an account → Enter a setup key using the key below, then enter the 6-digit code to confirm.
Setup key:
Creates GitHub issues from the current step's agent output (Epics, Features, or Stories).
Describe the problem — not the answer. The agents design the approach.
Code generated by the Developer Agent can be pushed to this repo. Set your PAT in 🐙 GitHub Settings (profile menu).
Add extra instructions injected before this agent runs. Leave blank to use the default system prompt.
Custom prompts are stored per-session and applied before the agent's standard instructions.
Create a public, read-only link to this run. Anyone with the link can view the idea and agent outputs — no sign-in needed. Costs, tokens, and account details are never shown. You can turn the link off anytime.
A multi-agentic, dynamic, and scalable workflow solution
Sign in to your account to continue.
Enter your username. If an email address is on file, a reset link will be sent.
Your account belongs to more than one organization. Select the one you want to sign in to.
Multi-Agent workflow from idea to production — with your approval at every step.
Scales the whole interface so you don't have to zoom in/out.
Preferences are saved on this device.
Select an agent on the left to view or edit its prompt.
Your Anthropic API key is encrypted with your password and stored locally.
Bring your own provider key. Your key is used (and billed) for sessions you start, taking priority over the org key. Keys are stored in Key Vault and never returned to the browser.
This context is injected into every agent prompt for your sessions. Use it to set your preferences, role, or organization-specific instructions.
Need a hand? Our IT team is here to help with access, billing, or technical questions.
Store your GitHub PAT to push generated code to a repository or trigger CI/CD deployments.
The target repository is set per session (in the New Session dialog). Your org's GitHub organization is set in Org Settings.
Context and GitHub repo for this session.
Injected into ALL agent prompts for every user and organization.
Export all users, orgs, sessions, and settings as an encrypted backup file. Only app admins can create or restore backups.
Verify outbound email is working. A test message will be sent to your address (or the address you specify).
| Name | ID | Max Jobs | Flags | Created | Actions |
|---|
Lowercase letters, digits, and hyphens only · 2–40 chars · e.g. acme-corp
| Name | Role | Status | Last Login | Actions |
|---|
New Organization Details
Lowercase letters, digits, hyphens · 2–40 chars
Copy this now — it will not be shown again.
Organizations pay $25 per seat / month (billed by active user, any size org). New orgs receive a 14-day free trial. Manage subscriptions below — clicking "Subscribe" opens a Stripe-hosted checkout page.
Loading billing status…
Decompose a completed session into parallelizable implementation slices and dispatch them as ephemeral workers. Requires PAD to be enabled for your org (Admin -> PAD).
Act as another organization. Your view, sessions, and admin scope follow the selected org until you return to your home org.
First, tell us about you.
12+ characters with upper & lower case, a number, and a symbol.
How do you want to get started?
Name your organization.
We sent you a verification link. Click it to activate your account and sign in.
🔐 After verifying, you'll set up two-factor authentication to secure your account.
📁 Don't see it? Check your Spam/Junk folder (it can take a minute to arrive). If it's there, mark it “Not junk” and add the sender to your contacts so future emails land in your inbox.
Injected into every agent prompt for users in your organization.
When users in this org create a new session, the repo owner field will be pre-populated with this value.
Number of unique approvers required before a gate auto-advances. Default is 1. Set higher to require multiple team members to approve each step.
| Username | Name | Role | Actions |
|---|
Designate which users can approve each agent gate. Users with no steps assigned cannot approve any gate. Org admins and app admins can always approve.
Loading…
Every organization runs a slightly different workflow. Add, remove, reorder, and edit the agents your org uses — the workflow adapts to whatever set you configure.
Open the editor to manage your org's Active and Standby agents, drag to reorder, and edit each agent's prompt.
Configure OIDC / SSO sign-in for your organization. Uses the browser-side implicit flow — no server required.
Turn a session — even one still in progress — into a client-ready proposal. Pick the source session, optionally add a focus, and the pitch agent drafts a roadshow-ready proposal in a single pass from whatever the session has produced so far — using your real ROI + live pricing.
No sessions yet — start a session first, then come back to pitch it (it doesn't need to be finished).
Creates a one-step proposal session from the selected source — it does not re-run the full pipeline.
Configure a webhook URL that receives a POST request on each approval, revision, or rejection event.
Payloads are JSON with fields: event, ts, session, step. CORS must allow requests from this origin.
Two-factor authentication is required to continue.
In your authenticator app (Google Authenticator, Microsoft Authenticator, Authy, 1Password…), add an account → Enter a setup key using the key below, then enter the 6-digit code to confirm.
Setup key:
📋 Open in your authenticator app
Enter the 6-digit code from your authenticator app.
Work items parsed from Steps 4 (Epics), 5 (Features), and 6 (Stories). Check the items you want to push.
Loading items…
Select sessions to compare (hold Ctrl/Cmd to multi-select):
Previewing the first lines of the export — confirm to download.
Loading preview…