[ Concepts · Cycles ]
Cycles
A cycle is a recurring planning window with a start, end, status, and optional goal. Issues assigned to a cycle form the work planned for that interval, and Hydrant can auto-create future cycles from space settings.
Cycles give teams a near-term operating rhythm while milestones preserve outcome context. Agents can inspect the active window, see scheduled work, and reason about carry-over without guessing from dates.
Shape
- name
- string
- Cycle label, often generated from the space prefix and count.
- startsAt
- number
- Start timestamp.
- endsAt
- number
- End timestamp.
- status
- planned | active | completed
- Cycle state.
- goal
- string?
- Optional focus for the planning window.
- space settings
- fields
- Length, start day, auto-create count, and carry-over mode live on the space.
Lifecycle
- planned: created ahead of time and waiting for its start date.
- active: current cycle; only one active cycle is allowed per space.
- completed: closed cycle. Incomplete issues can carry to the next cycle or return to backlog based on space settings.
- Auto-create can maintain future planned cycles using the space cycle prefix, length, start day, and autoCreateAhead value.
How It Appears In MCP / REST
MCP
list_cycles({ spaceId })
get_cycle_stats({ cycleId })REST
GET /api/v1/cycles?spaceId=...
GET /api/v1/cycles/:id/stats