Start with what you mean.
Choose the kind of thing you are making and describe it in your own words. Vibe Companion then asks only the questions that materially change the first build.
Build your app with AI without losing track of your project.
Vibe Companion turns a rough idea into a plain-language plan, shows what Codex is doing, and brings you back in when a real decision needs a human.
See the workflow
Working alpha · Private/local prototype
From “I have an idea” to “I know what happens next.”
The machinery can stay complicated. The experience should not.
-
1.0
Describe it
Start with the app in your head, in the language you already use. Vibe Companion accepts a new idea or an existing Codex workspace.
No package names required.
-
2.0
Review the plan
Codex proposes an ordered set of work. You can edit it, answer bounded product questions, and approve the plan before it reaches the board.
You see the shape before work starts.
-
3.0
Keep your place
Ideas, planned work, active builds, decisions and checks live in human labels such as Up next and Needs an action.
The board answers “where are we?”
-
4.0
Check the result
Launch a local preview, follow a practical checklist, see the evidence, and turn anything unfinished into the next clear piece of work.
Finished means checked.
See the idea become work you can follow.
These are real screens from the working alpha. They show the part I care about most: keeping the builder oriented while Codex moves from interpretation to implementation.
Inspect the plan before it becomes activity.
The idea becomes ordered work with a visible starting toolset. You can see what Codex thinks it is building, and why, before the first implementation card moves.
Let it move without letting it disappear.
Automatic work can continue while the project remains pausable and inspectable. Project chat stays close by, so an ordinary instruction can redirect or reorganise the work.
Fast is useful. Knowing when to stop is useful too.
Vibe Companion is designed to surface the moment when an apparently small choice changes the behaviour people will notice. Codex pauses, explains the decision, and waits.
Make the power visible. Put limits around it.
The goal is not to pretend AI-assisted work is simple. It is to make the important parts legible enough to supervise.
- 01 User language first
- Technical machinery is translated into the project, choice or problem it affects.
- So a builder can participate without learning a new profession first.
- 02 No finished without evidence
- A card is not complete just because the AI reports success. Results, checks and useful proof stay attached to the work.
- So progress means more than confident text.
- 03 Limits stay explicit
- Attempts, approval points and access to local work are scoped instead of disappearing behind an autonomy switch.
- So help does not quietly become control.
Local by design
The web app tracks the plan. A short-lived connection pairs it with a verified project folder on the builder’s own machine. The browser never receives arbitrary file or shell access.
Project status
Working alphaA public window, not a public trial.
Vibe Companion is a working private/local prototype. I am using it to explore a practical question: as AI-assisted building gets more capable, can the person doing the building stay oriented, make meaningful choices, and know when something is actually done?
This page shows the product direction and the thinking behind it. Public sign-up, cloud execution and team workflows are not part of the current alpha.
Make the complicated feel graspable.
If you are exploring a similar product, workplace or AI problem, I would like to hear about it.