A lot of AI tools sell you on the model. Bigger context window, smarter reasoning, fewer hallucinations. We sell you on the moment after the model — the one-tap approval. The approval loop is the part of Helix we polished hardest, and it is the part that decides whether the agent is useful.
Why the approval is the bottleneck
A draft that takes 10 seconds to read is a draft that gets read. A draft that takes 90 seconds is a draft that gets skipped. Once a queue piles up, you stop using the agent and the entire investment evaporates.
So the approval loop has to be relentlessly fast. Not "fast for AI software" — fast in the way that swiping email on a phone is fast.
Three rules we follow
1. Approve in one tap. Edit in two. Skip with a swipe.
Three gestures total. No menus, no nested screens. Edit is approve held a beat longer; you land in an editor with the cursor at the right spot.
2. Show the next decision, not a list of options.
A ranked queue surfaces the single thread you are most likely to action. The pile is collapsed by default; you only see the next swipe. The v1 ranking uses heuristics (recency, sender, thread state) and runs client-side; per-identity learning is on the roadmap. The ranking never reads message bodies.
3. Make the agent show its reasoning briefly.
Below every draft sits a one-line "why this draft" — the rule from the template, the previous similar message, or the explicit instruction the user gave. The reasoning is collapsed; tap to expand. Most users never expand it, but the option is what makes them trust the system enough to approve fast.
What we cut to keep this simple
Long-form explanations beneath every draft. Multi-step "approve, then send, then confirm" flows. A weekly digest that batches up everything for review on Sunday — useful for some, but a different product. We pruned all three to keep the loop tight.
The result: an approval is one tap. A morning queue is one minute. The agent stops being a curiosity and starts being a tool.