Workspaces
How AGH resolves workspace roots, layers config overlays, and attaches additional roots for monorepos and cross-project agent sharing.
- Audience
- Operators running durable agent work
- Focus
- Workspaces guidance shaped for scanability, day-two clarity, and operator context.
A workspace is a registered project root. AGH uses it as the source of truth for workspace-scoped agents, skills, memory, and config overlays. Sessions inherit the workspace context, and resolution is deterministic — the registered root wins over global defaults.
Use this section when the same machine runs more than one project, when an agent needs project-local instructions, or when a monorepo needs extra directories attached without copying files into the primary root. The important rule is that AGH treats the registered workspace as an identity, not just as the current shell directory. That identity is what sessions, memories, overlays, and additional roots attach to.
In this section
Resolver
Workspace resolver
Use this page for how AGH registers workspace roots and resolves an active workspace at session start.
Overlays
Workspace config overlays
Use this page for how `<workspace>/.agh/config.toml` and `mcp.json` layer over global config.
Multi-root
Multi-root workspaces
Use this page when one session must see additional directories for monorepos or shared agent libraries.