Developer alpha

The alpha tests one promise: a developer can install moxxy, connect a model account, complete useful work in a project, understand approvals, and resume the run without learning the runtime architecture.

Supported path

• Node.js 20.10 or newer on macOS and Linux;
• the desktop app on published installer platforms;
• Anthropic and OpenAI API keys;
• ChatGPT OAuth and an existing Claude Code subscription session;
• local read, edit, command, and search tools;
• approvals, persisted runs, and the default local memory path;
• optional extensions after the first successful run.

Experimental

• channel and background-service setup;
• collaboration, automations, voice, mobile, and agent-authored apps;
• third-party extensions and non-default runtime blocks;
• organization-wide enrollment and remote audit export;
• packaged desktop self-update across every environment.

These remain available behind advanced CLI commands or the desktop's More menu. They should not block personal onboarding.

Governed workstation profiles are a design-partner preview. Moxxy does not yet claim fleet management, compliance certification, or a production SLA.

Give useful feedback

For first-run feedback, include:

1. OS, architecture, Node version, and install method.
2. Selected model connection; never include a key or token.
3. Time from install to the first useful result.
4. The first task attempted and whether it completed.
5. Any word, decision, or approval that was unclear.
6. Whether the next launch resumed as expected.

Report reproducible bugs in GitHub Issues. Use GitHub Discussions for product feedback and use cases.

Exit criteria

The alpha can move forward when clean-machine smoke tests cover install, authentication, first read-only work, first approved write, and resume; most testers finish setup without editing config; and the dominant confusion is about task quality rather than product concepts.

Extension APIs may change during alpha. Release notes and package changesets document those changes.