An AI terminal companion for developers who know what they're building.
Build, understand, refactor, and ship without giving up control.
macOS · Linux · Windows
$ vibe-txt
> refactor the auth middleware and keep the existing API
Reading repository...Found 4 relevant files.
I'll update the middleware without changingthe public interface.
Apply changes? [Y/n]> It should remove everything between the idea and the implementation.
Use AI where it helps. Keep control where it matters.
human > prompt > inspect > ship
01
Give the AI your repository context.
Ask about architecture, dependencies, and unfamiliar code without manually hunting through files.
> how does billing talk to the queue?
src/billing/ · src/queue/worker.tsBilling publishes invoice.created, the workerconsumes it and retries with a backoff.02
Describe what you want, review the approach.
Describe what you want. Review the proposed approach. Apply only what you approve.
> add rate limiting to the public API
Plan: 3 files, 1 new middlewareToken bucket per API key, 60 req/min.Apply changes? [Y/n]03
Debug, refactor, and review in the flow.
Use the terminal to reason through failures, clean up code, and improve existing implementation.
TypeError: cannot read 'id' of undefinedat resolveSession (auth.ts:42)
Session is null on expired tokens.Suggested fix: guard before resolve.See what changes. Decide what runs. Keep control of your workflow.
@@ -18,7 +18,7 @@- const timeout = 3000;+ const timeout = config.requestTimeout;Ask. Inspect. Apply. Ship.
01
Describe the task directly in the terminal.
02
Review the plan, context, or proposed changes.
03
Choose exactly what gets changed.
04
Continue with your normal development workflow.
One terminal.
One conversation.
Less friction.
The strongest tools disappear into the work.
> find why checkout sometimes creates duplicate orders
Reading relevant files...Possible issue found in: src/services/checkout.ts src/api/orders.ts
The retry path can call createOrder twicebefore idempotency is checked.
> show me the safest fix
I would move the idempotency check beforethe retry branch and add a test for concurrent calls.
Open diff? [Y/n]> The interface should disappear into your workflow.
AI should solve the task, not perform for the user.
Every important change should remain understandable.
Designed for actual repositories, not only demos.