Axel

The single-inbox approve/deny is the right primitive — the moment you run more than two agents, the bottleneck stops being the agents and becomes you context-switching between their approval prompts. Pulling them into one keyboard-driven queue is exactly the fix. The thing I'd want next is a graduation path off per-action approval: once an agent has done the same safe action twenty times, approving the twenty-first by hand is just tax. Some notion of "auto-approve this class of action for this agent, still log it" is where the inbox model really pays off — you keep the audit trail without staying the human bottleneck forever.

Approving or denying agent actions from one inbox is the piece I keep missing when I have a few agents running at once, and keeping it native and keyboard-driven fits that workflow well. Any plans for a Linux build?