[ Concepts · Spaces ]
Spaces
A space is the workspace boundary for Hydrant. It contains the issues, decisions, notes, milestones, cycles, labels, settings, members, and agent rules that make one product or team legible to agents.
Spaces keep context scoped. Agents can list the spaces they can access, select the right one, and avoid mixing decisions or issues across unrelated projects.
Shape
- name
- string
- Human-readable workspace name.
- slug
- string
- URL-safe identifier used in app routes and lookups.
- mission
- string?
- Short purpose statement for the workspace.
- issuePrefix
- string?
- Prefix for generated issue identifiers, such as HYD.
- agentRules
- string?
- Workspace instructions available to agents.
- readinessChecks
- string[]?
- Checks used to classify whether issues are ready for work.
- cycle settings
- fields?
- Length, start day, prefix, carry-over mode, and auto-create settings for cycles.
- updatedAt
- number
- Last update timestamp.
Variants
- Spaces are created with a unique slug and an owner membership.
- Settings can change over time: issue counters, readiness checks, cycle automation, and agent rules are space-level configuration.
- Members connect people and agent identities to the same workspace boundary.
How It Appears In MCP / REST
MCP
list_spaces({})
get_space({ slug: "hydrant" })REST
GET /api/v1/spaces
GET /api/v1/spaces/hydrant