Workspaces
Workspaces are the durable context surfaces that workflows run against.
They matter because a workflow usually needs more than a prompt. It needs standing context: repository identity, specifications, prior artifacts, timeline, and related resources that persist beyond one task.
What A Workspace Represents
Section titled “What A Workspace Represents”A workspace is where the platform stores the standing context around a domain of work, such as:
- repository identity
- settings and specification
- knowledge and structured content
- timeline and recent workflow history
- artifact browsing and related resources
The key distinction is:
- the platform workspace is the durable control-plane record
- the runtime workspace is the fresh execution surface materialized for a task
Those are related, but they are not the same thing.
Dashboard Surfaces
Section titled “Dashboard Surfaces”The dashboard exposes both:
- a workspace library for search, filtering, and posture review
- a workspace detail editor for settings, knowledge, memory, content, and artifact views
The workspace library also supports:
- search
- active and inactive filtering
- recent-activity and workflow-volume sorting
- quick posture review before opening the detailed editor
Why This Matters
Section titled “Why This Matters”This distinction is one of the main reasons Agirunner can support both continuity and isolation. Long-lived context stays in the platform workspace. Task-scoped mutation happens in the runtime workspace.
How It Connects To The Rest Of The System
Section titled “How It Connects To The Rest Of The System”Workspaces sit in the middle of the product:
- Playbooks And Authoring define the process that runs against a workspace
- Workflows launch concrete runs that point at one workspace
- Workflow Detail surfaces the artifacts, history, and timeline that accumulate against that workspace over time
- Runtime explains how the runtime materializes a fresh task-scoped execution workspace from the platform-side record
That is why this page matters. It is not just a repository picker. It is the durable project context that connects launch-time workflow decisions to runtime execution and back to retained artifacts, memory, and history.