Connect your model, work in a project with explicit approvals, add extensions when needed, or apply organization policy to the same local developer experience. Developer alpha.
npm install -g @moxxy/cli
cd your-project
moxxyOn first start, moxxy asks you to choose one model connection and authenticate. It selects the recommended model and runtime defaults automatically, then opens the TUI. You do not need a config file, channel, service, compactor, cache strategy, embedder, or isolator to begin.
Start with a read-only task, then ask for a small change. Moxxy keeps the run in the workspace, reads safely resolved workspace paths without ceremony, and shows the target and impact of writes and commands before they execute.
| Personal developer | Governed workstation |
|---|---|
| Choose a model account | Use organization-approved model connections |
| Add optional extensions | Allow only approved extensions |
| Approve consequential tools | Apply centrally supplied policy |
| Keep local run history | Produce identity-bound, inspectable receipts |
Governed use is a developer-alpha design-partner preview. It is not yet a fleet control plane, compliance certification, or production SLA.
Extension authors and advanced operators can replace providers, modes, tools, compactors, cache strategies, embedders, isolators, channels, event stores, and audit sinks through the typed @moxxy/sdk contract. That flexibility remains a strength of the runtime; it is progressively disclosed instead of becoming first-run configuration.
| If you want to | Read |
|---|---|
| Complete a first useful task | Quickstart |
| Test the alpha and give feedback | Developer alpha |
| Add a lightweight procedure | Authoring a skill |
| Build a code extension | Authoring a plugin |
| Apply organization controls | Governed workstations |
| Understand the runtime internals | Architecture |