How the toolkit fits together
Your agent builds the product. Fluxzero runs it. The local tools give you and your agent a working environment and evidence. Cloud delivery makes a checked version available to users.
From an instruction to a working app
Section titled “From an instruction to a working app”- Your agent
The plugin and MCP supply guidance and project tools.
- Dev Server
One environment manages apps, builds, tests and services.
- Devboard
You see the preview and the same development feedback.
The agent plugin gives your coding agent the Fluxzero workflow. Its MCP connection retrieves SDK guidance matched to the project and exposes development tools. The CLI creates projects and launches or manages their environment.
The Dev Server manages backend and frontend processes, local services, builds, affected tests and startup actions. Devboard is your browser view of that work: the app, tested scenarios, recorded progress and monitoring.
The SDK supplies the programming model used by application code. Developers can work directly in the same code; using an agent does not create a separate kind of application.
| What you want | Where to go |
|---|---|
| Prepare your coding agent | Agent plugin |
| Connect a client to Fluxzero tools | MCP |
| Use a terminal | CLI |
| Configure the development environment | Dev Server |
| Inspect the local application | Devboard |
| Implement application code | Developer Guides |
From a checked change to a live product
Section titled “From a checked change to a live product”- Build tooling
Package the application and publish its image.
- Delivery workflow
Request deployment through the Deploy Action or System API.
- Cloud dashboard
See the version, tasks, configuration and runtime evidence.
A GitHub workflow authenticates to Fluxzero before requesting deployment. The dashboard lets you and your agent inspect the result and the product’s behavior after release.
Your local project and live application have separate data and configuration. The plugin does not automatically grant production access. Identity for app users is also separate from the permissions used by a deployment workflow.
Use Tools & automation for installation and reference, Local and live environments for the boundaries, and Publishing your app for the release procedure.
© 2026 Fluxzero