Skip to content
ThinkWork ThinkWork

Workspace Context

Space workspace context is the local file set for a workroom. It is where operators put the procedures, customer notes, project facts, team norms, and channel-specific instructions that should matter inside one Space without becoming tenant-wide agent defaults.

The tenant platform agent has its own baseline workspace. A Space adds the context for the current work. That lets the same agent behave differently in Support, Finance, Product Launch, or Customer Onboarding without cloning the agent.

What belongs here

Section titled “What belongs here”

Put content in a Space workspace when it is true for that workroom:

  • Customer or account context.
  • Project goals, milestones, and handoff notes.
  • Team-specific operating norms.
  • Workflow instructions for a recurring business process.
  • Channel or inbox procedures.
  • Links and summaries that orient the agent before it calls tools.

Do not use Space workspace files for reusable specialist behavior. That belongs in a folder specialist under the tenant agent workspace.

How it composes

Section titled “How it composes”

When work starts in a Space, ThinkWork resolves the tenant platform agent first, then applies the current Space context for the turn. The Space does not replace the tenant agent’s identity. It narrows the workroom.

Tenant platform agent
  + active Space workspace
  + thread history
  + eligible tools and knowledge
  = turn context

In the rendered /workspace sandbox, the active Space appears under Spaces/<active-space>/. Other authorized Spaces are listed in the generated Workspace Routing section of AGENTS.md, composed at render time from authorization state (active Space, other authorized Spaces, acting user, participants, and Agent Profiles). Their folders are not hydrated into the turn by default; the agent reaches them read-only with the fetch_workspace_source tool.

Editing model

Section titled “Editing model”

Space workspace files are authored state. Edits should be visible on later turns in that Space, while in-flight turns continue with the context they already loaded.

Use the Admin Workspace tab for Space files. Use Tenant Agent when the instruction should apply across the tenant, and use folder specialists when the instruction defines reusable delegated behavior.

Section titled “Related pages”