# Deciduous Roadmap
## Completed
### v0.8.x - Prompt Tracking & Template Sync (December 2024)
- [x] `--prompt` flag for capturing user prompts on nodes
- [x] Prompt display in TUI detail panel with word-wrap
- [x] Template sync fix - init.rs templates match actual command files
- [x] `deciduous update` no longer destroys custom content
### v0.7.x - TUI Graph Viewer (December 2024)
- [x] `deciduous tui` command for terminal-based graph visualization
- [x] Timeline view with vim-style navigation (j/k/gg/G)
- [x] Detail panel with node info, connections, files
- [x] File browser mode (F to toggle, n/N to navigate)
- [x] File preview with syntax highlighting (p key)
- [x] File diff viewer with syntax + diff coloring (d key)
- [x] Commit modal with split view (O key)
- [x] Branch filtering (b to cycle, B for fuzzy search)
- [x] Timeline order toggle (R for reverse chronological)
- [x] Search (/ to filter by title/description)
- [x] Goal story view (s to show goal hierarchy)
### v0.6.0 - Multi-User Graph Sync (December 2024)
- [x] jj-inspired dual-ID model with `change_id` (UUID) for globally unique nodes
- [x] `deciduous diff export` - export nodes as shareable JSON patches
- [x] `deciduous diff apply` - apply patches from teammates (idempotent)
- [x] `deciduous diff status` - list available patches
- [x] `deciduous migrate` - add change_id columns for sync
- [x] Auto-migration on database open
- [x] Bootstrapped templates include multi-user sync documentation
### Legacy Cleanup
- [x] All templates use `deciduous` binary (no more `losselot` references)
- [x] Live graph URLs point to correct project
- [x] `src/init.rs` uses installed binary path
### Code Tracking & File Associations (Partial)
- [x] `--files` flag for associating files with nodes
- [x] File browser in TUI detail panel
---
## In Progress / High Priority
### Narrative User Guide
*A real, end-to-end tutorial that walks through an actual use case*
- [ ] **Narrative-driven tutorial** (like the jj tutorial)
- Not a reference manual—a story
- Follow a real feature from inception to merged PR
- Show the decision graph evolving alongside the code
- Include the missteps, dead ends, and course corrections
- [ ] **Cover the full workflow live**
- Start with `deciduous init` in a fresh project
- Log goals, make decisions, reject options, implement actions
- Show context recovery after a simulated "session break"
- Generate PR writeup from the graph
- Deploy to GitHub Pages
- [ ] **Dual perspective: human and AI**
- Show the human developer using the TUI to review decisions
- Show the AI querying the graph to recover context
- Demonstrate handoff between sessions
- [ ] **Publish as a dedicated guide**
- Standalone page on the GH Pages site
- Could also be an asciinema + written hybrid
- Link prominently from README
### Automated Graph Sync Workflow
*Multi-user state management should be seamless*
- [ ] **Default to diff/patch workflow for multi-user state management**
- With multiple users coming, graph database sync should be automated by the AI
- AI should automatically export patches when committing decision-related work
- AI should automatically apply patches when pulling/syncing
- Remove the manual friction of remembering to export/apply
- [ ] **Auto-export on commit**
- Before any commit that touched decision-related code, auto-run `deciduous diff export`
- Use branch-specific patch files (e.g., `.deciduous/patches/$(whoami)-$(branch).json`)
- Include patch file in the commit automatically
- [ ] **Auto-apply on pull**
- After `git pull`, detect new `.deciduous/patches/*.json` files
- Automatically apply them (idempotent - safe to re-apply)
- Report: "Applied 3 patches from teammates: alice-feature.json, bob-fix.json, carol-refactor.json"
- [ ] **Git hooks for automation**
- `post-commit` hook: auto-export current branch's decisions
- `post-merge` hook: auto-apply any new patches
- `pre-push` hook: ensure graph is synced and patches are committed
- [ ] **Claude/Windsurf workflow updates**
- Update tooling templates to include auto-sync behavior
- AI should do this automatically, not wait for user to ask
- "Before pushing, I'll sync the decision graph..." should be default behavior
- [ ] **Conflict resolution**
- When patches have conflicting nodes, use change_id to merge intelligently
- Prefer latest timestamp when edges conflict
- Interactive resolution mode if needed: `deciduous diff resolve`
### Context Recovery (Critical)
*Make compaction restore actually work reliably*
- [ ] `/context` command fully restores working state after context loss
- [ ] Query decision graph for recent goals, decisions, actions in progress
- [ ] **Sort nodes by recency** - most recently updated nodes first
- Use `updated_at` timestamp for sorting
- Show N most recent chains (like DAG view recency filtering)
- Recent activity is most relevant for context recovery
- [ ] Show what was being worked on, what's complete, what's pending
- [ ] Include recent git activity, uncommitted changes, branch state
- [ ] Pull in relevant prompts from history if available
- [ ] Goal: new session can pick up exactly where the last one left off
---
## Backlog - Core Features
### Commit-Centric Graph Navigation
- [ ] More robust per-commit tooling
- Link nodes to commits more reliably
- Auto-detect commit context when logging actions/outcomes
- `deciduous add action "..." --commit HEAD` should be the default flow
- [ ] Commit-centric browsing in the web viewer
- Browse graph starting from commits (not just nodes)
- Show which nodes are associated with each commit
- Timeline view organized by commit history
- Click a commit → see the decision subgraph around it
- [ ] `deciduous log` command to show commits with their linked nodes
- [ ] Integration with `git log` to annotate commits with decision context
### Web Viewer - URL State & Sharing
- [ ] **Query param encoding for shareable state**
- Encode ALL view parameters in URL query string
- Branch filter, selected node, view type, expanded chains, etc.
- Copy URL → share with teammate → they see exact same view
- Support deep linking to specific nodes: `?node=42&branch=feature-x`
- Persist state across page refreshes
- "Copy link" button in UI for easy sharing
### Web Viewer - DAG + Timeline Split View
- [ ] **Split view showing DAG and Timeline together**
- DAG view on one side, Timeline on the other
- Selecting a node group in DAG highlights corresponding timeline entries
- Swap panels in/out - view decision flow and log simultaneously
- Useful for reviewing decision history while seeing structure
- Configurable split direction (horizontal/vertical)
### Web Viewer - PR Integration
- [ ] **Link PRs to branch-filtered decision graph views**
- Click a PR link → opens deciduous web viewer filtered to that branch's nodes
- URL format: `deciduous.site/graph?branch=feature-foo` or similar
- PR description can embed a link that auto-filters the DAG to just that branch
- Users can explore the decision reasoning alongside the PR diff
- Integrate with GitHub PR template to auto-include graph link
- [ ] **GitHub App / Action for PR annotations**
- Automatically comment on PRs with link to branch-filtered graph
- Badge showing number of decision nodes in the branch
- One-click navigation from PR → decision graph explorer
- [x] **DAG recency filtering** (December 2025)
- Default view shows only 4 most recently active goal chains
- Chains sorted by most recent node update time within the chain
- "Show more" and "Show all" controls to expand view
- Rust utility functions for TUI (`build_chains`, `sort_chains_by_recency`, `get_recent_chains`)
### TUI Enhancements
- [ ] **Phase 2: Multi-goal chains**
- Navigate between related goals
- Show how goals connect and depend on each other
- [ ] **DAG view improvements** (currently disabled)
- Better hierarchical layout algorithm
- Zoom and pan controls
- [ ] **Settings system** (partially done)
- [x] `.deciduous/config.toml` exists with branch settings
- [ ] Timeline order default (newest-first vs oldest-first)
- [ ] Editor preference (`$EDITOR` fallback chain)
- [ ] Color theme selection
- [ ] Key binding customization
- [ ] Database path configuration
- [ ] **Keyboard shortcut audit and redesign**
- Analyze all current shortcuts for intuitiveness
- Ensure shortcuts are discoverable and memorable
- Consider user expectations from similar tools (vim, lazygit, ranger)
- Group related actions with similar key patterns
- [ ] **Visual discoverability**
- Add context-sensitive help hints in footer
- Show available actions for current context
- Highlight keyboard shortcuts in help overlay
- Consider modal indicator showing current mode prominently
- [ ] **Onboarding experience**
- First-run tutorial or guided tour
- Progressive disclosure of advanced features
- Cheat sheet generation (`deciduous tui --help-keys`)
### Code Tracking & File Associations (Extended)
- [ ] **Web UI: "View Code" button on nodes**
- Click a node → see associated files
- Show git diff for the commit linked to that node
- Quick navigation to file locations
- [ ] Update `.claude/commands/` and `.windsurf/rules/` templates
- Include instructions to log file associations
- `deciduous add action "..." --files <changed-files>`
- [ ] `deciduous files <node-id>` command to list associated files
- [ ] Reverse lookup: `deciduous nodes --file src/foo.rs` to find nodes touching a file
### Prompt Tracking (Extended)
- [x] **View prompts in web UI**
- Display the original prompt in node detail panel
- [ ] Prompt history view in web UI
- See what prompt led to each decision chain
- Search/filter by prompt content
- [ ] Prompt templates
- Save effective prompts for reuse
- Share prompt patterns that lead to good decision trees
- [ ] Prompt → Outcome analysis
- Correlate prompt patterns with successful outcomes
- Identify which prompt styles lead to better decisions
- [ ] **Extended prompt features in web UI**
- Filter/search nodes by prompt content
- "Copy prompt" button for reuse
---
## Backlog - Tooling & Automation
### Release Tooling
- [ ] **Automated release notes generation**
- `deciduous release-notes --from v0.7.0 --to v0.8.0`
- Query graph for all goals/outcomes between versions
- Group by feature area (TUI, sync, export, etc.)
- Generate markdown summary of what changed and why
- [ ] **PR tagging for releases**
- Tag PRs that landed in a release
- `deciduous release tag-prs v0.8.0` - adds label to all PRs in release
- Link PRs back to decision graph nodes
- [ ] **Release summary from decision graph**
- Walk the graph to find all completed goals since last release
- Show the decision chain that led to each feature
- Include key prompts/feedback that drove changes
- Generate changelog with decision context
- [ ] **GitHub Actions CI/CD for releases**
- Automate the entire release pipeline via GitHub Actions
- Trigger: push tag matching `v*` pattern (e.g., `v0.9.0`)
- Pipeline steps:
1. Run `cargo test` and `cargo clippy`
2. Build release binaries for multiple platforms (linux, macos, windows)
3. Create GitHub Release with auto-generated notes
4. Publish to crates.io (`cargo publish`)
5. Upload platform binaries as release assets
- Workflow file: `.github/workflows/release.yml`
- Optional: Separate workflow for nightly/canary builds
- Consider: cargo-dist or release-plz for Rust-specific release automation
- [ ] **Release checklist automation**
- `deciduous release prep v0.9.0` - prepare release locally
- Bump version in Cargo.toml
- Update CHANGELOG (if exists)
- Run tests and clippy
- Generate release notes from decision graph
- `deciduous release publish v0.9.0` - trigger the release
- Create and push git tag
- GitHub Actions takes over from there
- Fail-safes: block release if tests fail or graph has incomplete goals
### Roadmap Manager Tool
- [ ] **Link roadmap items to work**
- Roadmap items should link to decision graph nodes
- Track progress through the graph (goal -> decisions -> outcomes)
- Show completion status based on linked outcomes
- [ ] **Work item integration** (future)
- Design with external ticketing in mind (JIRA, Linear, GitHub Issues)
- Roadmap items could link to external tickets
- Sync status bidirectionally
- Keep this extensible for enterprise workflows
- [ ] **CLI commands**
- `deciduous roadmap list` - show roadmap items and their status
- `deciduous roadmap link <item> <node-id>` - link to graph node
- `deciduous roadmap status` - show completion based on linked nodes
### Claude Code Hooks Integration
- [ ] Explore using Claude Code hooks to guarantee workflow behavior
- Claude Code supports hooks that run on various events (tool calls, messages, etc.)
- Could enforce decision graph logging more reliably than instructions alone
- [ ] **Pre-tool hooks**: Before file edits
- Auto-log `action` node when Claude is about to modify files
- Capture which files are being changed
- Block edits if no active goal exists in the graph
- [ ] **Post-tool hooks**: After successful operations
- Auto-log `outcome` nodes after code changes succeed
- Auto-link outcomes to their parent actions
- Trigger `deciduous sync` after significant changes
- [ ] **Pre-commit hooks**: Before git commits
- Verify graph integrity (no orphan outcomes/actions)
- Require at least one goal node for the current session
- Auto-add commit hash to recent action/outcome nodes
- [ ] **Session start hooks**: On conversation begin
- Auto-run `/context` equivalent
- Load graph state and surface pending decisions
- Warn if there are disconnected nodes needing attention
- [ ] **Prompt submit hooks**: When user sends a message
- Detect feature requests and auto-create goal nodes
- Capture original prompt in node metadata
- [ ] Hook configuration in `.deciduous/hooks.toml`
- Enable/disable specific hooks
- Configure strictness (warn vs block)
- Custom hook scripts for project-specific needs
- [ ] Document hook setup in Claude Code settings
- Integration guide for `.claude/settings.json`
- Example hook configurations for different workflow styles
### Editor Memories Integration
- [ ] **Actually save memories correctly at runtime**
- Windsurf creates memories during runtime - need to patch into that flow
- Currently memories are static; need dynamic memory creation as decisions happen
- Investigate Windsurf's memory creation API/mechanism
- Hook into the runtime to persist decision context as memories are created
- Ensure memories reflect real-time decision graph state
- [ ] **Leverage Claude Code and Windsurf memories**
- Both editors have "memories" features that persist across sessions
- Could store decision graph summaries, recent goals, key patterns
- Auto-populate memories with recent decision context
- Memories could include: current goals, pending decisions, recent outcomes
- [ ] **Claude Code memories**
- Detect and update `.claude/memories/` or equivalent
- Store project-specific decision patterns
- "Last session worked on goal #X, consider continuing"
- [ ] **Windsurf memories**
- Already have `.windsurf/memories.md` template
- Enhance with dynamic decision graph summaries
- Auto-retrieve relevant memories when starting sessions
- [ ] **Memory-graph sync**
- `deciduous memories export` - export decision summaries to memory format
- `deciduous memories update` - update editor memories with recent decisions
- Bidirectional: memories inform context recovery
### Roadmap Skill & TUI Integration
- [ ] **Claude Code skill for roadmap management**
- `/roadmap` skill to interact with ROADMAP.md and decision graph
- Show current roadmap items, their status, linked nodes
- Add/update roadmap items with decision graph links
- [ ] **TUI roadmap view**
- New view in `deciduous tui` for browsing roadmap items
- Show roadmap items linked to decision graph nodes
- Filter by status (completed, in progress, backlog)
- Navigate from roadmap item → linked goal/decision nodes
- [ ] **Roadmap-graph bidirectional links**
- Roadmap items can reference graph nodes by ID
- Graph nodes can link back to roadmap items
- Track completion: roadmap item is "done" when linked outcome exists
### Retroactive Commit Association
- [ ] **Audit existing nodes and associate with git commits**
- Many early nodes were created without `--commit` flag
- Cross-reference node `created_at` timestamps with `git log` dates
- Match node titles/descriptions to commit messages
- `deciduous audit --associate-commits` command to suggest matches
- Interactive mode: show node + candidate commits, let user confirm
- Batch mode: auto-associate high-confidence matches (>90% title similarity)
- [ ] **Backfill script for existing graphs**
- One-time migration to enrich old nodes with commit data
- Parse commit messages for keywords matching node titles
- Use time windows (node created within N minutes of commit)
- Generate report of associations made
- [ ] **Ongoing commit detection**
- When running `deciduous sync`, detect recent commits without linked nodes
- Suggest: "Found 3 commits with no linked decisions - want to associate them?"
- Help maintain commit-node linkage going forward
### Git Integration & Pre-commit Hook Awareness
- [ ] Inspect and respect pre-commit hooks
- Detect `.git/hooks/pre-commit` or `.husky/` hooks
- Parse hook contents to understand what checks run
- Warn users if hooks might reject commits (linting, formatting, tests)
- [ ] Pre-flight commit validation
- `deciduous commit --dry-run` to simulate what hooks would do
- Show which checks would pass/fail before actual commit
- [ ] Auto-fix integration
- If hooks run formatters (prettier, rustfmt), detect and apply fixes
- Re-stage auto-fixed files before commit
- [ ] Hook-aware templates
- Update `.claude/commands/` and `.windsurf/rules/` to mention pre-commit awareness
- Instruct LLMs to check for hooks before committing
### Git.log File Reliability
- [ ] Investigate why git.log file isn't always being created/updated
- User reported missing git.log during session
- This file should always exist and track all git commands run
- [ ] Ensure git.log is created on `deciduous init`
- [ ] Add git.log writing to all git-related operations
- [ ] Consider moving git.log into `.deciduous/` directory for better organization
- [ ] Add `deciduous log` command to view git.log contents
- [ ] Document git.log purpose and location in tooling files
### Template Sync (init.rs ↔ actual files)
- [x] **FIX: `deciduous update` destroys custom content in command files** (v0.8.2)
- ~~Currently `update --claude` overwrites `.claude/commands/*.md` completely~~
- ~~This destroys all custom instructions users have added~~
- Fixed: init.rs templates now match actual files
- [ ] **Auto-detect when tooling files are out of sync**
- When `.claude/commands/*.md`, `.windsurf/rules/*.md`, `CLAUDE.md`, or `AGENTS.md` are modified
- Remind/enforce updating corresponding templates in `src/init.rs`
- The templates in init.rs should match what's in the actual files
- [ ] **Validation command**
- `deciduous validate-templates` - check if templates match actual files
- Warn if they've diverged
- Optionally auto-update init.rs from actual files
- [ ] **Memory/hook for sync**
- Add to Claude Code memories: "If you modify .claude/commands or CLAUDE.md, also update src/init.rs templates"
- Could be a pre-commit check or a deciduous hook
- [ ] **FULLY AUTOMATE template sync** (Critical)
- **Goal: Never manually sync templates again**
- Build script or CI step that extracts actual file contents into init.rs
- Single source of truth: the actual `.claude/`, `.windsurf/`, `CLAUDE.md`, `AGENTS.md` files
- `src/init.rs` templates are auto-generated from these files
- Options:
- `build.rs` script that reads files and generates template constants
- Pre-commit hook that regenerates init.rs template section
- CI check that fails if templates don't match actual files
- Include ALL tooling files:
- `.claude/commands/decision.md`
- `.claude/commands/context.md`
- `.windsurf/rules/decision.md`
- `.windsurf/rules/context.md`
- `CLAUDE.md`
- `AGENTS.md`
- Never have drift between what `deciduous init` creates and what the repo actually uses
---
## Backlog - Architecture & Quality
### TUI Architecture Refactor
- [ ] **Functional core, imperative shell**
- Extract pure functions from app.rs for all state transformations
- Move all I/O to thin imperative shell at edges
- State transitions should be pure: `fn update(state: App, event: Event) -> App`
- [ ] **Comprehensive test coverage**
- Unit tests for all pure state transformation functions
- Test navigation logic without terminal
- Test modal state machines
- Test filtering and search logic
- Property-based tests for state invariants
- [ ] **TEA pattern enforcement**
- Strict Model/Update/View separation
- No side effects in view functions (already done, verify)
- Event handlers return new state, don't mutate
- Extract reusable update functions
### Type Unification (TUI + Web)
- [ ] **Shared type definitions**
- Unify TUI types (src/tui/types.rs) with web types (web/src/types/graph.ts)
- Single source of truth for node/edge structures
- Consider code generation or shared schema
- [ ] **Port TUI features to web viewer**
- Timeline view with vim-style navigation
- Commit modal with split-view diff
- Branch filtering and fuzzy search
- Goal story view
- [ ] **Parallel development workflow**
- Changes to one should auto-update the other
- Shared test fixtures for both platforms
- Document the type mapping
### Documentation Restructure
- [ ] Rethink the `docs/` folder organization
- Currently: GitHub Pages viewer lives here
- Problem: Also contains ad-hoc design docs (like MULTI_USER_SYNC.md)
- Consider: Separate `docs/` (user-facing) from `design/` (internal design docs)
- Consider: Move viewer to dedicated folder
- [ ] Consolidate documentation
- Single source of truth in CLAUDE.md (the canonical reference)
- .claude/commands/ and .windsurf/rules/ derive from CLAUDE.md patterns
- README.md stays user-facing (installation, quick start)
- [ ] Auto-generate tooling docs
- `deciduous docs` command to output markdown documentation
- Include all commands, options, examples
- Keep README.md and tooling files in sync automatically
---
## Backlog - Future Vision
### TUI PR Review Mode
- [ ] **GitHub PR integration in TUI**
- Pull in PR comments from GitHub API
- Show file-level and line-level comments alongside code
- Browse commits in PR context with associated comments
- Mark comments as resolved/addressed from TUI
- Reply to comments directly from TUI
- [ ] **Code review workflow**
- Navigate between commented locations
- Jump from decision node to related PR/commit comments
- See review status and approval state
### LLM Critique & Analysis
- [ ] `deciduous critique --goal <id>` - Have an LLM analyze a goal's decision chain
- Review decisions made, options chosen/rejected
- Identify potential blind spots or unconsidered alternatives
- Evaluate confidence levels vs actual outcomes
- Suggest improvements for future similar decisions
- [ ] Multi-model critique comparison
- `deciduous critique --goal <id> --models claude,gpt4,gemini`
- See how different models evaluate the same decision chain
- Highlight where models agree/disagree on quality
- [ ] Critique storage - save critiques as special nodes linked to goals
### LLM Benchmarking Framework
- [ ] **Goal-based benchmarking**: Use the same goal/task across multiple LLMs
- Define a goal with acceptance criteria
- Run each model on the same task
- Compare: decisions made, paths taken, outcomes achieved
- [ ] `deciduous benchmark` command
- `deciduous benchmark --task "Implement feature X" --models claude,gpt4,gemini,llama`
- Each model gets isolated graph namespace
- Automated or human evaluation of outcomes
- [ ] Metrics to capture:
- Decision quality (did they consider good options?)
- Path efficiency (how direct was the route to outcome?)
- Confidence calibration (were high-confidence decisions correct?)
- Recovery ability (how did they handle setbacks?)
- Graph structure (complexity, dead ends, backtracking)
- [ ] Benchmark reports
- Side-by-side comparison of decision graphs
- Aggregate stats across multiple benchmark runs
- Export to shareable format for publishing results
- [ ] Reproducible benchmark suites
- Define standard tasks with known-good solutions
- Version-controlled benchmark definitions
- CI integration for regression testing model capabilities
### DuckDB for OLAP Analytics
- [ ] Add DuckDB as optional analytical backend for decision graph queries
- SQLite is great for OLTP (single-project, real-time logging)
- DuckDB excels at OLAP (cross-project analytics, time-series queries, aggregations)
- [ ] Use cases for analytical queries:
- **Cross-project patterns**: "What decision patterns lead to successful outcomes across all my projects?"
- **Time-series analysis**: "How has my decision-making evolved over the past 6 months?"
- **Confidence calibration**: "Are my high-confidence decisions actually more successful?"
- **Path analysis**: "What's the average depth of decision trees that lead to good outcomes?"
- **Bottleneck detection**: "Which decision types take longest to resolve?"
- [ ] Implementation ideas:
- Export SQLite graphs to Parquet files for DuckDB ingestion
- `deciduous export --parquet` for analytical snapshots
- `deciduous analytics` subcommand for running OLAP queries
- Optional: federated queries across multiple project databases
- [ ] Potential analytical views:
- Decision funnel analysis (goal → decision → action → outcome conversion)
- Confidence vs outcome correlation matrix
- Branch/feature complexity metrics
- Session productivity heatmaps
- Node type distribution over time
- [ ] Visualization integration:
- Export to formats compatible with BI tools (Metabase, Superset, etc.)
- Built-in charts in TUI or web viewer
- `deciduous report` to generate analytical summaries
---
### Live Graph Diff Viewer
- [ ] **Real-time graph following**
- Diff viewer that "follows" the decision graph as nodes are written
- User sees live updates as AI creates/modifies nodes
- Stream-style view of graph changes in real-time
- Could use websocket or file watching to detect changes
- TUI mode: live refresh every N seconds or on file change
- Web mode: push updates via SSE or websocket
- [ ] **Visualization of graph deltas**
- Show what nodes/edges were added, modified, deleted
- Highlight new nodes with a visual indicator
- Animate transitions between graph states
- Timeline scrubber to replay graph evolution
- [ ] **Integration with editor workflows**
- Side panel in IDE showing live graph updates
- Works alongside Claude Code, Windsurf, Cursor
- Non-blocking: viewer runs in separate process/terminal
### Live Graph Editor (Experimental)
- [ ] **Bidirectional graph editing**
- Not just viewing - actually edit the graph live
- Add/modify/delete nodes through the viewer UI
- Changes sync back to SQLite database
- Potentially coordinate edits with running AI session
- [ ] **Collaborative editing**
- Multiple users can edit graph simultaneously
- Operational transform or CRDT for conflict resolution
- Real-time cursor presence (see where others are editing)
- This is ambitious but could enable pair programming with AI
- [ ] **Graph manipulation tools**
- Drag and drop nodes to reorganize
- Quick actions: merge nodes, split nodes, reparent
- Undo/redo support
- Validation: prevent invalid graph structures
---
## Future Enhancements
- [ ] Support for additional editors (Cursor, Copilot, etc.)
- [ ] `deciduous init --all` to bootstrap for all supported editors at once