
Claudia
io.github.yuvalsuedePublished by GitHub account yuvalsuedev0.1.3Updated Oct 25, 2026
Task management for AI agents with hierarchical tasks, dependencies, sprints, and coordination.
Overview
Claudia is a local task-management server that lets an AI assistant create, track, coordinate and verify hierarchical tasks, dependencies, sprints and projects.
- What you can do
- Create, read, update, delete and bulk-edit tasks, with hierarchical trees and state transitions between pending, in progress, verification and completed, plus per-task JSON context storage up to 64KB and acceptance-criteria verification with evidence. Manage dependencies and coordination: add or remove blockers, list blocked and ready tasks, and atomically claim, release, hand off or abandon tasks for multiple agents. Run compound operations that start a task, finish it with a summary, or return the current agent's workspace. Organize work into sprints and isolated projects, including selecting the active project and auto-detecting it from the working directory.
- When to use it
- Useful when an assistant works through long multi-step jobs and needs durable task state across sessions, or when several agents share one project and must claim work without collisions. Also fits teams that want a kanban-style task store with sprints and acceptance checks behind a CLI and web dashboard.
- Requirements
- Runs as a local process over stdio, started with bunx from the npm package claudia-cli; the README lists Bun runtime v1.0+ as a prerequisite. A local database file is used, defaulting to a path under the user's home directory and overridable with the CLAUDIA_DB environment variable. No accounts, API keys or headers are declared.
Installation
In SourceWeft
- Open Claudia in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Claudia
A task management system built for AI agents.
Official website: https://claudiacli.com/
Claudia provides structured task tracking with a Model Context Protocol (MCP) server, enabling AI assistants like Claude to manage their own work through hierarchical tasks, dependencies, sprints, and acceptance criteria verification.
Why Claudia?
AI agents need a way to:
- Track progress across complex, multi-step tasks
- Coordinate when multiple agents work on the same project
- Remember context between sessions (64KB JSON storage per task)
- Verify work against acceptance criteria before completion
- Organize work into sprints and project hierarchies
Claudia provides all of this through both a CLI and MCP server interface.
Quick Start
Try the Demo
See Claudia in action with sample data:
Then open http://localhost:3333 in your browser to explore the kanban board and sprint views.
Screenshots
Task Board
Sprint Management
Features
Installation
Prerequisites
- Bun runtime (v1.0+)
From Source
Build Standalone Binary
Usage
CLI Commands
Task Management
Task Hierarchy
Task Context (Agent Memory)
Dependencies
Sprints
Projects
Web Dashboard
The dashboard provides:
- Tasks View: Kanban board with drag-and-drop columns
- Sprints View: Sprint cards with progress indicators
- Project Filter: Scope views to specific projects
- Clear Completed: Archive finished tasks
MCP Server Integration
Start the MCP server for use with Claude Code:
Claude Code Configuration
Add to .mcp.json in your project root:
Or for development (without building):
After adding the config, restart Claude Code to connect.
Available MCP Tools
Compound Operations (Recommended for agents)
Task Management
Coordination
Verification
See the full MCP tools reference below for complete documentation.
Task Workflow
Valid transitions:
pending→in_progress,blocked,archivedin_progress→pending,verification,completed,blocked,archivedverification→in_progress,completed,blocked,archivedblocked→pending,in_progress,archivedcompleted→in_progress,archivedarchived→ (terminal state)
Tasks can skip verification if no acceptance criteria are defined.
Multi-Agent Coordination
Claudia supports multiple AI agents working concurrently on the same project.
Task Claiming
Optimistic Locking
Recommended Pattern
task_ready- List tasks with satisfied dependenciestask_claim- Atomically reserve a tasktask_transition- Move toin_progresstask_context_merge- Save progresstask_transition- Move tocompleted- On failure:
task_release- Let another agent retry
Configuration
Development
Exit Codes
MCP Tools Reference
Compound Operations
task_start
Create and start a task in one operation. Auto-claims for the current agent.
task_finish
Complete a task with optional summary.
task_workspace
Get current agent's workspace context including claimed tasks.
task_handoff
Transfer task to another agent.
task_abandon
Release task back to pending with reason.
Task CRUD
task_create
task_read
task_update
task_delete
task_list
task_transition
task_tree
Bulk Operations
task_create_many
task_update_many
task_transition_many
Dependencies & Coordination
task_dependency_add
task_dependency_remove
task_dependencies
task_blocked
List all tasks with unsatisfied dependencies.
task_ready
List all tasks ready to work on (dependencies satisfied).
task_claim
task_release
Context Storage
task_context_set
Overwrite task context (max 64KB).
task_context_merge
Deep merge into existing context.
task_context_get
Verification
task_verify
Mark an acceptance criterion as verified.
task_verification_status
Get verification progress for a task.
Sprints
sprint_create
sprint_list
sprint_show
sprint_update
sprint_delete
sprint_activate
Projects
project_create
project_list
List all projects.
project_read
project_update
project_delete
project_select
project_current
Contributing
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
License
GPLv3 - see LICENSE for details.
Source: README.md at commit 8898fa8
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts