Jaidu uses OpenAI Codex for host-side code execution. The Agents page is therefore focused on configuring Codex variants.
Configurations are used throughout Jaidu: onboarding, default settings, workspace creation, and follow-up threads.

​
Common Use Cases

Use CaseExample Configuration
Fast iterationLower reasoning effort and permissive approvals
Complex tasksHigher reasoning effort and planning-oriented prompt
Safer executionRestricted sandbox and stricter approvals
Code reviewPrompt additions for review criteria

​
Key Concepts

Controls what Codex can access:
  • read-only - Can inspect files but cannot modify them
  • workspace-write - Can modify files in the project directory
  • danger-full-access - Unrestricted filesystem access
Controls when Codex pauses for your confirmation:
  • untrusted - Ask before every action
  • on-failure - Ask when an action fails
  • on-request - Ask only when explicitly requested
  • never - Do not pause for confirmations
Controls how much work the model does before responding. Higher effort is slower but more thorough. Lower effort is faster but more lightweight.
Use append_prompt to add your own reusable instructions to a Codex variant, such as repository conventions, review checklists, or project-specific constraints.

​
Configuration Access

Access Codex configurations via Settings → Agents in the Workspaces UI.
Codex configuration form editor interface with configuration list and form fields
The interface uses a two-column layout:
  • Left column - Codex
  • Right column - Configuration variants for Codex

​
Managing Configurations

​
Creating a New Configuration

  1. Click the + button in the Configurations column
  2. Enter a Configuration Name such as DEFAULT, SAFE, or HIGH_REASONING
  3. Optionally clone an existing configuration
  4. Click Create Configuration

​
Editing a Configuration

  1. Select Codex from the left column
  2. Select a configuration from the right column
  3. Edit the fields in the form
  4. Click Save in the bottom bar

​
Deleting a Configuration

  1. Select the configuration to delete
  2. Click the delete button
  3. Confirm deletion
You cannot delete the only Codex configuration. Jaidu always requires at least one usable Codex profile.

​
Setting a Default Configuration

Click the Default badge next to a configuration to make it the default for Codex. The default configuration:
  • Appears pre-selected when creating new workspaces or attempts
  • Is reused for follow-up messages unless you choose another configuration
  • Becomes the default Codex configuration in the chat toolbar

​
Codex Configuration Options

​
sandbox
string
Execution environment: "read-only", "workspace-write", or "danger-full-access"
​
approval
string
Approval level: "untrusted", "on-failure", "on-request", or "never"
​
model_reasoning_effort
string
Reasoning depth: "low", "medium", or "high"
​
model_reasoning_summary
string
Summary style: "auto", "concise", "detailed", or "none"
​
append_prompt
string | null
Extra instructions appended to the Codex system prompt
​
base_command_override
string | null
Override the Codex CLI command path when an administrator needs to point Jaidu at a different Codex command installed on the host.
​
additional_params
string[] | null
Additional CLI arguments to pass to Codex
Options that reduce approvals or expand filesystem access make Codex more autonomous. Use them deliberately.

​
Environment Variables

Each Codex configuration can define environment variables that are injected into the Codex process at launch. This is useful for setting API keys, toggling provider-specific behaviour, or pointing Codex at a custom environment.
Codex configuration form showing environment variable entries