konfig

konfig is one YAML file that is a total, self-contained, declarative description of a kdeps agent's behavior - tuning, harness, themes, events, actions, presets, and skills. Export it from the current effective state (even a completely default, never-customized setup) and hand the file to another machine to fully configure an agent there, no other setup needed.

Exporting

kdeps konfig export [path]     # default ./konfig.yaml, from a bare CLI invocation

/konfig export [path]          # inside the REPL, exports the LIVE session's config

The CLI form reads whatever is persisted in ~/.kdeps/agent-loop-settings.yaml (or built-in defaults if nothing was ever customized). The REPL form captures the running session's exact state instead, including anything changed with /model tool set, /theme, /goal on, etc. that hasn't necessarily been touched via a command that persists it elsewhere.

Importing

kdeps konfig import [path]     # default ./konfig.yaml
kdeps --konfig <path> [path]   # import, then start the agent loop

/konfig import [path]          # inside the REPL, applies immediately

Importing writes every section to where it already lives on disk -- harness entries to ~/.kdeps/harness/<name>.yaml, themes to ~/.kdeps/themes/<name>.yaml, events to ~/.kdeps/events/<name>.yaml, actions to ~/.kdeps/actions/<name>.yaml, presets to ~/.kdeps/presets/<name>.yaml, skills to ~/.kdeps/skills/<name>/SKILL.md, and tuning/registry/active-theme into ~/.kdeps/agent-loop-settings.yaml -- overriding any built-in or existing user entry of the same name. kdeps konfig import and /konfig import also reload the in-process harness, theme, event, action, and preset registries and apply the active theme immediately; --konfig <path> applies before the rest of startup reads settings, so the freshly imported values take effect for that run without a second step. Imported skills are picked up the next time the process starts (a running REPL's skill list is loaded once at startup).

What's in the file

Section	Contents
tuning	Every /model tool set knob - rounds, retries, compaction/fold thresholds, memory-graph leaf limits, web/bash/file/code call limits, turo settings, goal/refine/handshake toggles
harness	Every tool-use/behavior-prompt section - all built-in sections plus any ~/.kdeps/harness/*.yaml overrides, already merged by name
themes	Every REPL theme - built-in plus any ~/.kdeps/themes/*.yaml overrides, merged by name, with every palette color fully resolved (never left blank to inherit from normal on import)
events	Every reactive LLM event (auto-compact, fold, and the round-count guards) - built-in plus any ~/.kdeps/events/*.yaml overrides, merged by name. See events
actions	Every registered action name (the fixed vocabulary events' run: fields draw from) - built-in plus any ~/.kdeps/actions/*.yaml overrides, merged by name. See events
presets	Every named harness/event bundle (frugal, balanced, thorough, ...) - built-in plus any ~/.kdeps/presets/*.yaml overrides, merged by name. See presets
activeTheme	The currently selected theme's name
skills	Every loaded skill, with its full SKILL.md content inlined - skills travel with the file, not by path
registry	Enabled workflow/agency/component/skill lists, default model, model-name display mode, favorite models, custom OpenAI-compatible endpoints

Harness and themes are exported as the full effective set, not a diff against the binary's built-ins - the file alone fully determines behavior on any machine or kdeps version, independent of what that machine's own ~/.kdeps happens to contain.

Status

Export and import are both implemented, including the --konfig <path> startup flag.