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 for your owner chat (Discord and Slack work too).

npm install -g @jungjaehoon/mama-os
mama init          # asks for settings; tokens are typed at hidden prompts
~/.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.

Then send your bot a message. Setup is done when MAMA answers you, not when the process is running. The first-day tutorial walks through connecting a source, asking about work, giving a correction, reports, the viewer and sending files.

Claude Code development memory is separate and needs no daemon: /plugin install mama, or add the MCP server {"mcpServers":{"mama":{"command":"npx","args":["@jungjaehoon/mama-server"]}}}. See Claude Code plugin.

How it works

What you connect   work sources · a messenger · corrections you give
The agent          one owner agent on Claude or Codex, reading and writing through MAMA's actions
The record         SQLite on your machine: originals · work history · guidance · reports · run logs · local search index

The record. Every collected message, file notice or calendar change is stored as an original observation. Work items keep revisions: each one says what changed, why, the evidence it came from and who was involved. Search runs locally over originals, work history and memory.

The agent. Your messages, new source changes and scheduled reports all reach one agent session. It reads the stored work and sources before answering, updates the work history, writes the board and the wiki pages of the work it touched, and can split a large replay window across subagents inside the same turn. A source change gets a short turn that decides whether to tell you and a second turn that records it; MAMA checks the work ledger and orders the record again if it is missing. Every tool call it makes is recorded with the run that made it.

Guidance and workflows. Your corrections are kept as lessons, preferences, constraints and workflows, each with a line saying when it applies. Rules that always apply go in your owner policy file, which the agent holds in every session. With each message from you or source change, the agent is shown the few saved lessons that match it best, and can add, revise or retire workflows as you agree on them. Every change keeps its history.

The viewer. http://127.0.0.1:3847 shows the board, work items with their history, the memory graph, the wiki and logs.

What you can connect

Each source is optional; enable the ones you use in ~/.mama/connectors.json or during mama init.

Source	What MAMA collects	How it connects
Chatwork, Slack	Messages in the rooms and channe