mohManual

Manual/Reference

Your data and privacy

Chapter 17 · 2 min read

Everything moh keeps is in one folder in your home directory, ~/.moh/ — plain files you can open, back up or move. Nothing about your usage is sent anywhere.

Where things live

~/.moh/
├── config                         # your settings and login tokens
├── projects/<project>/
│   ├── <id>.jsonl                 # one file per conversation
│   ├── memory/                    # durable facts about the project
│   └── retro/                     # suggested improvements
├── trash/                         # deleted conversations, 30 days
├── themes/                        # your colour themes
├── skills/                        # your own skills
└── extensions/                    # extensions you installed
  • Conversations are written like a diary: new lines are added, nothing is rewritten in place. That is what makes resume, fork and the branch map possible.
  • Logins and keys stay in your personal settings or your system's keychain — never inside a project's files, where they could be shared by accident.
  • A project is recognised by its git remote, so two copies of the same repository share the same history on your machine.

Secrets never reach the diary

Before anything is written down, moh masks whatever looks like a secret — an API key, an access token, a password field, a Bearer header, a private key — and stores the word [redacted] in its place.

what is saved
you typed OPENAI_API_KEY=sk-proj-9fK2…x7Q
on disk OPENAI_API_KEY=[redacted]

There is no setting, flag or question that turns this off. The live conversation is not affected — only what is saved — and files written by older versions are left exactly as they were.

The only network traffic

  • Talking to the AI providers you configured.
  • An optional check for new versions — it never installs anything without your yes, and it can be switched off.
  • Features you turn on yourself: web pages you ask moh to read, MCP servers, a handoff, Jev.

Nothing about your usage is phoned home: no remote telemetry, no analytics. moh does measure its own usage — calls, tokens, estimated costs — but only on your machine, from your own files, and the reports never leave it.

Deleting really means deleting — eventually

A deleted conversation rests in the trash for 30 days (you can change the period), then is removed for good. Forks keep their own copy, and project memory is untouched. To remove everything moh knows about you, delete the ~/.moh/ folder.

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