Workspace runtime presets are the supported preset model for workspace execution. Use them to choose which skill and MCP server definitions are selected for Codex in an issue workspace or for the next workspace follow-up. Runtime presets are organisation settings. They apply only after a workspace runs on a registered host that exposes the selected resources. Runtime presets do not install skills or MCP servers. They select resources that are already exposed by the selected host executor. Jaidu can prepare its own bundled system skills for built-in workflows, but a missing custom or user-installed skill remains something to set up on the host before the preset can be used.

​
What Runtime Presets Store

A runtime preset stores resource IDs only:
  • skill IDs exposed by the selected host executor;
  • MCP server IDs exposed by the selected host executor;
  • a default marker for the organisation, when one preset should be used by default.
Runtime presets do not store full Codex profile settings. They do not contain sandbox mode, approval policy, reasoning settings, prompt extensions, command overrides, environment variables, secrets, MCP server definitions, URLs, headers, command arguments, skill bodies, or installation sources.

​
Runtime Resource Availability

A runtime preset is an allowlist of resource definitions. Selecting a preset does not guarantee that every selected MCP server becomes a callable tool inside the next turn. Availability is resolved in two stages. Before launch, the selector performs an inventory check against the selected host executor:
Selector statusMeaning
SelectableThe selected resource ID is exposed by the selected host executor and can be passed to the next Codex turn. This is not a guarantee that MCP tools will start or be advertised.
Not supportedThe selected resource ID is missing from that executor inventory, the resource is unavailable, or workspace runtime resources are unsupported for the executor. For example, the current Codex app-server path accepts stdio MCP definitions and does not pass HTTP MCP definitions through as workspace runtime tools.
PendingThe selector has not loaded the selected host inventory yet.
After launch, true MCP tool availability can only be known from the Codex app-server startup and tool-discovery results. Use Available only for that post-launch state, when a selected MCP server started and exposed callable tools to Codex. Other post-launch states include Configured but no tools and Failed, but the selector does not infer those states from inventory alone. /mcp is a diagnostic for MCP status returned by the Codex app server. When its output is not scoped to the selected per-turn workspace runtime config, it is labeled as base host MCP status so it is not confused with the preset selection.

​
Skill Selection Behaviour

For skills, an explicit runtime preset is the selected skill set Jaidu passes to Codex for the next workspace turn.
  • In a new workspace thread, Jaidu sends the selected skills when Codex starts the thread.
  • In an existing workspace thread, Jaidu refreshes the resumed thread’s skill inventory before the next turn so deselected or removed skills from earlier preset turns are not intentionally carried forward.
  • Switching back to Default uses the organisation default preset when one exists. Without an organisation default, Jaidu uses the current unrestricted default skill inventory.
If Jaidu cannot safely refresh the skill inventory for a resumed thread, the turn fails with a runtime cleanup error instead of continuing with stale skill instructions.
Skill selection is a behaviour boundary for workspace Codex turns. It is not a host permission boundary, a security sandbox, or a way to grant filesystem or project access. Conversation text and repository files can still mention skill names, but those mentions do not make a skill selected for the turn.

​
Configure Runtime Presets

1

Open Runtime presets

Open Settings, select your organisation, and choose Runtime presets.
2

Create a preset

Add a preset name, then select the skills and MCP servers the preset should expose to workspace Codex turns.
3

Set the organisation default

Mark one preset as the default when you want new issue workspaces to start with the same resource set.
Runtime preset availability depends on the selected host. If a host does not expose a saved skill or MCP server ID, Jaidu blocks or warns before launching that Codex turn.

​
Use Runtime Resources In Workspaces

Workspace create and workspace chat surfaces use the same runtime resource model:
  • Default uses the organisation default preset when one exists. Without an organisation default, the workspace uses unrestricted default behaviour.
  • Preset uses a saved organisation runtime preset.
  • Custom selects skills and MCP servers for that workspace or next follow-up without saving a new preset.
For follow-up, queue, retry, and edit flows, a changed runtime resource selection is a per-turn override. It applies to that requested Codex turn and does not mutate the saved workspace runtime snapshot.