Documentation
CLICommands

ox config

View and modify ox configuration settings. Settings can be configured at user, repo, or team level with a priority chain.

Usage

terminal
# Interactive config editor (TUI)
$
# List all settings with values
$
# Describe every setting (for apps)
$
# Show a setting with its override chain
$
# Set at user level (default), repo level, or team level
$
$
$
# Clear an override at user level or repo level
$
$

Interactive mode

Without a subcommand, ox config opens an interactive editor when stdin and stdout are terminals. With --no-interactive, in CI, or with redirected input or output, it lists settings instead. With --json, it prints the settings as JSON.

Available settings

SettingValues
session_recordingdisabled, manual, auto
session_publishingauto, manual
murmur_sendmanual, auto
murmur_receiveon, off
telemetryon, off
disposable_machineon, off
tipson, off
statuslineon, off
brief_paneon, off
usage_paneon, off (deprecated)
recap.trace_consultationson, off
context_git.auto_commiton, off (deprecated)
context_git.auto_pushon, off (deprecated)
view_formathtml, text, json
session.drafton, off
agent.summarizerinline, delegated, off
agent_workerauto, none, claude, codex
recording_reminderon, off
plan.saveon, off
plan.htmloff, recommend, always
plan.opennever, ask, always
skills.claude_org_dedupeon, off
pr_visuals.richon, off
pr_visuals.themelight, dark
pr_visuals.headeron, off
attribution.commitAny text, or "" to disable
attribution.prAny text, or "" to disable
hooks.userpromptsubmit.cloud_queryon, off
attribution.score_threshold0.0 to 1.0

To see each setting's label, description, type, allowed values, the levels it can be set at, and its current value, run ox config schema. It works outside a repository, where values come from user config and defaults.

Priority chain

Settings are resolved in this order (first match wins):

  1. User (your user preferences file), Personal preferences
  2. Repo (.sageox/config.json), Project-specific settings
  3. Team (Team Context config), Team-wide defaults
  4. Default, Built-in fallback values

User-level preferences apply even in repositories that have not run ox init. To read and write a different user preferences file, pass --config <file>; it overrides OX_USER_CONFIG and normal user config discovery. Repo and team files are still selected by the current project and --repo/--team.

Examples

List all settings

terminal
$

Lists every setting with its current value and source. Add --json for JSON output.

Get a specific setting

terminal
$

Shows the effective value and the override chain (user > repo > team > default).

Set at user level

terminal
$

Set at repo level

terminal
$

This adds the setting to .sageox/config.json in the current repo.

Set at team level

terminal
$

This updates the team context config, affecting all team members. Not every setting accepts every level; ox config schema lists the levels for each one.

Clear an override

terminal
$
$

Clearing an override falls back to the next level in the chain. Clearing a user-level override lets the repo or team value take effect.

Subcommands

CommandDescription
ox config listList all settings with current values and sources
ox config schemaDescribe every config setting (for apps)
ox config get <key>Show a setting's value and override chain
ox config set <key> <value>Set a configuration value
ox config unset <key>Remove an override at a specific level

Flags

FlagDescription
--user(set, unset) Apply to user-level config (default)
--repo(set, unset) Apply to repo-level config (.sageox/config.json)
--team(set, unset) Apply to team-level config
--json(list, get, schema) Output in JSON format

What's next

  • ox status: View current configuration state
  • ox init: Initialize a project with default settings