Octopus

Octopus

The Claude Code frontend for ADHD developers.

You launched 15 Claude Code sessions. Three need permission. One is waiting for a decision. Two finished and need PRs. You forgot about the one that's been stuck for 20 minutes. You opened Twitter "for a second" and now it's been 40 minutes.

Octopus is your external working memory. It keeps track so your brain doesn't have to.

The problem

Claude Code is powerful. You can run dozens of sessions in parallel, each one writing real code. But the bottleneck was never Claude — it's you. Reading terminal output. Switching tabs. Checking CI. Typing responses. Clicking merge. At 5 sessions it's fine. At 20, you're drowning. At 50, you've mass-replied "y" to things you didn't read.

If your brain works like ours, this hits even harder. Every context switch costs you 20 minutes. "I'll come back to that session" means it's gone forever. The dopamine of launching 10 sessions wears off fast when you have to babysit all of them. You need a system that watches everything so you can hyperfocus on what actually matters.

What Octopus does

One window. Zero tab-switching. Every session from dispatch to merge.

Features

Stay focused
- Dispatch board — Kanban columns: Running, Needs Attention, Done. No session gets forgotten.
- Smart attention signals — See *what* Claude is asking (permission? confirmation? question?) without reading the terminal
- Session recaps — AI-generated summaries so you don't re-read 200 lines of output to remember where you left off
- Quick reply — Allow/Deny buttons and freeform reply, right from the board. No context switch needed.

Ship without leaving
- Full pipeline — Issue → Session → Code → PR → CI → Merge → Close. Zero visits to github.com.
- Git operations — Stage, commit, push with status…