A runtime is the program or service Rudder starts when an Agent works. The fastest setup uses a local CLI you have already installed and signed in to.

​
What you will verify

You will configure one Agent, pass its environment check, and run a small Chat task. The real task matters: a successful test proves that Rudder found the runtime, but not that the runtime can complete your work.

​
Before you start

Install and authenticate one supported runtime on the same computer as Rudder: Run the command once in your terminal to confirm it opens without a missing command or login error.

​
Connect it to an Agent

  1. Open the Agent, then edit its Runtime configuration.
  2. Choose the local runtime you installed.
  3. Choose a model and thinking level when that runtime offers them.
  4. Leave advanced permissions, sandbox bypass, custom commands, and instruction-file paths at their defaults unless your task needs them.
  5. Select Test runtime chain.
  6. Read the result:
    • pass: Rudder can start the runtime.
    • warn: setup may work, but read the named limitation.
    • fail: fix the named command, login, model, path, or network problem.
  7. Save the Agent.
  8. In Chat, ask for a safe, concrete result such as a two-line summary.
  9. Open the Agent Run and confirm the selected runtime produced the reply.

​
Check the result

The setup is ready when the environment test passes, or has a warning you understand, and the real Chat task finishes. The Run should show the intended runtime plus a result or clear blocker.

​
Common problems

  • Command not found: install the CLI or set the correct supported command.
  • Authentication failed: sign in through the runtime outside Rudder, then test again.
  • Model unavailable: choose a model your provider account can use.
  • Instructions or workspace cannot be read: use an absolute path and fix host permissions.
  • The test passes but the task fails: open the Run and fix the specific provider, model, permission, or project-access error.
Rudder supplies its own control tools to supported local runtimes. Do not add a second Rudder MCP server. External MCP connections and their access levels are advanced configuration; see Permissions and platforms when you need them.