Your terminal, in blocks that explain themselves
by•
I built Verlox because Al terminals have a trust problem. They run things, scroll fills the screen, and you're left reconstructing what actually happened,
Blocks is my answer https://www.verlox.app.
Every command you run becomes its own card with the command, its output, and a quiet line that tells you the outcome in plain English.
No digging through scrollback to figure out whether something worked.
A few things I'm proud of in this release:
Fix this. When a command fails, one button sends that exact run, the command plus its own output, to the Al and it gets straight to work on a fix. Not "the last thing on screen", the specific block you clicked. Run the same command twice and each block keeps its own story.
Explain. On any successful block, one click generates a plain English explanation of what the command did, rendered right inside the card with the model that wrote it credited underneath, No tokens are spent unless you ask.
Reversibility you can see.
If a command deleted or changed files that Verlox captured, the block shows a Restore button wired to the Recovery Vault. The promise isn't "trust the Al", it's "here's the undo".
Suggested next steps.
Ran git add? The block offers git commit, Ran nom install? It offers nom start. Small thing, saves a surprising amount of typing, "
Everything the.Al does in Verlox is plan first, approve before run, and recorded on a timeline. Blocks brings that same transparency down to every single command.
Would love your feedback, especially on what a block should show that it doesn't yet.
Replies