Knowledge and memory
Connected documents, visual workspaces, search, and worker-published knowledge stay distinct from private worker memory.
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.
Choose the right area
Open Knowledge, Inbox, Publishing, Documents, Computer, Applications, or Media without leaving the shared SuprOS workspace.
Assign the work
Ask a permanent worker for research, planning, creation, investigation, communication, or execution tied to that project.
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.
Review and reuse the result
See what ran, what it cost, which sources and revisions were used, what finished, and the files or decisions it created.
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.
One product shell
Different kinds of work, the same operating rules.
SuprOS keeps each capability where a user expects to find it while sharing identity, organization isolation, approvals, budgets, provenance, accessibility, and responsive navigation.
Inbox and Publishing
Mail and site revisions remain organization-scoped, with consequential actions and public publishing waiting for approval.
Documents and Media
Documents, Spreadsheets, Presentations, PDF, Web Artifacts, transcription, and Media output retain source and revision provenance.
Applications and Computer
Generated software, browser work, coding, and commands inherit the assignment, budget, isolation, and rollback policy of the project.
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.
The right project
The account, project, and team context needed to keep work in the right place.
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.