Projects

Workspaces support first-class Projects: named collections of sessions, assets, and context. Bind a session to a project and it inherits the project's working directory and starts every conversation already knowing what the project is about.

What a project is

A project lives at {workspaceRootPath}/projects/{slug}/ and carries:

• A name, slug, and accent color — the color can tint bound sessions in the session list (toggle the treatment under Appearance).
• Assets — files uploaded to the project (specs, designs, CSVs). The asset manifest is visible to the agent.
• MEMORY.md — a size-capped project memory file. Whatever you (or the agent) record there is injected into every bound session.
• A working directory — sessions bound to the project inherit it unless they override it.

Context injection

When a session is bound to a project, a <project_context> block is added to its system prompt containing the project's description, asset manifest, and MEMORY.md. The agent starts each conversation with that context — no need to re-explain the project every time.

Binding is live: assigning or unassigning a session updates the UI immediately, and the next turn picks up the current project context.

Working with projects

• Create a project from the Projects panel in the navigator (or the sidebar context menu → Add Project).
• Bind a session from the session's context menu, or create the session from within the project's page.
• Project page — each project has an info page with Sessions / Assets / Settings tabs.
• Filter by project — the session list can group and filter by project; clicking a project under the Projects navigator jumps to its sessions.
• Spawned sessions inherit the project — subagent sessions spawned from a bound session bind to the same project automatically.

Projects and the task board

The Kanban task board is organized per project: each project gets its own editable columns, and its tasks and sessions appear as cards. Unbound sessions appear under the workspace's default view.