Coding agents
Managed Claude Code, Codex, Hermes, and OpenCode agents, with a separate Desktop local path
Coding agents
A coding agent is a real coding CLI with a filesystem and terminal. Cloud tasks use Foxl-managed model access through Relay and charge your Foxl credits. Remote tasks run on isolated Amazon Bedrock AgentCore machines.
Cloud backends
| Backend | Managed model family | Default model |
|---|---|---|
| Claude Code | Claude | Opus 5 |
| Codex | GPT | GPT-5.6 Sol |
| Hermes | Claude | Opus 5 |
| OpenCode | Claude | Opus 5 |
Claude choices include Fable 5.1, Fable 5, Opus 5, Opus 4.8, Sonnet 5, and Haiku 4.5. Codex choices include GPT-6 Astra, GPT-5.6 Sol / Terra / Luna, and GPT-5.5. Older versions remain available through the model preferences. The full orchestrator catalog also includes GLM, Kimi, Grok, and Gemma; a chat-model choice does not change which models a coding CLI supports.
Choosing an agent
- Per task: choose a backend when creating a task, or name a supported backend in chat.
- Account default: use the agent segment of the Tasks or Runtimes header, or Settings > Code > Coding agent. This also applies to new scheduled and autonomous tasks.
- Terminal: opens a shell without a coding assistant. Remote compute is metered even when no model is running.
- Models and credits: the picker links to managed model settings. A provisioned backend is ready without uploading a personal key or subscription file.
An existing task keeps its agent and model when resumed. Codex uses Retry where the deployed runtime cannot reconnect to a sleeping session.
Desktop local agents
Desktop's local execution path keeps its own CLI credentials and provider billing. Supported local choices include Claude Code, Codex, Kiro, Cursor, Hermes, and OpenCode. Kiro and Cursor are local options rather than managed cloud backends. See On your own computer.
Personal credentials saved by older versions of Code are not used for managed cloud tasks. Changing a Desktop provider does not change the cloud task's model access.
Isolation and the workspace
Each Remote agent gets its own session workspace. It survives invocations and idle gaps, so a supported reconnect or resume can keep the cloned repository and build artifacts. The compute is recycled after fifteen idle minutes and has an eight-hour maximum lifetime. Session storage can outlive compute for 14 idle days. Keep durable work in a pushed branch.
Configuring the container
Settings > Code > Container controls:
| Setting | Effect |
|---|---|
| Approvals | Whether the CLI can edit and run commands without asking each time |
| Time limit | How long a task may run; 30 minutes by default, up to 8 hours |
| Instructions | Account instructions in the assistant's supported instruction file |
| Environment variables | Extra variables for commands in the task |
| Advanced config | Supported preferences for the selected CLI |
These settings are reapplied on reconnect. Repository instruction files are preserved. Managed model IDs, provider endpoints, and authentication are controlled by the task and cannot be replaced by personal credentials in container settings.
Model usage, including auxiliary requests for titles or summaries, goes through the task's Relay authorization. See Budgets and tiers for how credits are reserved and settled.