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.

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_recap — Claude checks context at session start

Add to your Claude Code config:

{
  "mcpServers": {
    "uroboro": {
      "command": "uroboro",
      "args": ["mcp"]
    }
  }
}

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