MAMA

Documentation · Your first day · How it works · What you can connect · Security · Status

MAMA is a work agent that runs on your own computer. It follows the conversations, files and schedules in the tools you connect, keeps them as they were, and keeps a history of each piece of work: what changed, why, who did it and what the feedback was. You talk to it in your messenger. It answers from that history, sends you reports, and remembers how you want things done.

The same repository also gives Claude Code a development memory (decisions and checkpoints that survive a new session), and both are built on mama-core, a shared engine other products can use.

MAMA runs no hosted service. The record stays on your machine. Only the content a run needs leaves it, through the AI CLI you logged into and the services you connected.

Why

An assistant is only as useful as what it remembers, and memory kept on someone else's server disappears when the service changes. MAMA keeps the record of your work on your computer, in its original form, so today's model and a better one tomorrow can read the same history. You decide which sources to connect and what to hand over.

Principles

In order of importance.

1. Never lose the record. Original text, time, source and every later change are kept, not overwritten.
2. Know why it changed. Each change to a piece of work names the message or file behind it.
3. Act only where allowed. MAMA sends only to the owner destinations you configured, and its agent writes files only inside its own workspace.
4. Remember corrections. Say "reports should be short" or "translate feedback into the usual spreadsheet" once. MAMA keeps it as guidance or as a workflow and applies it from then on.
5. Stay independent of the model vendor. Claude or Codex runs the agent; the record's format does not depend on either.
6. Everything else. Speed and convenience improve only within the five above.

What it looks like

You: Who is working on what right now?

MAMA: 12 items are in progress. Two need you today: the sample poster review is waiting for your decision on the color variant, and the launch checklist is overdue since yesterday 17:00.

You: From now on, when feedback arrives as a PDF, translate it into our feedback spreadsheet and send it back as a file.

MAMA: Saved as a workflow. I will use it for the next feedback PDF.

At 08:00, 13:00 and 18:00 it sends a full report. Urgent changes arrive as soon as they happen; the rest are gathered into an hourly reminder between 09:00 and 21:00.

Getting started

You need Node.js 22.13+, a logged-in claude or codex CLI, and a Telegram bot in a group for common changes (Discord and Slack work too). Create that group even for a solo owner; use its negative group or supergroup ID during setup. Private chats enter personal sessions.

npm install -g @jungjaehoon/mama-os
mama init          # asks for settings; tokens are typed at hidden prompts
mama register-owner YOUR_TELEGRAM_USER_ID # after setting member_root outside HOME
~/.mama/start.sh   # or the launchctl command init prints

To run from a checkout instead, run pnpm install and pnpm build, then use node packages/standalone/dist/cli/index.js wherever the guides say mama.