Jeden/Docs

CLI command

jeden config

Inspect and change Jeden's schema-backed user configuration.

Exact invocation#

Shell
jeden config [list|path|get <key>|set <key> <value>|reset <key>] [--json] [--cwd path]

Inputs and options#

  • No action defaults to list.
  • --cwd selects the project layer used when computing effective values; --json selects structured output.
  • Use the linked leaf commands for their required key/value inputs.
  • The contract keys are contracts.communication and contracts.functionality; both are strings. An empty communication contract means Jeden's default (plain language, then what was done, blockers, next steps); none turns it off.
  • The communication keys are communication.mode (normal, debug, quiet) and the overrides communication.toolCalls, communication.toolResults, communication.reasoning, and communication.code (auto, show, hide).
  • model is the model route turns run on, as the selected provider's catalog advertises it. Brama may advertise virtual subscription routes; an explicit JEDEN_MODEL_ENDPOINT uses that direct provider's concrete model IDs. /setup records the selection, jeden config get model reads the effective value with the project layer applied, and JEDEN_MODEL or --model overrides it for one run. The contract journeys under tests/contracts pass it into their isolated homes the same way they pass credentials.

Output and state effect#

Lists merged effective settings, prints the writable user path, reads one setting, or atomically writes a schema-validated user value/default depending on the selected action. New and rebuilt system prompts include each non-empty operator contract; the built-in task contract remains read-only and is exposed separately as taskContract by RPC contract settings. The next turn of every session honours the communication mode.

Refusals and boundaries#

  • The functionality is jeden.config, using jeden.config.read and jeden.config.write; jeden errors show jeden.config prints every cause with its test. An unknown verb is verb-unknown and a word after a request argument-unexpected, exit 2; the leaf pages list the rest.
  • Unknown keys and values that do not match the setting's boolean, finite-number, enum, array, object, or string schema are refused before writing, naming what the key takes.
  • 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.