ONE USEFUL FIRST STEP
Start with one clear loop.
Explore the workflow before connecting anything. The public demo and Windows companion preview are available; the full commercial installation and activation path is still in development.
See the idea without connecting an account.
The home-page example shows a project, a question, a recorded answer and a result for review. Try its scenarios and pause the motion whenever you like. It uses sample data and starts no agents.
Explore the guided example →A small preview, not the full installer.
The existing ZIP contains the separate Windows owl widget. Extract it and keep the widget and brand folders together. Follow the included widget/README.md; it describes Windows, .NET Framework 4.x and WPF requirements, plus start-widget.cmd and VabesWidget.exe.
The archive may carry earlier character naming and the natural appearance. It does not establish native support for every newer browser theme, a full commercial installation or a license entitlement.
For a supported local workflow.
- Choose a small outcome. Name one useful change, its boundaries and the checks that will show it works.
- Check your build and tool. The current local implementation targets Windows. Managed Codex is supported; imports of other existing cycles depend on their adapter and configuration. Your AI account is separate.
- Add the project deliberately. Choose its folder and the supported agent path. Saving a project or cycle is separate from starting it.
- Review before starting. Check permissions, limits, the stopping point and owner decisions. Start when the scope and supported setup are clear.
- Inspect the result. Read the recorded output, run the relevant checks and decide what to accept. Keep the next task bounded too.
These are workflow steps for a supported local build, not a promise that the preview ZIP includes the complete panel.
Activation comes with a verified release.
A product license, device activation and a clean installation experience belong to the commercial release. The existing WebMoon account is the account destination; opening it does not buy or activate Vabes.