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.

Recall

$ uro recap --days 7

See what happened. Instant context.

Search

$ uro search "auth"

Find past decisions by keyword.

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

Scrollable browser timeline with compact mode that collapses rest periods. List and horizontal views.

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.

Claude Code Integration

Auto-capture without thinking about it

When you use Claude Code with the uroboro MCP server, decisions get captured automatically as you work.

  • uro_decision — Captured when Claude makes architectural choices
  • uro_blocker — Logged when work is blocked on external factors
  • uro_question — Saved when open questions are deferred
  • uro_capture — General context capture with tags
  • uro_recap — Claude checks context at session start
  • uro_search — Search past captures by keyword

One command to set up:

claude mcp add uroboro --scope user -- uroboro mcp

Then in ~/.claude/CLAUDE.md, tell Claude to use the tools automatically.