Context Switching Kills Momentum

Sound familiar?

"Why did I do it this way?"

Staring at code you wrote last week
"What's the status on X?"

20 minutes digging through Slack
Interrupted mid-task

Restart from scratch
Great decision rationale

Lost in a chat thread forever

The Real Cost:

  • Re-explaining decisions—Same questions, different meetings
  • Repeated mistakes—Forgot why you avoided that approach
  • Slow ramp-up—Rebuilding context after vacation, sick days
  • Knowledge silos—Only you know why things work

Simple Capture. Instant Recall.

Three commands cover 90% of use cases

Capture

$ uro d "JWT over sessions — stateless"

Decisions, blockers, questions. 5 seconds. Backdate with --time.

Recall

$ uro recap --days 7

See what happened. Instant context.

Search

$ uro search "auth" --days 30

Filter by keyword, project, tags, branch, or date range.

Visualize Your Work

Three ways to see what happened

Timeline TUI

$ uro timeline

Interactive terminal UI with vim-style navigation. Filter by project, type, or keyword. Group by day.

Web Timeline

$ uro web --port 8080

Browser timeline with list, horizontal, and project views. Compact mode, presentation mode, diff mode, narrative pane, keyboard navigation, and standalone HTML export.

Graph View

$ uro graph --days 90

Canvas scatter plot of all activity. Projects on Y-axis, time on X-axis. Scales to thousands of days.

Export to JSON, HTML, Markdown, or CSV. Generate time reports for billing with uro report. Back up your data with uroboro backup.

Claude Code Integration

Auto-capture without thinking about it

Claude Code captures decisions as you work via MCP. Enforcement hooks audit capture compliance and nudge during long sessions. Per-project .claude/uroboro.tags files define tagging conventions.

  • uro_decision — Record architectural choices with reasoning and alternatives
  • uro_blocker — Log blockers with what you're waiting on
  • uro_question — Save open questions for later
  • uro_capture — General context capture with tags
  • uro_recap — Load recent decisions, blockers, commits at session start
  • uro_search — Search captures by keyword, project, tags, date range
  • uro_stats — Aggregate statistics by tags, activity, or projects
  • uro_distill — Extract style signals from git commits and captures
  • uro_prompt_profile — Analyze Claude Code prompting patterns
  • uro_enforcement — Configure capture compliance hooks

Setup:

claude mcp add uroboro --scope user -- uroboro mcp
uroboro hooks install
uroboro init

Add the MCP server, install enforcement hooks, and create per-project capture conventions. Then in ~/.claude/CLAUDE.md, tell Claude to use the tools automatically.