Skip to main content
Pioneer creates a default workspace on first launch. Keep using it, or create another workspace from the selector at the top of the main thread sidebar. The active workspace is where your threads, provider keys, MCP servers, skills, tasks, settings, and artifacts come together for the gateway you are connected to. Switching workspaces changes the thread tree and the workspace-scoped configuration the app shows.

​
Manage workspaces

Use the workspace selector in the left thread sidebar to:
  • switch to another workspace;
  • create a new workspace;
  • rename an existing workspace.
New threads are created in the active workspace. Provider setup, MCP installation, skill availability, tasks, and artifacts are also resolved through the active workspace.

​
Use workspaces for project separation

Use separate workspaces when work should stay separate but can share the same gateway machine and execution environment. Projects, experiments, and personal contexts are common examples. Workspaces are project and policy boundaries inside one gateway. They separate threads, provider keys, MCP servers, skills, tasks, artifacts, and workspace settings. Turn permission modes and sandbox/resource policy constrain tool work inside that gateway. Use a separate gateway when the execution environment itself should be different.

​
Use gateways for environment separation

Use a separate gateway when the machine, files, accounts, network access, task schedules, or security boundary should be different. A work gateway can stay near work repositories and internal tools; a home gateway can run on a personal server; a sandbox gateway can be reserved for testing tools and skills. The desktop app can connect to all of them, but gateways do not share state. Each gateway has its own database, keystore, workspaces, provider settings, skills, MCP servers, tasks, and execution environment.

​
Use threads for context

Inside each workspace, use threads to keep work understandable. Use one thread for one goal. Start a new thread when the topic changes, when you move from research to edits, or when you want a clean context. Name threads clearly so you can find them later. For example, Research MCP server options is more useful than Notes, and Fix gateway status on macOS is more useful than Bug.
A workspace is a gateway-scoped product boundary. Use permission modes for turn-level control, and choose separate gateways when work needs separate host environments or OS accounts.

​
Further reading

  • Gateway Architecture explains why workspaces belong to a gateway.
  • Permission System explains turn permission modes, sandbox/resource policy, and approval prompts.
  • Persistence explains how workspace, thread, task, artifact, and event state is stored.
  • Secret Storage explains how workspace-scoped provider and MCP secrets are stored.