Each page describes how one part of Mob behaves today. Pages open with what
the feature does and how to use it; how it works and where it lives in the
code come further down. When a change alters that behaviour, update the page
in the same pull request. Design discussion happens in issues and pull
requests; Mob does not keep architecture decision records.
| Page |
Covers |
| Model providers |
adding a provider, /model per conversation, providers.json, presets and the model catalog |
| Configuration |
files, environment, live reload, who owns the service, access tokens |
| Turns and context |
replies that outlive their tab, limits, context counting and summaries, token usage |
| Tools and approvals |
built-in and plugin tools, approvals, remembered grants |
| Sandbox |
the container sandbox, its limits and gVisor |
| Slash commands |
the command registry, help and completion |
| Schedules |
prompts the model runs on its own later, once or repeatedly |
| Desktop app |
the Electron window, tray and packaging |
| Page |
Covers |
| Coding agents |
getting started, the agents, projects and tasks, the Agents page, approvals and notices |
| Task workflow |
blueprints, automatic checks and reviews, sub-tasks, read-only reviewers, results |
| Plans |
several tasks approved at once, drawn as a flow you can review and change |
| Page |
Covers |
| Messaging channels |
Telegram, WeChat iLink and email, and their shared bridge |
| Plugins |
plugin settings and secrets, the email mailbox, Cloudflare |
| MCP servers |
external tools over the Model Context Protocol |
| Skills |
Agent Skills the model loads by name, and running their scripts in the sandbox |
| DeepSeek Harness plugins |
DSH tool compatibility, the optional runtime, setup and limitations |
| Extensions |
how plugins add tools, hooks, commands, routes, configuration and background runs |
| Page |
Covers |
| Remote access |
which way to pick, the web app at usemob.app, pairing with local Mob, encrypted runners |
| Mob in the browser |
Mob running in the tab with no runner, its models and moving conversations |
| Runners in the cloud |
a runner at Render that stays on without your computer |
| GitHub App |
a runner watching a repository: label an issue and Mob proposes a plan |
The retired Cloudflare Worker and Telegram Mini App, and the decision records
written for them, are kept at the legacy-worker tag.