Tasks, Projects & Workspaces

Last updated · 2026-09-05

Four basic concepts

ConceptMeaningExample
WorkspaceThe folder you authorize; the boundary for all reads, writes, and commands~/Code/shop-api
ProjectAn organizational unit for workspaces"Shop backend"
TaskOne complete conversation and unit of work, containing multiple runs"Refactor the orders module"
RunOne execution of the agent for a given input"Get tests green, then refactor"

A project maps to a workspace. A task runs inside one workspace and can take several follow-up inputs, each producing a run; every run gets its own timeline, approval records, and ChangeSet.

The task composer

The toolbar under the New Task input box offers:

Backend (model)

  • API models: any model from the eleven configured providers;
  • CLI backends: locally installed Codex CLI, Claude Code, or OpenCode (reusing their sign-in and default model — VibeSpace never touches their credentials).

See Model providers and CLI backends.

Permission mode

Three levels: Request approval, Auto approval (default), and Full access. See Permissions & approvals.

Experts

Assign a built-in expert (e.g. "Implementation Engineer" or "Code Reviewer") to run the task; each expert has its own responsibilities and tool restrictions. See Experts & teams.

Skills

Check the skill packages to activate — their instructions and resources are injected into the run. See Skills.

Attachments

  • Attach files and images (images need a vision-capable model; you'll be warned otherwise);
  • Attachments are sent as checksummed snapshots and never include local absolute paths.

Projects page

The Projects navigation lets you:

  • Review all authorized projects and their workspaces;
  • Filter historical tasks by project;
  • Keep per-project defaults.

Archiving conversations

Settings includes an "Archived conversations" panel: inactive tasks can be archived to reduce clutter and restored when needed. Storage usage is visible on the "Data management" card in Settings.

Working with the Kanban

The Kanban view (provided by the built-in module) organizes tasks as cards across columns to track "to do → in progress → done" — see Kanban.