The problems
In March 2026 my back began to hurt a lot more than usual. I had a standing desk and I was reasonably active, and it still was not enough: the hours of sitting were more than my body was willing to take. That is when I started looking at voice — at working without a chair, a desk, or a keyboard at all.
Independently, I noticed I was nowhere near using the Claude quota I was paying for, on the $100 plan. The reason was not the model, it was me: I was running one task at a time, by hand — hardly the best use of it — and nothing about the way I worked could run in parallel. Voice looked like the answer here too: put it in front of a board, and one conversation could feed several agents.
The solution
To me the solution was clear: a board that I could control with my voice, hands free. The voice is what gets me out of the chair. The board is what lets the work run in parallel.
Two weeks later, I had my first success. Earbuds in, phone in a pocket, I was able to talk to Claude and Opencode directly from my phone. Whisper transcribes on my own Mac, the text goes to claude -p or opencode run, and the reply is read out on the phone. All running on the subscription I already pay for. Nice!
Worst case, I had built myself a decent way to work. Best case, a product. I would have taken either.
What changed
From then on the desk stopped being where the work happened. On a walk, I describe the next thing to the agent and it becomes a ticket. Once a ticket is specified, I drop it into ready: a worker picks it up, checks it out in a git worktree of its own, and builds it while I am somewhere else. The conversation is one at a time; the work is not. I am usually describing the next feature while the last one is opening its pull request.
Now I spend at least an hour a day "vibewalking" — outside, walking, and still working — and my back has noticed. That was the whole point. The quota problem is gone, in the other direction. I hit the ceiling of my Claude plan, upgraded to the $200 one, and I hit that too. Squad33 is built with Squad33: most of what has shipped since was described on a path.
The surprise is that some days I get more done on a phone, outside, than I do at the desk. Not because I run more at once — it is still one conversation — and not mainly because talking is faster. It is that reading and reviewing what an agent produces is draining in a way that listening to it is not. And I go deeper by voice: there is no keyboard fatigue, the thing that quietly stops me from typing the extra details.
Go outside
Squad33 is a free beta, it is macOS, and it drives the Claude Code or Opencode subscription you already pay for — it ships no model access of its own. Download it, pair your phone with the QR code, and go outside.
— Benoit Hirbec, squad33.ai
Top comments (1)
Putting each ticket into its own git worktree is what keeps this workable. Whenever I kick off parallel runs from quick notes, the failure mode is almost always dirty working trees stepping on each other when two branches touch the same dependencies. Isolating them by default saves hours of untangling merge garbage later.