Guide · 4 min read
Code — overview
Ship software in Miton: chat-first agent, editor, code search, sub-agents, per-turn rewind, and project intelligence. Overview and links to task guides.
- Product stage
- Pre-release development
- Last reviewed
- 2026-07-23
- Successful result
- The change is visible in the active project.
What this accomplishes
Ship software in Miton: chat-first agent, editor, code search, sub-agents, per-turn rewind, and project intelligence. Overview and links to task guides.
Code is Miton’s software engineering lens. You get a chat-first agent that knows your project, a code editor, search, sub-agents in isolated worktrees, per-turn rewind, and project intelligence for milestones and drift.
This page is the overview. Task guides below cover each tool. See also /for-developers.
Current availability
This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates.
Before you start
- A Miton development build and an active project containing source code.
- A connected model. Trust the project before allowing file, terminal or Git actions.
What Code does
Code is for engineers who ship real software. You can:
- Open a project and let the agent read structure before you type.
- Run tests in a sub-agent — ask “is the build green?” and get real results.
- Review diffs in a sub-agent with structured feedback.
- Spawn sub-agents in isolated git worktrees parallel to your main session.
- Rewind any agent turn with one click — git-native restore points.
- Post inline PR comments on GitHub, GitLab, and Bitbucket with sensitive content stripped locally.
- Track milestones, blueprints, and drift between plan and codebase.
How Code fits with the other lenses
Miton shares one agent engine across Chat, Writer, Canvas, Code, and Automation:
- Writer — long-form editor, citations, export.
- Canvas — visual canvas, design tokens, forms.
- Automation — workflow graph, scheduler, webhooks.
They share memory, model routing, permissions, and undo.
Default tools
Code highlights these agent tools:
read/write/edit— read and write files with diff preview.bash— shell commands with permission prompts.glob/grep— file and content search.codex— apply a project patch from a plan.pr— open a pull request on GitHub, GitLab, or Bitbucket.subagent— spawn a sub-agent in an isolated worktree.
You can disable, configure permissions, or add custom tools.
Built-in sub-agents
Five default types:
- Explorer — read-only codebase exploration.
- Verifier — run tests and report results (read-only).
- Debugger — investigate failures; can add instrumentation.
- Test Runner — continuous test runs with failures surfaced in chat.
- Orchestrator — coordinate multiple sub-agents for multi-step plans.
Spawn from chat with /explorer, /verifier, /debugger, /test-runner, /orchestrator, or
define custom types in Settings.
Pages in this section
- Editor and language tooling — CodeMirror editor, LSP, symbols, find.
- Sub-agents — worktree isolation, permissions, review.
- Plan mode — read-only plan before non-trivial changes.
- Transparency and approvals — options, per-task accept/reject.
- Per-turn rewind — git-native restore and stash.
- Code search — full-text, semantic, and hybrid search.
- Git and worktrees — branches and isolation.
- PR review — desktop-local review and privacy gate.
- Blueprints and milestones — plan graph and drift signals.
- Backend design loop — REST/FastAPI/Axum brief + scaffold Done-when (Step 42a).
- Skills and commands — slash commands and custom skills.
- Troubleshooting — diagnostics and support channels.
Shared topics live in the Docs index. Engineering detail lives in ../../architecture/.
What success looks like
Ship software in Miton: chat-first agent, editor, code search, sub-agents, per-turn rewind, and project intelligence. Overview and links to task guides. The result remains attached to the active project when you move to another workspace.
Common failures and recovery
- Confirm the correct project and branch are active.
- Check the model connection and the permission request shown in Chat.
- Keep the exact error before retrying; use Code troubleshooting when the failure persists.
Related next action
Open Code troubleshooting for recovery steps and diagnostic paths.