Docs / Reference
Look it up. Get back to the work.
Reference pages describe current names, controls and file formats. Task instructions live in the guides; future behaviour lives on the roadmap.
- Architecture conceptsHow Miton works in plain English — one project, specialised workspaces, shared goals, memory and permissions — before the engineering deep dives.
- Configuration filesWhere Miton stores settings and project data — user profile, project `.miton/` folder, override order, and wipe options.
- Documentation mapFind the right Miton guide, reference page, essay or trust resource without leaving the public site.
- Environment variablesEnvironment variables Miton reads at startup — development overrides, provider keys, and paths. Most configuration belongs in Settings instead.
- GlossaryPlain-English definitions for Miton terms you see in the app — surfaces, modes, goals, and project concepts. An engineer appendix maps internal code names to those functions.
- KeybindingsKeyboard shortcuts in Miton — the cross-surface shortcuts every keymap preset shares, plus the keymap presets themselves. macOS uses Cmd; Windows and Linux use Ctrl.
- LAN bindOptional LAN access for Miton Studio — consent flow, bearer token, configuration, and security expectations.
- mDNSHow Miton Studio advertises itself on your local network for zero-config discovery — service name, supported clients, and privacy notes.
- Permission modesThe five steering modes in Miton — Chat, Plan, Confirm, Autoedit, and Full access — and what each allows without asking.
- Permissions taxonomyHow workspace trust and steering modes combine to decide what the agent may read, write, and run — plus per-tool overrides and the session audit trail.
- Slash commandsBuilt-in slash commands for chat — session control, model and mode, prompt-shaping helpers, and the built-in skills invoked the same way.