talos config

Settings live in three scopes; the effective value is the one with the highest precedence. Values are JSON: true, 3, "text", ["a","b"]. Every key is in Configuration.

Operation	What it does
listdefault	Prints the effective configuration: every scope merged, as TALOS uses it.
origins	Prints, for each effective value, the scope and file it comes from.
get	Prints one effective value.
set	Sets a value in one scope.
unset	Removes a value from one scope; a lower-precedence value, or the default, applies again.
show	Prints the user settings file as it is written, without merging.
migrate	Upgrades the settings file of a scope to the current format, keeping a backup.
rollback	Restores the settings file of a scope from the backup made by migrate.
permissions	Simulates a permission decision: which rule would allow, ask or deny an action, without running it.

Without an operation, talos config runs list.

list

Prints the effective configuration: every scope merged, as TALOS uses it.

talos config list

origins

Prints, for each effective value, the scope and file it comes from.

talos config origins

get

Prints one effective value.

talos config get <key>

Arguments

key

Dotted key, e.g. ui.theme or permissions.allow.

Exit codes and errors1

Code	Exit	Meaning
CONFIG_PATH_REQUIRED	2	The command or the configuration is not valid. Check the command, its options and the configuration.

set

Sets a value in one scope.

talos config set <key> <json> [--scope user|project|project-user]

Arguments

key

Dotted key.

json

The value, as JSON. Quote strings for your shell: '"forge"'.

Options

--scope <value> default user

Where to write it. Default user. Valuesuserprojectproject-user

• Key bindings (ui.keymap) can be set only in the user or project-user scope, never in the project.

Examples

talos config set ui.theme '"ember"'

talos config set catalog.modelsDev false

Turns off the models.dev catalog.

Exit codes and errors3

Code	Exit	Meaning
CONFIG_SET_REQUIRES_PATH_VALUE	2	The command or the configuration is not valid. Check the command, its options and the configuration.
CONFIG_SCOPE_INVALID	2	The command or the configuration is not valid. Check the command, its options and the configuration.
CONFIG_KEYMAP_SCOPE_INVALID	11	The provider key could not be used. Check the key saved for this provider.

unset

Removes a value from one scope; a lower-precedence value, or the default, applies again.

talos config unset <key> [--scope user|project|project-user]

Arguments

key

Dotted key.

Options

--scope <value> default user

Where to remove it from. Default user. Valuesuserprojectproject-user

Exit codes and errors3

Code	Exit	Meaning
CONFIG_PATH_REQUIRED	2	The command or the configuration is not valid. Check the command, its options and the configuration.
CONFIG_SCOPE_INVALID	2	The command or the configuration is not valid. Check the command, its options and the configuration.
CONFIG_KEYMAP_SCOPE_INVALID	11	The provider key could not be used. Check the key saved for this provider.

show

Prints the user settings file as it is written, without merging.

talos config show

migrate

Upgrades the settings file of a scope to the current format, keeping a backup.

talos config migrate [--scope user|project|project-user]

Options

--scope <value> default user

The scope to migrate. Default user. Valuesuserprojectproject-user

Exit codes and errors1

Code	Exit	Meaning
CONFIG_SCOPE_INVALID	2	The command or the configuration is not valid. Check the command, its options and the configuration.

rollback

Restores the settings file of a scope from the backup made by migrate.

talos config rollback [--scope user|project|project-user]

Options

--scope <value> default user

The scope to restore. Default user. Valuesuserprojectproject-user

Exit codes and errors1

Code	Exit	Meaning
CONFIG_SCOPE_INVALID	2	The command or the configuration is not valid. Check the command, its options and the configuration.

permissions

Simulates a permission decision: which rule would allow, ask or deny an action, without running it.

talos config permissions dry-run --tool <tool> [--command <cmd>] [--resource <path>] [--server-id <id>] [--operation <op>]

Options

--tool <value>

The tool to simulate. ValuesReadWriteEditBashWebFetchMcpHookPluginTalosService

--command <value>

The shell command (required for Bash).

--resource <value>

The file or resource (required for Read, Write, Edit).

--server-id <value>

The MCP server (required for Mcp).

--operation <value>

The operation, for tools that name one.

Examples

talos config permissions dry-run --tool Bash --command "npm test"

Exit codes and errors6

Code	Exit	Meaning
CONFIG_PERMISSIONS_OPERATION_INVALID	10	TALOS did not do this because it is not allowed here. Review the permission rules, then try again.
PERMISSION_DRY_RUN_TOOL_INVALID	10	TALOS did not do this because it is not allowed here. Review the permission rules, then try again.
PERMISSION_DRY_RUN_COMMAND_REQUIRED	10	TALOS did not do this because it is not allowed here. Review the permission rules, then try again.
PERMISSION_DRY_RUN_RESOURCE_REQUIRED	10	TALOS did not do this because it is not allowed here. Review the permission rules, then try again.
PERMISSION_DRY_RUN_SERVER_REQUIRED	10	TALOS did not do this because it is not allowed here. Review the permission rules, then try again.
PERMISSION_DRY_RUN_TARGET_REQUIRED	10	TALOS did not do this because it is not allowed here. Review the permission rules, then try again.