Skip to main content
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:
  1. 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.
  2. Runtime. Installs the agent’s binary on first use under ~/.mulerun/vendor/ and keeps it up to date.
  3. Model & effort. Translates --model and --effort flags into the right runtime args / env vars for the chosen agent.

Synopsis

The -- 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.
Pin a model by its allow-list id (--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 code invocation on a clean machine downloads the agent runtime; expect ~10-30 seconds on a fast link.
  • Use --debug to see the exact runtime path, env, and exec arguments.
  • If a runtime install gets stuck, run mulerun code reset and try again.

See also