HN Explorer

Show HN: Aq – an attention queue TUI for Claude Code (github.com)

1 points by orbis-tertius ↗ HN
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, review and comment loop: [tuicr](https://tuicr.dev/}-inspired code reviews. Easy to add comments and send them to agents

- unobtrusive tooling: run on tmux sessions, connect to claude code via hooks, no complex dependencies

- quiz mode: answer design questions about the code to verify and reinforce your understanding of the changes

- keyboard-first navigation with vim keybindings

Comments, ideas and PRs all welcome!

6 comments

[ 0.23 ms ] story [ 8.3 ms ] thread
nicknaddaf
This is a very cool tool. I am doing this in a primitive way, in multiple VS Code instances or terminals, but sometimes I get confused and frustrated when working on several repos at the same time. However, I am looking for much more than that; I'm not sure if this tool already provides it, which is initializing and orchestrating several Claude Code sessions when working on a massive project with many repos.
orbis-tertius
Thanks! For now we just keep separate Claude Code sessions as separate independent windows. What feature would you like this to have? For example, the ability to organise windows/sessions together and have them push to the same attention queue?
sirallap-agentg
nice, same pain here. i usually have 5-10 claude code / opencode sessions in tmux and what kills me is the one stuck on a permission prompt while i'm looking at another one... in the end i only let the blocked ones notify me, the finished ones just wait in a list. do you treat those two differently?
orbis-tertius
Yeah we do actually.

In review or step mode they'd both get pushed to the queue, but if you set your sessions to vibe mode then you only get: - permission prompts (when Claude asks for permission) - option menus (when Claude asks you to pick between choices) - questions - menu cards (e.g. folder-trust questions)

You can change mode in your session with M.

Does this answer your question?