Show HN: Aq – an attention queue TUI for Claude Code
Hi, here's a TUI we originally created for internal use. The goal is to be able to control multiple Claude Code sessions running in parallel while being able to review the changes and to understand the design choices the agents make. The key design principles are: - the programmer's attention is the bottleneck, so instead of cycling between sessions to find what's waiting for user input we use hooks to push work to the attention queue, i.e. let work come to you, not viceversa - easy change, revi
Read original source
Source record
Recorded metrics
points · 2 votes
2026-11-11 13:45:06.162Z
cumulative since publication
Research analysis
Project record
Repository: nodo-labs-uk/attention-queue. Source account: Hi, here's a TUI we originally created for internal use. The goal is to be able to control multiple Claude Code sessions running in parallel while being able to review the changes and to understand the design choices the agents make. The key design principles are: - the programmer's attention is the bottleneck, so instead of cycling between sessions to find what's waiting for user input we use hooks to push work to the attention queue, i.e. let work come to you, not viceversa - easy change, revi
Observed adoption & comparisons
Source votes: 2 votes (Nov 11, 2026 UTC; cumulative since publication) Recent records to compare: “[分享创造] 分享一个从视频里学知识的开源笔记本” (V2EX, Nov 12, 2026); “addyosmani/agent-skills” (GitHub Trending, Nov 12, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.