Every CLI tool has this problem at some point: the parser eats an argument that was meant for something else. Gitlawb Zero just fixed one of the most annoying instances of this.
The Bug
When you ran Zero with a flag that takes a value, the parser would sometimes consume the next positional argument as the flag’s value.
Example:
zero --model gpt-4 myfile.txtBefore the fix, myfile.txt might get consumed as part of --model’s value instead of being treated as a positional argument. The result: the file never gets processed.
The Fix
fix(cli): prevent consuming positional arguments as flag values (#619)
The fix adds proper boundary detection between flag values and positional arguments. The parser now correctly distinguishes between:
--flag value(flag with value)--flag value positional(flag with value + positional)value positional(two positionals)
Why This Matters
CLI parsing bugs are frustrating because they break the most basic workflows. You type a command exactly as documented, and it does something unexpected. The fix is invisible — commands now do what you typed. But that’s exactly the point: good infrastructure is invisible.
What This Means
Zero’s CLI is now more reliable. Flag-heavy commands (which Zero has many of) work as expected. For users scripting Zero or integrating it into workflows, this eliminates a class of silent bugs.
Related articles
- Gitlawb Zero Deep Dive: The Decentralized Coding Agent You Own
- Beware: Your Coding Agents Sandbox Was Leaking Its Own Credentials to Spawned Commands
- Beware: Gitlawb Zero v0.4.0 Closed a Hole Where a Cloned Repo Could Re-Enable the MCP Servers You Disabled
Sometimes Claude writes better code. Sometimes GPT does. aiFiesta lets you compare both instantly in one chat for $12/mo — plus 7 more premium models.