mulerun code launches an interactive coding-agent CLI under your MuleRun
identity. The CLI takes care of three things you would otherwise have to do
by hand:
- Credentials. Exchanges your MuleRun OAuth token for a short-lived per-call key and injects it into the agent runtime — no manual API-key setup.
- Runtime. Installs the agent’s binary on first use under
~/.mulerun/vendor/and keeps it up to date. - Model & effort. Translates
--modeland--effortflags into the right runtime args / env vars for the chosen agent.
Synopsis
-- separator follows the POSIX convention: everything after it is
forwarded verbatim to the underlying agent. Use it for one-shot prompts and
for any flag intended for the agent itself.
Flags
Global flags (
-t, -b, --proxy, …) apply as usual; see
Configuration.
Examples
Subcommands
mulerun code agents
List the agents compiled into this distribution. The default agent is
marked.
mulerun code models -a <agent>
List the model ids you can pass to --model for a given agent, along with
their canonical aliases.
--model X) or forward an unlisted id
verbatim with --model raw:<id>.
mulerun code upgrade
Upgrade the active agent runtime to the latest published version. Some
agents are version-pinned by the CLI itself — for those, the command prints
a notice and exits.
mulerun code reset
Remove the local install of the active agent runtime. The next
mulerun code invocation reinstalls it.
Tips
- The first
mulerun codeinvocation on a clean machine downloads the agent runtime; expect ~10-30 seconds on a fast link. - Use
--debugto see the exact runtime path, env, and exec arguments. - If a runtime install gets stuck, run
mulerun code resetand try again.
See also
mulerun studio— multimodal generationmulerun login— OAuth setup- Configuration — proxies, base URL, token