Markdown Inbox

Let's say you're a developer using Claude Code daily. Here's a typical week:

• Monday: Claude generates 3 design docs for a new feature
• Tuesday: You export 2 debugging sessions for reference
• Wednesday: Claude writes a test plan and architecture overview
• Thursday: 2 more code review summaries
• Friday: Claude produces migration documentation

That's 10+ documents in a week. Without a system, they pile up.

With Markdown Inbox:

• You see 10 unread items in your queue
• You process them during dedicated triage time
• You tag the architecture doc (important for reference)
• You archive the debugging sessions (useful once, don't need again)
• You hit zero by Friday evening

Monday starts fresh. No accumulated guilt. No mystery pile.