A real workflow
This website. Built in the conversation.
Here is what working through VibeCommand actually looks like. We used its Chat to improve the page you are visiting, then checked the result in LIVE.
Ask for a change. See it on the page.
We opened this website as a VibeCommand project and asked Codex to improve its homepage. The conversation and the running page stayed side by side.
Actual Mac app captures. This website is the project shown; the agent edited its original files.
FROM REQUEST TO RESULT
Small changes.
Visible progress.
- 01
Open the real project.
We added the existing website folder, selected Codex and sent the first task through VibeCommand’s own CLI. The app showed the same conversation.
- 02
Refine the homepage.
The agent widened the responsive layout, updated the headline and added a three-step explanation. A follow-up integrated the original transparent VibeCommand logo.
- 03
See the change in LIVE.
We asked for “Your idea. Your Mac. One conversation.” above the headline. The text appeared on the running page and remained visible when we expanded LIVE.
- 04
Check the work and continue.
Terminal history exposed the build and lint results. We used the next message to fix internal navigation issues, keeping the conversation connected to the actual files.
Something outside a project? Open Mac Assistant to investigate the Mac itself or prepare a new project. The workflow shown above is a real project session; Mac Assistant has a separate conversation.
THE NEXT STEP
Built for the way
you already work.
Explore the setup, see what is being tested, and help shape VibeCommand.