Maxxwell has two distinct local inference paths. They are not interchangeable.
Use an installed coding-agent runtime
For the simplest start, install and sign in to Claude Code or Codex using that
tool’s own instructions. Then select the runtime:
When Maxxwell delegates to an installed vendor CLI, that CLI owns its sign-in.
Maxxwell records the selected runtime name; it does not copy the vendor’s login
into a Maxxwell account or hosted service.
Use a provider API key
maxxwell run can run a task through a configured provider API key:
Use maxxwell run --help in your installed build for its exact provider,
environment, model, cost, and approval options. Do not assume that a working
subscription login is equivalent to an API key or that credentials can be
moved between providers.
Local-use boundary
- Choose a credential deliberately; Maxxwell does not scan the machine merely
because a credential may exist.
- Ordinary local use does not require a Maxxwell account or hosted control
plane.
- A delegated vendor CLI may inherit the environment and files it normally
uses. Review that tool’s own authentication and permission model.
- Never place credentials in a repository, prompt, transcript, or bug report.
Provider and coding-plan terms differ. A technically working OAuth token or
subscription login is not evidence that it may be reused by another client.
Use each vendor’s supported authentication path.
