Path one: sign the agent in yourself
Claude Code, Codex and OpenCode each have their own sign-in. If you have already signed one in on that machine, Myrax uses it and never sees the credential. The dashboard shows the engine as ready because the agent reported a working credential, not because Myrax holds one.
This is the path to prefer. Nothing about your account passes through a server.
Path two: save a key in Providers
If an agent is installed but not signed in, the dashboard says “needs a sign-in” and you can save an API key instead. That key is written to a file on the paired computer and passed to the agent as an environment variable for that run only. It is not stored in the Myrax database.
The provider list covers the major direct APIs and the aggregators, plus a custom entry for anything that speaks an OpenAI-compatible shape.
Checking a key before it costs you a build
The Providers page validates a key against the provider before saving it, so a typo surfaces immediately instead of ten minutes into a build. Some providers return a narrower answer than you expect, for example a key that can send mail or complete a request but cannot list account resources. A validation that succeeds with “restricted key” is still a working key.
Where keys are not
- Not in the database. Provider keys live on the machine that runs the agent.
- Not in the artifact.
.env,*.pemand*.keyare filtered out of every export. - Not in a build log. Lines that look like
key=,secret=,password=ortoken=are redacted before a diff leaves the machine.
The trap worth knowing
A key and an account balance are different things. Providers that meter credit will accept a request and then refuse it with a billing message when the account is empty, and the error arrives mid-run, not at validation. If a build fails after a few seconds with a message about credits or max_tokens, the key is fine and the balance is not. That is a provider problem, not a Myrax one, and the fix is on the provider's dashboard.
Which engines exist and what each needs: Engines. What stays on your machine: Where your code runs.

