Jeden/Docs

CLI command

jeden config set

Validate and persist one user configuration setting.

Exact invocation#

Shell
jeden config set <key> <value> [--json]

Inputs and options#

  • Required: exact schema key and value. Multi-token values are joined with spaces before type parsing; JSON arrays and records must be valid JSON. A boolean setting takes true or false.
  • Use contracts.communication to say how Jeden writes to you: your text replaces Jeden's default (plain language, then what was done, blockers, next steps) and none turns it off. Use contracts.functionality for execution and completion instructions; quote each contract as one shell argument.
  • Use communication.mode to choose normal, debug, or quiet, and communication.toolCalls, communication.toolResults, communication.reasoning, or communication.code with auto, show, or hide to override one item. A configuration file that names any other value is refused when it loads, naming the value and the ones there are.
  • Use ui.language to pin the language of Jeden's screens (picker, settings, badges, footers and the GitHub star request) to one of the fleet's languages, the list every Wisent product offers (wisent-texts languages.json), or auto for English; every screen text reads in each of them, and a test fails the build when a language lacks one or a translation drops a placed value.
  • Automatically discovered secret-named environment values are protected regardless of their length unless you explicitly set secrets.minLength to a nonnegative whole byte length. A threshold deliberately leaves shorter discovered values unprotected; explicitly configured values, environment names and secret files remain protected. jeden config reset secrets.minLength removes the threshold by restoring null. The shared setting schema used by the terminal and RPC settings reports that unset default. secrets.mode redact puts the configured replacement in place of each secret; obfuscate puts one * per character, keeping only its length.
  • taskScheduler.maxOutputBytes is the declared output budget for delegated jobs, including the platform command that merges a captured workspace into its parent. Merge diagnostics use this same setting rather than a separate hidden byte ceiling. The CLI configuration, Desktop Settings → Delegated tasks and RPC config/task-limits/set update the same declaration.

Output and state effect#

Parses the schema type, updates the nested user configuration object, atomically writes the user config, and prints the key/path or structured mutation result. A non-empty contract is added to every new or rebuilt system prompt; a communication setting applies from the next turn, including in a running session.

Refusals and boundaries#

  • Read before any file: key-missing, key-unknown, value-missing (config set requires a value for &lt;key&gt;, and the command line ends after the key, observed: what the key takes) and value-invalid (&lt;key&gt; takes &lt;what it takes&gt;, and `&lt;value&gt;` is not that, observed: what the reader answered), each exit 2: an invalid boolean, a number that is not finite, a value outside an enum's choices, JSON that is not an array or object where one is taken, or task limits config/task-limits/set would refuse. type-unreadable (exit 1) guards a schema type without its reader.
  • Writing is jeden.config.write, shared with jeden workspace adopt|forget and RPC config/language/set; each refusal exits 1 and leaves the files as they were: table-occupied (a key on the way holds a value that is not a table; it is not replaced), config-unmigratable (the file cannot be brought to this build's schema version, such as one a newer Jeden wrote), config-unwritable (the file could not be replaced whole, with what the system answered) and legacy-unremovable (the superseded ~/.jeden/config.json could not be removed after its keys moved).
  • secrets.minLength refuses negative, fractional and nonnumeric values before writing. The real redaction journey is node tests/secrets/discovery.mjs with JEDEN_BIN, JEDEN_TEST_SOURCE_REVISION, JEDEN_TEST_STADO and JEDEN_TEST_SECRET_MIN_LENGTH above the synthetic secret's byte length. Each case runs under its own HOME, where the model is played through Stado's attestation alternative and answers the value it was handed between the delimiters, so the final answer shows whether Jeden redacted the secret before the request left. It checks a short discovered secret, an explicit threshold, an explicit protected value, reset and invalid-setting refusal; commands, replies and session exports remain under .build/secret-discovery.
  • A command line of the wrong form (an unknown command or option, a missing, unexpected or invalid argument, a missing confirmation) prints the error and the usage and exits 2; a refusal that retrying unchanged can help (a dependency down or not answering, a rate limit) exits 69; any other refusal or failure exits 1. A refusal a functionality declares ends with fix: … and cause: &lt;operation&gt;.&lt;cause&gt;, and jeden errors show &lt;operation&gt; lists every cause of that functionality.