English | 中文

Dependency-aware todo manager. Tasks form a DAG (directed acyclic graph) — topological sort tells you what to do next.

Most todo apps treat tasks as a flat list. Real work has dependencies: you can't deploy before tests pass, can't test before the API is built. dagdo models your tasks as a graph and always tells you which tasks are ready to work on right now (zero in-degree nodes).

• Dependency graph — link tasks with dagdo link, cycles are automatically rejected
• What's next? — dagdo next shows tasks with no unfinished blockers (topological sort)
• Smart completion — dagdo done tells you which tasks just became unblocked
• Notes — attach plain-text notes to tasks (acceptance criteria, links, context)
• Visualize — ASCII tree, Mermaid syntax, or PNG/SVG image (--dot for Graphviz)
• Web view — dagdo ui opens an interactive graph editor with live updates
• Cloud sync — dagdo sync keeps tasks in sync across machines via any git remote
• Priority & tags — filter and sort by what matters
• Prefix IDs — type a3f instead of the full a3f1b2
• Light / dark mode — web view follows your system theme (or toggle manually)
• Single binary — compile to a standalone executable, no runtime needed

npm install -g @coiggahou2002/dagdo

git clone https://github.com/Coiggahou2002/dagdo.git
cd dagdo
bun install
bun run build   # produces ./dagdo binary

Download from GitHub Releases.

# Add tasks
dagdo add "Design database schema" --priority high --tag backend
dagdo add "Implement API" --tag backend
dagdo add "Build frontend" --tag frontend
dagdo add "Integration testing"

# Add dependencies (use ID prefixes)
dagdo link <design-id> --before <api-id>       # Design must finish before API
dagdo link <design-id> --before <frontend-id>  # Design must finish before frontend
dagdo link <api-id> --before <testing-id>      # API must finish before testing
dagdo link <frontend-id> --before <testing-id> # Frontend must finish before testing

# What can I work on right now?
dagdo next
# a3f1b2  HIGH  Design database schema [backend]

# Finish a task
dagdo done <design-id>
# Done a3f1b2  Design database schema
#   Unblocked: b2c3d4  Implement API
#   Unblocked: e5f6a7  Build frontend

# See the dependency graph
dagdo graph              # ASCII in terminal
dagdo graph --mermaid    # Mermaid syntax (paste into GitHub/Notion)
dagdo graph --all --png graph.png  # PNG image with done tasks grayed out

Every task gets a 6-character hex ID (e.g. a3f1b2). You can use any unique prefix:

dagdo done a3f    # matches a3f1b2
dagdo done a      # works if only one ID starts with "a"

# ASCII tree (default)
dagdo graph

# Mermaid (copy to GitHub issues, Notion, etc.)
dagdo graph --mermaid

# PNG or SVG via Mermaid (requires mermaid-isomorphic and playwright)
dagdo graph --png output.png
dagdo graph --png output.svg
dagdo graph --all --png full.png   # include done tasks (grayed out)
dagdo graph --png output.png --dot # use Graphviz instead of Mermaid

Tasks are stored in ~/.dagdo/data.json — one user-level todo list across all your projects. If you want the list synced across machines, see the next section.

dagdo ui starts a local HTTP server on http://localhost:3737, opens your browser, and renders an interactive task graph. CLI changes from other terminals appear within a second; the browser can also edit: drag nodes to rearrange, drag from one node's bottom handle to another's top to create a dependency (with cycle detection), select a node/edge and press Delete to remove it, double-click a node title to rename it, and use the + New task button in the header to add one. Click a node to open a compact popover anchored next to it — rename the task, change priority, add/remove tags, write a plain-text note (up to 2000 chars), or mark the task done. Supports light, dark, and system themes.

Canvas shortcuts:

• Space + left-drag — pan the canvas (grab cursor while held; borrowed from Figma/Sketch)
• Option + click (macOS) / Alt + click (other platforms) on empty canvas — create a new task exactly at the click point
• Esc — dismiss the popover

dagdo ui                  # default port 3737, opens a browser tab
dagdo ui --port 8080      # pick your own port
dagdo ui --no-open        # don't auto-open — useful in remote/SSH sessions

Port conflicts auto-increment (e.g. a second instance will land on 3738). Ctrl+C stops the server.

If you use dagdo across multiple machines, you can sync your global tasks through any git remote (GitHub, GitLab, self-hosted — whatever you already use).

Requirements: git installed locally, and an empty (or existing dagdo-managed) git repository on a remote you control. Authentication is whatever your git already uses (SSH keys, credential helper) — dagdo never touches your credentials.

# On your first machine (with existing tasks)
dagdo sync init git@github.com:you/my-dagdo-tasks.git
# → pushes your local tasks to the remote

# On a second machine (fresh install)
dagdo sync init git@github.com:you/my-dagdo-tasks.git
# → clones the remote into ~/.dagdo/

# Day-to-day: after making changes, publish them
dagdo sync
# → fast-forward push (or pull, if remote is ahead)

# Check where you stand
dagdo sync status

Model. Sync assumes a single-user, one-active-device-at-a-time workflow. Each dagdo write auto-commits locally; dagdo sync pushes or pulls as a fast-forward. If both sides diverge (you edited on two machines without syncing in between), dagdo refuses to merge and asks you to pick a side explicitly:

dagdo sync --accept-local    # keep local, overwrite remote
dagdo sync --accept-remote   # keep remote, overwrite local

dagdo ships with a Claude Code skill that lets AI agents manage tasks through the CLI. The agent decomposes work into tasks, links dependencies, and uses dagdo next to recommend what to work on — all via natural language.

cp -r skills/dagdo ~/.claude/skills/dagdo

Just describe your work — the agent handles the rest:

• "help me plan the API refactor as dagdo tasks" — decomposes the work, creates tasks, links dependencies
• "what should I work on next?" — runs dagdo next and recommends based on priority
• "I finished the database migration" — finds the task, marks it done, reports what's unblocked
• "remind me to ask Jack for the server credentials" — creates a quick task

The full command reference, storage details, and interaction guidelines live in skills/dagdo/SKILL.md.

MIT