Features
Workspaces
Workspaces - Opulent documentation
Workspaces
Persistent, context-aware environments — every new task starts knowing exactly what it needs to know
What it is
Opulent Workspaces are persistent environments that retain instructions, knowledge, memory, and file context across every task. Backed by Secure Sandboxing, these environments offer complete isolation with full repository (Git) access and state snapshots. Instead of re-explaining your business context or setting up local dev environments each time, a workspace carries that context automatically — from the first task to the hundredth.
Workspaces replace the need for repetitive setup. Define a context once, and every agent interaction in that workspace starts from a fully informed, securely isolated position.
How to Create a Workspace
- Open the Dashboard and click New Workspace
- Give it a name and write a master instruction that defines the context, goals, and constraints
- Upload relevant files to the knowledge base (SOPs, brand guides, codebase docs, product specs)
- Start creating tasks — each one automatically inherits the workspace configuration
Secure Execution & Snapshots
Every workspace operates in a secure sandbox. This isn't just a container; it includes:
- Full Repository Access: Agents can initialize Git repos, create branches, commit code, and push to remote origins natively.
- State Snapshots: Workspaces can be captured and restored, meaning long-running projects can be paused and resumed exactly where the agent left off, down to the filesystem level.
Pinning Workspaces
Pin frequently used workspaces to the top of your sidebar. Hover over any workspace and click the pin icon. Pinned workspaces always appear first, regardless of sort order.
Master Instructions
The master instruction is the always-on system context for every task in the workspace. Write it to contain everything the agent needs to operate without repeated explanation.
What to Include
Identity & Purpose
"This workspace is for the Acme Corp Growth team. The agent's role is
to support outbound research, competitive analysis, and content production.
Always maintain a professional, data-driven tone."Naming Conventions & Standards
"File naming: YYYY-MM-DD_ProjectName_Version.
All reports should use the Executive slide theme.
Data tables should always include a 'Source' column."Constraints & Rules
"Never include specific revenue figures in external-facing documents.
All research should cite at least 3 independent sources.
Competitors: Salesforce, HubSpot, Pipedrive."Tooling Preferences
"Prefer Google Drive for file delivery. Slack #growth-team for notifications.
Use HubSpot as the source of truth for pipeline data."Knowledge Base
Upload files that should be available as reference for every task in the workspace.
What to Upload
| File Type | Use Case |
|---|---|
| Brand guide (PDF) | Ensure consistent tone and style in all outputs |
| Product spec sheet | Keep agents accurate on features, pricing, positioning |
| Competitor matrix | Inform competitive positioning in every research task |
| SOP documents | Guide agent behavior in recurring workflows |
| Codebase README | Provide context for development tasks |
| Customer personas | Ensure outputs are audience-appropriate |
| Previous reports | Provide baseline for comparisons and updates |
Knowledge Base Updates
- File updates take effect in new tasks created after the update
- Instruction updates apply the next time you send a message in any task
- Previously completed tasks are not affected by updates
Memory
Beyond static files, Opulent's memory system creates compounding context across every interaction in the workspace.
Agents automatically store:
- Project decisions and rationale
- Your stated preferences (formatting, tone, tooling)
- Key facts about your business, team, and customers
- Patterns from past tasks (what worked, what to avoid)
This means a workspace that has been active for 30 days knows far more than one created today — and that knowledge compounds with every subsequent task.
Managing Memory
"Remember that our fiscal year runs February to January"
"Store this competitor analysis in memory for future reference"
"Update memory: we now use Linear instead of Jira for sprint tracking"View and manage stored memory blocks from the workspace Settings → Memory panel.
Collaboration
Workspaces are private by default. Share with teammates to enable collaborative agent workflows.
Sharing Model
| What is Shared | How |
|---|---|
| Master instructions | Automatically shared with all workspace members |
| Knowledge base files | Automatically shared with all workspace members |
| Agent memory | Shared at workspace level |
| Individual task threads | Private to creator by default — share explicitly |
To share a specific task thread with a colleague, open the thread and use the Share button.
Organizing Tasks
Within a workspace, use filters to navigate your work:
| Filter | Shows |
|---|---|
| All tasks | Every task in the workspace |
| In progress | Currently active agent tasks |
| Scheduled | Tasks queued for future execution |
| Completed | Finished tasks with outputs |
Drag tasks to reorder them. Mark favorites for quick access.
Tips
Write detailed master instructions. The more specific your context, the less you need to repeat per task. Think of it as onboarding the agent to your team once.
Keep the knowledge base current. Outdated docs produce outdated outputs. Review your knowledge base monthly and replace stale files.
Use one workspace per team function. Separate workspaces for Sales Research, Product Development, and Finance keep context clean and relevant — agents don't carry irrelevant context from unrelated projects.
Let memory accumulate. The longer a workspace is active, the more context the agent carries. Don't reset unnecessarily.
Test the master instruction with a real task. After writing instructions, run a representative task to verify the agent behavior matches your expectations.
Common Questions
Is there a limit on how many workspaces I can create? No limit. Create as many as your workflow requires.
Can I invite someone to see only specific tasks, not the whole workspace? Yes. Individual tasks can be shared separately from the workspace itself.
If I update the master instruction, does it affect ongoing tasks? Instruction updates apply the next time you send a message in any active task. Tasks you don't interact with again won't see the update until reactivated.
Can I move a standalone task into a workspace? Yes. Tasks can be moved into workspaces at any time.
Can the agent from one workspace access memory from another? No. Memory is scoped to the workspace. This keeps contexts clean and prevents contamination across projects.