Everything in coregoo
A tracker, a docs library, and an automation surface — designed together so they actually reference one another.
A tracker with real depth
Everything you expect from an issue tracker, without the configuration project that usually comes attached.
- Epics, sub-tasks and a parent/child hierarchy with cycle protection
- Issue links — blocks, duplicates, relates-to — with the inverse kept in sync automatically
- Due dates, original estimates, worklogs and a derived time-remaining rollup
- A blocked indicator that reads your links instead of trusting a checkbox
- Full audit history on every ticket: who changed what, and when
Sprints and estimation that stay out of the way
Run iterations without a ceremony tax. Completing a sprint releases whatever did not land, keeping its status intact.
- One active sprint at a time, with points summed per column
- Async planning poker — votes stay hidden until reveal, even over the API
- Auto-reveal once everyone has voted, then apply the consensus in a click
- Agents can vote too, so estimates are not just a human ritual
A Library that behaves like a wiki
Spaces hold nested page trees. Pages are plain Markdown, so nothing is trapped in a proprietary block format.
- Spaces with nested, collapsible page trees
- A markdown-first block editor — click a block to edit its raw source, blur to render
- Comments and @mentions on pages, routed to the same inbox as ticket activity
- Deleting a page reparents its children instead of orphaning them
The glue between the two
Most tools bolt a wiki onto a tracker and call it integrated. These actually reference each other.
- ⌘K searches tickets, pages, spaces and people at once — and jumps you there
- Type a ticket id in any page and it renders as a live chip with the current status
- Backlinks resolve both directions: “References” on the page, “Mentioned in” on the ticket
- Full-text search reaches page bodies, not just titles
Built for agents from the start
The CLI is not an afterthought wrapper — it is how the system was designed to be driven.
- Agents are members: assignable, mentionable, and part of the audit trail
- Every command takes --json and returns parseable output with proper exit codes
- Drops into Claude Code as a plugin so your agent files and moves its own tickets
- Data is a single JSON file — commit it, diff it, review changes in a pull request
Your workspace, your server
Multi-tenant when you want it, self-hosted when you need it, with no database to operate.
- Organizations are fully isolated, each with its own members and ticket prefix
- Owner / admin / member roles, email invites, and password resets
- Sessions are opaque bearer tokens — only their hash is ever stored
- Runs anywhere Node runs; no Postgres, no Redis, no queue
See it on your own board
Create a workspace and try it with a real ticket — it takes about a minute. Free during the beta, and early workspaces keep 25% off when we launch.