Settings and appearance
kcode changes how it behaves and looks through settings, with no extension to write.
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. Precedence runs from compiled defaults to user config, trusted project config, an optional launch profile, KCODE_* environment variables, then command-line flags.
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 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.