Where Opulent runs
Sessions run in isolated cloud workspaces with durable state, a shell, an editor, a browser, files, tools, and scoped permissions.
Opulent can install dependencies, run applications, transform data, edit documents, operate a browser, and package finished artifacts after you close your laptop. The run does not depend on your machine staying awake.
You start or steer work from the Opulent app, a Slack thread, or another connected surface. That surface controls the run. The work itself happens in an Opulent cloud workspace, or on infrastructure you control through a Connected Workspace.
Context layers and their authority
Different context carries different authority. Treating all of it as equally true is the most common cause of a confidently wrong result.
| Context layer | Scope and authority |
|---|---|
| Run workspace | Mutable working files, browser state, scripts, and intermediate artifacts inside one run |
| Documents and artifacts | Reviewable outputs retained beyond the workspace; an accepted artifact is canonical for that deliverable |
| Knowledge | Approved and versioned organizational facts, policies, examples, and standards |
| Skills | Approved and versioned procedures, tools, checks, and stop conditions |
| Memory | Scoped guidance distilled from reviewed work; advisory, never a silent override of Knowledge or policy |
| Connected systems | Current CRM, ERP, ticketing, and repository records; authoritative when named as the system of record |
When a workspace copy conflicts with a named system of record or an accepted artifact, Opulent surfaces the conflict rather than silently choosing the stale copy. Name the precedence in the request whenever two sources could reasonably disagree.
Ways to work with Opulent
| Surface | Use |
|---|---|
| Web app | Start substantial work, inspect the plan, follow the run, open files, and review the artifact. |
| Workbench | Watch commands, inspect logs, edit files, use the document surface, open the browser or desktop, and take over when needed. |
| Slack and connected messaging | Start a run from the conversation where the request already has context, and get updates and results in the same thread. |
| Connected Workspace | Run commands and file operations on infrastructure your team controls. |
| API and MCP | Create, search, inspect, message, wait for, stop, and archive sessions programmatically. |
Use the app for planning and review. Use Slack when the work begins in a team conversation. Programmatic controls fit repeatable operations, and a Connected Workspace keeps execution on infrastructure you control.
One workspace, many kinds of work
A single run can combine task planning, file edits, code execution, browser use, and desktop interaction inside one workspace. That matters because most real jobs are not one kind of work: a reconciliation reads a system, transforms a file, checks a total, and drives a portal that has no API.