---
title: Workspace
order: 1
description: "The magus root directory that owns a set of projects and shared config; the unit magus operates over."
tags: [glossary, core-model]
---

# Workspace

The magus root directory that owns a set of projects and shared config; the unit
magus operates over.

## Elsewhere

npm, pnpm and Yarn workspaces, Cargo workspaces and Go's `go.work` each call a set of
packages that share one dependency resolution a workspace. A magus workspace is wider: it is
the root magus operates over, and it can hold several of those package-manager workspaces,
each inside a project.

## Example

`magus ls` lists every project the workspace discovered under its root.

```sh
magus ls
```

## Used in

<!-- BEGIN GLOSSARY USAGE (generated by glossary-usage-generate from the knowledge graph; edit the generator, not this list) -->

In the docs:

- [2. Workspace spells & magusfiles (import "charm")](../concepts/charms.md#2-workspace-spells--magusfiles-import-charm)
- [Across separate runs: the workspace lock](../concepts/concurrency.md#across-separate-runs-the-workspace-lock)
- [Workspace providers](../concepts/workspace/providers.md#workspace-providers)
- [Review, workspace and the merge queue](../decisions/0011-typed-provider-calls.md#review-workspace-and-the-merge-queue)
- [2. Bootstrap a workspace with magus init](../guides/getting-started.md#2-bootstrap-a-workspace-with-magus-init)
- [Maintaining the workspace harness](../guides/integrations/agents/claude-code.md#maintaining-the-workspace-harness)

In the code (`magus refs <name>` lists every site):

- `activity.Workspace` (Go)
- `diagram.workspace` (Go)
- `job.workspace` (Go)
- `notes.workspace` (Go)
- `tool.workspace` (Go)

<!-- END GLOSSARY USAGE -->

## See also

- [Workspace and projects](../concepts/workspace.md)
- [Project](project.md)