mohManual

Manual/Going further

Browser, MCP, helpers and the project map

Chapter 10 · 3 min read

Beyond reading and editing files, moh can drive a web browser, use tools from other programs, delegate pieces of work to helpers, and orient itself with a map of your project. Each of these follows the same permission rules as everything else.

A browser it drives itself

moh can open web pages, read them, click, fill in forms and take pictures of what it sees. It uses its own private browser, working in the background — nothing pops up on your screen.

  1. Turn it on. One row in the settings (ctrl+s → Browser), or type /browser. When moh needs it and it isn't set up, ctrl+b takes you straight there.
  2. Let it install its parts. moh downloads what it needs (about 200 MB) into its own folder — no npm, no administrator password.
  3. Ask. "Open localhost:3000, sign up with a test name and tell me what breaks."
$ moh browser status     # what is installed, what is missing
$ moh browser install    # install or refresh the browser parts

Safety

Looking at a page is free; clicking, typing, uploading and running scripts ask first, and "always" is limited to that site. Downloads are blocked unless you approve each one. Pages on your own machine are reachable; the rest of your private network is blocked unless you allow it, so a page cannot trick moh into poking at your router.

MCP: tools from other programs

MCP (Model Context Protocol) is a common standard for giving an AI extra tools — your issue tracker, a database, a documentation search. Add a tool server once and moh can use it. 

$ moh mcp add github -- npx -y @modelcontextprotocol/server-github
$ moh mcp add docs --url https://example.com/mcp
$ moh mcp list
  • Servers start only when first used and stop when the conversation ends.
  • Every MCP tool asks on its first use.
  • A server suggested by a project's moh.json asks whether you trust it before anything runs — a cloned project can never switch tools on by itself. Servers you add with --user are yours and trusted.

Helping hands: subagents

For bigger jobs, moh can hand focused pieces of work to small helper agents that run alongside it — one explores the code while another drafts a fix. They can only use tools the main conversation already has, never more.

Running helpers appear as chips above your message box. Press tab to reach them, ←/→ to move, and enter to open a live view of what one is doing. Their final result always lands in the main conversation.

The project map (MPM)

The optional Moh Project Map builds a local index of your project's structure — which files exist, which functions and classes they define, how they relate. It stores names and relations, never copies of your code. moh uses it to start a task in the right place and to answer focused questions about the code.

  • It is off until you turn it on (settings, ctrl+s).
  • Its advice always cites the source, and comes only when it is sure: files your request names, things it mentions, and — more quietly — names from moh's own recent reasoning. If a match is ambiguous, it says nothing.
  • It updates in the background without slowing a conversation down. Check it with /mpm or moh mpm.

Written for moh 0.61. Inside moh, ctrl+h opens the built-in manual for your exact version.