Utter

The core planning surface covers summary, board, backlog, list, calendar, sprints, timeline, and docs views, all reading from the same set of issues. Move an issue once and every view updates. Most teams lose hours reconciling a roadmap deck against a task tracker. Here there's a single source to reconcile against, which is the point of an AI task manager that also tracks plain human work.

Utter connects the coding agents your team already uses, including Claude Code, Codex, Cursor, and any MCP-compatible client. The platform orchestrates and records what an agent does rather than running a model itself, so you're not locked into one vendor's assistant. Agents get real tasks with scope, and the run stays on the issue. Teams that want MCP project management without building their own plumbing get the connection for free.

Every agent-created comment, status transition, and issue update lands in activity history alongside human actions. A change made by an agent reads the same as one made by a person, with a clear record of who did what. No black box. That's what keeps trust intact when automation does real work, and it's the feature most teams end up relying on.

The assistant reads a PRD, FRD, spec, or a rough brief and drafts a structured backlog: epics, the stories and tasks under each, and subtasks under those. It asks clarifying questions when the brief is ambiguous, and you review and edit the tree before anything is created. Nothing gets built behind your back. It turns a messy document into something you can start planning against.

Ask about sprint risk, blocked issues, release scope, or recent comments, and the assistant answers using real workspace context. You don't paste in a status dump. It also drafts issues from a short description, filling in a title, type, and body you can edit before saving. That last part saves real time on a messy Monday morning.

The developer surface is a versioned REST API of roughly 180 operations covering issues, projects, sprints, comments, and agents, with a full OpenAPI contract you can generate clients from. If you want REST API project management that behaves predictably in production, this is the layer to build on. API keys are scoped to the permissions each integration needs, and webhooks subscribe external systems to issue, comment, project, and workspace changes with retryable delivery. Usage and audit views show every call.

The pricing model charges only for builders. Those are the people who actively create and manage work. Viewers who read projects and follow issues are free on every plan with no cap. For teams that invite clients and part-time reviewers, this changes the math considerably compared with per-seat tools that bill every person.

Track goals, workload, milestones, and project health without maintaining a second plan. Reports and full activity history sit alongside the work, so managers can follow delivery without asking for a separate update. That's the practical win of keeping planning and reporting in the same workspace.