The right project
The account, project, and team context needed to keep work in the right place.
How it works
From “I will do it later” to work you can review today.
Start with a real business job, not a blank chat. Supr gives the work a home, keeps the steps visible, and leaves you with files, decisions, and next actions you can use.
Create a project
Start with the product, repo, launch, or workflow you want help with. The project becomes the boundary for context, history, usage, and decisions.
Describe the work
Ask for a launch audit, repo review, bug investigation, research pass, release checklist, or implementation plan.
Choose what needs your approval
Supr can research and draft on its own. It stops for your approval before it sends, publishes, deletes, changes access, or spends money.
Watch the work
See what is running, what is waiting on you, what finished, and the files it created.
Reuse the good work
Keep the outputs and run the same playbook again when the project changes or the next week begins.
Runtime boundary
The dashboard is public. The raw agent runtime is not.
Your account layer checks who you are, what project you opened, and what is included in your plan. Only then does Supr hand the approved work to its protected execution workspace with the project context and your guardrails attached.
That separation keeps the experience simple for you while keeping the execution service protected behind the scenes.
What Supr carries into the work
The work starts with context, not guesswork.
Useful help needs more than a message. Supr packages the run with the account, project, plan, autonomy, approval, and context needed to do useful work inside the right boundary.
What is included
Your plan, available work, and the limits that apply before a run begins.
Your guardrails
What Supr can do on its own and when it must pause for you.
The useful context
Your project description, relevant history, chosen template, and the details you provide.