Settings and appearance
Change how kcode behaves and feels without writing an extension.
What you can change
Model and effort defaults, context and compaction budgets, memory recall, permissions, notifications, provider endpoints, and worktree configuration all have settings. Appearance settings cover fonts, scale, shaders, cursor effects, and tile behavior.
Choose the right scope
Keep personal defaults in ~/.kcode/config.toml. Put shared project choices in the trusted project’s .kcode/config.toml. A launch profile and environment variables can override those choices for a particular run. Precedence runs from built-in defaults to user config, project config, launch profile, then environment.
Themes and keyboard bindings
A theme can extend a bundled theme and replace selected values rather than repeat every token. Keyboard mappings let you rebind actions, add another chord, or remove a binding. Neither requires a Lua or Wasm plugin.
Set up for long-running work
Choose a default reasoning effort, set when context is compacted, and enable memory recall so the agent can bring relevant knowledge into a new turn. Notifications can bring you back when a session needs input, while keep-awake lets work continue when you step away.