Multi-Repo Workspaces

Workspaces let you register sibling repositories alongside your primary project. Once registered, the agent can read from and write to those repos as part of the same session — useful when your work spans multiple related projects (e.g. a shared library and the app that depends on it).

By default, Caboose blocks all file access outside the primary project directory. Workspaces are how you explicitly grant access to additional paths.

Adding a workspace

/workspace

This opens the workspace add flow, which guides you through:

1. Path — the local path to the sibling repo
2. Name — a short label used in logs and the sidebar
3. Mode — proactive (agent searches this workspace automatically) or explicit (agent only accesses it when you reference it directly)
4. Permissions — read-only or read-write

Modes

Proactive

The agent treats this workspace like an extension of the primary project. It may read or search this repo as part of normal exploration — for example, looking up a shared type definition or checking a dependency’s source.

Explicit

The workspace is available but the agent won’t access it unless you tell it to. Use explicit mode for repos you want available for reference but don’t want the agent roaming through automatically.

Permissions

• Read-only — the agent can read files from this workspace but cannot write or run commands in it
• Read-write — full access, same as the primary project

Workspace list

Active workspaces are shown in the sidebar. To remove a workspace, open /settings and navigate to the workspaces section.

Example

You’re working on an API server and want the agent to reference a shared types library:

/workspace
Path: ../shared-types
Name: shared-types
Mode: proactive
Permissions: read-only

Now the agent can look up type definitions in shared-types as part of understanding your codebase, without you needing to explicitly tell it where to look every time.