Own your terminal: every surface of MendCode can be replaced
40 themes, 22 view slots, keybindings with a leader key and vim mode, four prompt modes and five output styles, hooks on 12 events. /customize previews each change live and a package can carry all of it.

A coding agent spends hours in your terminal. Its colors, its footer, how a tool call reads and which keys do what should be yours to change, not a fixed product decision.
Five layers
What you can change
Look
40 themes, 28 Markdown colour slots, the footer’s segments and over 60 settings for how a session reads. /theme, /customize.
Views
22 slots: messages, tool cards, footer, sidebar and whole pages. Replace any with a view of your own.
Keys
keybindings.json, a leader key of your choice and vim mode in the prompt (/vim).
Prompt
Four prompt modes, five output styles, AGENTS.md or CLAUDE.md with @file includes and a model per role.
Tool calls
Hooks on 12 events can block a call before it runs; tool_define writes a new tool; MCP, skills and packages add more.
Features
A tier is a starting set; each of the 69 features can still be switched on or off.
/customize
/customize edits the terminal’s look with a live preview, and every change is saved at once. /settings lists every daemon setting, /status shows read-only facts about the daemon, engines and storage, and /extensions shows what loaded, with errors.
Views are small functions
The look of one surface is one small file: a view is a pure synchronous function from data to styled rows. Start one with the scaffold:
mendcode view scaffoldShare it
A package can carry a theme, profile values, keys and views. It applies as an overlay, and turning it off puts your own values back.