Skip to main content
Glama
become-human

become-human

by 201Tech
README.md
<div align="center">

# BecomeHuman

<table><tr><td><pre>
        __________                                    __________
 =====-'  [o] [o]  ]=[]=[]=[]=[]=[>   *   <__________(          '-=====
                 [====]                         (______
                 [====]                         (______
 =====-._______[====]                            (_______.______.-=====
              machine                                 human
</pre></td></tr></table>

**Your AI agent, working with you. Not just for you.**

[Install](#install) · [What changes](#what-changes) · [Your files](#your-files) · [Make it yours](#make-it-yours)

</div>

## Why

AI agents are fast, but they forget you every session, decide things you wanted to decide,
and leave work you cannot follow. BecomeHuman fixes that in any agent that speaks MCP:
Claude Code, Codex, Cursor, Gemini CLI and others.

## Install

Run it **once per computer**. From then on your agent starts it by itself, every session.

**Claude Code**, as a plugin (inside a session):

```
/plugin marketplace add 201Tech/become-human
/plugin install become-human@become-human
```

Or as an MCP server, which also lets you pass [settings](#make-it-yours):

```bash
claude mcp add become-human --scope user -- npx -y become-human
```

<details>
<summary>Codex, Gemini CLI, Cursor and others</summary>

```bash
codex mcp add become-human -- npx -y become-human
gemini mcp add -s user become-human npx -y become-human
```

For Cursor, Windsurf, Claude Desktop and any other agent, add this to its MCP config:

```json
{
  "mcpServers": {
    "become-human": {
      "command": "npx",
      "args": ["-y", "become-human"]
    }
  }
}
```

</details>

You only need [Node.js](https://nodejs.org) 20 or newer.

## What changes

> **You:** let's continue<br>
> **Agent:** Last time we left off at #4 "add the login screen". There is also an open question:
> email or phone? Which do you prefer?<br>
> **You:** email, and stop using semicolons<br>
> **Agent:** Done. Learned: you prefer code without semicolons.

- **It does the work and keeps you in the loop:** what it will do, why, and what changed.
- **You lead:** it asks before any choice that shapes the work, and your word is final.
- **It makes your life easier:** it spots what slows you down and offers to fix it, only with your consent.
- **It teaches:** plain explanations, adapted to how much you already know.
- **It learns how you work:** your preferences and corrections, so it never asks twice.
- **It remembers each project:** code, writing, research or planning: ideas, decisions, questions, next steps.
- **It is a real partner:** matches your tone, notices when you are tired, admits mistakes,
  disagrees with respect.

Read the full rules in [rules/human-first.md](rules/human-first.md).

## Your files

Everything stays on your computer, in a folder you can open: **`~/BecomeHuman`**.

| File | What is inside |
| --- | --- |
| `profile.md` | What the agent learned about you, grouped by topic |
| `my-rules.md` | Your own rules for every agent |
| `maps/<project>.md` | One checklist per project: ideas, decisions, questions, next steps |

They are plain text. Read them, fix them, add notes: the agent follows what is there
and never erases what you wrote.
Not sure where they are? Ask your agent: *"where is my data?"*

## Make it yours

- **Your rules:** write them in `~/BecomeHuman/my-rules.md`, one per line. They win over the defaults.
- **Your language:** set `BECOME_HUMAN_LANG=pt` to get your files in Portuguese (`en` is the default).
- **Another folder:** set `BECOME_HUMAN_HOME` to keep the files elsewhere, like a synced folder.
- **Profile size:** the agent keeps at most 50 facts and merges similar ones. Change it with `BECOME_HUMAN_PROFILE_LIMIT`.

To pass a setting to Claude Code, add `-e` when installing:

```bash
claude mcp add become-human --scope user -e BECOME_HUMAN_LANG=pt -- npx -y become-human
```

## Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md). License: [MIT](LICENSE).

TDQS

B3.1/5.0

Scored across 8 tools

Disambiguation4/5

The two domains (human memory vs. project idea map) are clearly separated, and remember/forget/map_add/map_resolve each target a distinct operation. The only mild overlap is between get_rules, get_profile and where_is_my_data, which all return loosely related read-only context and could be confused by an agent looking for stored knowledge.

Naming Consistency3/5

There is a readable grouping (get_* for reads, map_* for map operations), but conventions are mixed: bare verbs (remember, forget), verb_noun (get_profile, get_map), noun_verb (map_add, map_resolve), and a full sentence (where_is_my_data). An agent can follow it, but it is not a predictable pattern.

Tool Count5/5

Eight tools is well within the sweet spot and each one maps to a concrete operation: read rules/profile/map, write/remove a fact, add/resolve a map node, and locate data. Nothing feels redundant or padded.

Completeness3/5

Fact memory covers create, read and delete, but there is no update/edit of an existing fact, and the map surface lacks any node removal, rename or edit operation — only add and resolve. An agent that mis-records a node or needs to correct a preference will hit a dead end.

Maintenance

ActivityMaintained
ResponsivenessOutdated data