Workspace Experience

The workspace is the center of the desktop experience. It is the place where the operator sees the agent's context, the attached capabilities, and the state that should survive across sessions.

What a workspace represents

At the product level, a workspace is a stable operating context. It gives an agent:

• its instructions
• its apps and capabilities
• its integrations (connected external accounts that apps use)
• its skills (agent behaviors and instruction packs)
• its session and continuity state
• its memory and outputs
• its model and provider settings

That means the desktop is not just opening a folder. It is opening a complete operating environment.

What the desktop should make visible

The best desktop workspace experience makes the important things obvious without forcing the operator into raw files too early:

Area	What it should answer	Why it matters
Workspace identity	Which workspace am I looking at?	Prevents accidental edits in the wrong context.
Active configuration	What model, provider, and runtime settings are in effect?	Determines behavior during the next run.
Apps and capabilities	What can this workspace do right now?	Shows the agent's actual tool surface.
Integrations	Which external accounts are connected?	Determines whether apps can access services like Gmail, GitHub, or Twitter.
Session state	What happened most recently?	Helps you continue work without starting over.
Durable memory	What should persist beyond one run?	Keeps important context from being lost.
Outputs	What has this workspace produced?	Gives you reviewable results instead of hidden side effects.

How the experience should feel

The goal is not to expose every internal file in the first screen. The goal is to help you answer three questions quickly:

1. What is this worker for?
2. What can it do right now?
3. What changed since the last time I opened it?

That is why the desktop should emphasize the workspace summary, the available apps, the current model configuration, and recent activity first. Raw files, logs, and advanced diagnostics are useful, but they should come after the operator can already orient themselves.

Daily workflow

1. Open the workspace
   Start by selecting the worker context you want to inspect or continue.
2. Check the active capabilities
   Confirm which apps, skills, and tools are available before you run anything important.
3. Review recent state
   Look at the latest outputs, memory updates, and session history to understand what changed.
4. Adjust configuration if needed
   Update the model or provider settings before starting the next run.
5. Continue the worker
   Launch or resume the worker with the confidence that the workspace context is still intact.

A good workspace UI avoids two extremes

• It should not hide the important state behind too many nested screens.
• It should not drown the operator in raw files before they need them.

Holaboss works best when the desktop treats the workspace as a living operating environment: visible, inspectable, and editable, but still organized around the operator's decisions instead of around the repository layout.