Deciduous
Decision graph tooling for AI-assisted development. Track every goal, decision, and outcome. Survive context loss. Query your reasoning.
See It In Action
Browse the Live Decision Graph — 340+ decisions from building deciduous itself
Watch the Demo — Full session: initialization, decision logging, graph visualization, context recovery
Why Deciduous?
LLMs generate complex code fast. Reviewing it, understanding it, and maintaining it? That's on you.
The problem: Sessions end. Memory compacts. Decisions evaporate. Six months later, no one—human or AI—remembers why you chose approach A over approach B.
The solution: Deciduous creates a persistent, queryable graph of every decision made during development. Both you and your AI assistant can query past reasoning, see what was tried, understand what was rejected and why.
This isn't documentation written after the fact. It's a real-time record of how software gets built, captured as decisions happen—by whoever is making them.
The Premises
-
Decisions are the unit of institutional knowledge. Code tells you what, but decisions tell you why. Six months from now, you won't remember why you chose Redis over Postgres for that cache. The graph will.
-
Structured thinking produces better outcomes. The act of logging a decision—naming it, assigning confidence, connecting it to goals—forces you to think it through. It's rubber duck debugging for architecture.
-
Real-time logging beats retroactive documentation. Capture reasoning in the moment, not reconstructed from memory. By the time you write the post-hoc docs, you've already forgotten the options you rejected.
-
Graphs beat documents. Decisions connect—goals spawn decisions, decisions spawn actions, actions produce outcomes. A graph captures these relationships. You can trace any outcome back to the goal that spawned it.
-
Complex PRs tell a story. A 50-file PR is incomprehensible as a diff. But as a decision graph? You can see the goal, the key decisions, the rejected approaches, and how each file change connects to the larger purpose. Reviewers can understand why, not just what.
-
Context loss is inevitable. Sessions end. Memory compacts. The graph survives. When you come back to a project after months away, the graph is your memory.
-
Humans and AI assistants both benefit. You can query the graph to remember your own reasoning. The LLM can query it to understand decisions made before its context window. Either of you can log decisions. The graph doesn't care who's typing—it just preserves the reasoning.
-
The graph is a shared workspace. When the LLM makes a choice, you can see it. When you make a choice, the LLM can query it. Decisions flow between sessions, between humans and AI, between teammates.
Who Uses It
You, the developer:
- Think through decisions more carefully by structuring them
- Remember why you made choices months later
- Review complex PRs by understanding the decision flow, not just the diff
- Onboard to unfamiliar codebases by reading the decision history
Your AI assistant:
- Recover context after session boundaries or compaction
- Understand decisions made before its context window
- Build on previous reasoning instead of starting fresh
- Leave a queryable trail for future sessions
Your team:
- Share decision context across PRs via patch files
- Review PRs with full visibility into the reasoning
- Build institutional knowledge that survives employee turnover
Quick Start
1. Install
2. Initialize in your project
This creates:
.deciduous/deciduous.db— SQLite database for the graph- Editor-specific tooling (
.claude/commands/,.windsurf/rules/,.opencode/command/, or.codex/prompts/) docs/— Static web viewer (deployable to GitHub Pages)CLAUDE.mdorAGENTS.md— Project instructions with the logging workflow
3. Start using
# Log a decision
# Connect decisions
# View the graph
4. Deploy to GitHub Pages
Enable Pages: Settings > Pages > Source > Deploy from branch > gh-pages
Your graph will be live at https://<user>.github.io/<repo>/
The Workflow
SESSION START
|
Run /recover → Query past decisions
|
DO WORK → Log BEFORE each action
|
AFTER CHANGES → Log outcomes, link nodes
|
BEFORE PUSH → deciduous sync
|
SESSION END → Graph survives
During a session
# Starting a new feature
# Making a choice
# Implementing
# Recording outcome
Viewing the Graph
Two full-featured interfaces for browsing the graph—use whichever fits your workflow.
Web Viewer
A browser-based interface with four visualization modes, branch filtering, and auto-refresh. Deploy to GitHub Pages for shareable, always-up-to-date graphs.
| View | Purpose |
|---|---|
| Chains | Decision chains organized by session—see the story of a feature |
| Timeline | Chronological view merged with git commits—trace decisions to code |
| Graph | Force-directed interactive visualization—explore connections, zoom, pan |
| DAG | Hierarchical goal→decision→outcome flow—understand structure at a glance |
Features: branch dropdown filter, node search, stats bar with counts, click-to-expand details, recency sorting, responsive layout.
Terminal UI
A rich terminal interface for when you're already in the shell. Vim-style navigation, syntax-highlighted file previews, and integrated git diffs.
| Key | Action |
|---|---|
j/k, gg/G |
Navigate timeline |
Enter |
Toggle detail panel with connections, metadata, prompts |
/ |
Search by title or description |
f |
Filter by node type (goal, decision, action, etc.) |
b/B |
Filter by branch / fuzzy branch search |
o |
Open associated files in your editor |
O |
View linked commit with full diff |
p/d |
Preview file content / show file diff (syntax highlighted) |
s |
Show goal story—hierarchical view from goal to outcomes |
? |
Help |
Features: auto-refresh on database changes, file browser panel, commit detail modal, syntax highlighting via the same engine as bat.
Node Types
| Type | Purpose | Example |
|---|---|---|
goal |
High-level objective | "Add user authentication" |
decision |
Choice point | "Choose auth method" |
option |
Approach considered | "Use JWT tokens" |
action |
Implementation step | "Added JWT middleware" |
outcome |
Result | "Auth working in prod" |
observation |
Discovery or insight | "Existing code uses sessions" |
Edge Types
| Type | Meaning |
|---|---|
leads_to |
Natural progression |
chosen |
Selected this option |
rejected |
Did not select (include reason) |
requires |
Dependency |
blocks |
Preventing progress |
enables |
Makes something possible |
Multi-User Sync
Share decisions across teammates working on the same codebase.
Each node has both a local ID and a globally unique change_id (UUID). Export patches to share:
# Export your branch's decisions
# Apply patches from teammates (idempotent—safe to re-apply)
# Preview before applying
PR Workflow
- Create nodes while working
- Export:
deciduous diff export --branch my-feature -o .deciduous/patches/my-feature.json - Commit the patch file (not the database)
- Open PR with patch file included
- Teammates apply after pulling
Commands Reference
# Initialize
# Add nodes
# Node metadata
|
# Update prompts on existing nodes
# Connect nodes
# Query
# Visualize
# Export
# Multi-user sync
# Shell completion
Shell Completion
Enable tab completion for commands, options, and arguments.
Zsh (add to ~/.zshrc):
Bash (add to ~/.bashrc):
Fish (add to ~/.config/fish/config.fish):
deciduous completion fish | source
PowerShell (add to profile):
deciduous completion powershell | Out-String | Invoke-Expression
Branch-Based Grouping
Nodes are automatically tagged with the current git branch.
Configuration (.deciduous/config.toml):
[]
= ["main", "master"]
= true
GitHub Pages Deployment
deciduous init creates GitHub workflows that:
- Deploy your graph viewer to GitHub Pages on push to main
- Clean up branch-specific PNGs after PR merge
Enable Pages: Settings > Pages > Source > Deploy from branch > gh-pages
Building from Source
macOS Dependencies
The syntect crate (used for syntax highlighting in the TUI) requires libiconv:
Add the LIBRARY_PATH export to your shell profile (.zshrc or .bashrc) to make it permanent.
Optional Dependencies
| Dependency | Required For | Install |
|---|---|---|
| graphviz | deciduous dot --png |
brew install graphviz (macOS) / apt install graphviz (Ubuntu) |
Why "deciduous"?
It almost has the word "decision" in it, and they're trees.