emulo

Your real coding-agent sessions already contain the rules you never wrote down: what “done” means, what you reject on sight, how you debug, how you design UI, and how you write when you are actually working.

Emulo mines selected evidence from those sessions — Claude Code, Codex, Copilot CLI, OpenCode, and Google Antigravity logs out of the box — into a private working profile your agent reads before every task. Separate layers for work, design, writing, and video mean the right part of you loads for the right task.

The mined profile loads where your agents already live: Claude Code and Codex natively, Cursor, Gemini, and OpenCode through explicit adapters, and OpenClaw and Hermes Agent as a standard skill (guide).

The Emulo Proof v1 methodology is an unexecuted methodology until a separately approved evidence release exists.

The video layer, and where it comes from

A spec commercial, made in Claude Design. No After Effects and no motion software: the whole thing is a composition rendered out to video.

It is spec work. It was not commissioned by Vercel and it was not made for them. A brand was picked to see how far the motion could go.

It is here because emulo:video is mined from sessions like the one that produced it. The other layers work the same way: the profile is not a template, it is what survived from real work.

Install

Inside Claude Code:

/plugin marketplace add ohad6k/emulo
/plugin install emulo@emulo

Inside Codex:

codex plugin marketplace add ohad6k/emulo --ref v0.6.2 --json
codex plugin add emulo@emulo --json

Then run emulo:mine and point it at your session history. Everything below explains what that produces and why. If you want the CLI instead of the plugin, see Quickstart.

Open source and privacy

Emulo is MIT licensed, free, and works without an account. There is nothing to buy and no sign-in.

Session extraction, redaction, caches, the profile itself, and the agent adapters all stay on your machine. The one exception is mining: if you point it at a hosted model, the selected evidence goes to that provider. Point it at a local model and the whole run stays on your machine.

Not memory

Memory is what you explicitly told the model.

Emulo mines what your work already proved about you: what you reject, what "done" means, when you ask for proof, how you talk when you're actually working, and the agent behaviors that make you stop the task.

That's why it reads raw session logs, not your CLAUDE.md or rules file.

A real run

One line to the same agent, twice: "help me post emulo on reddit." Once cold, once with the Emulo profile loaded.

Here's how I'd play it.

Subreddits: r/ClaudeAI and r/ChatGPTCoding are your core audience. r/LocalLLaMA fits the local angle. r/cursor, r/SideProject, r/opensource for reach. Don't blast all at once — post to one, tune the title, repost over a few days.

Title: I built a local tool that reads your AI coding logs and writes a "you.md" your agents read before every task

Titles (pick per sub):

• I built a local tool that reads your AI coding logs and writes a "you.md" your agents read before every task
• emulo: mine your own Claude Code history into a profile so your agent codes like you (local, open source)

Body:

Every fresh agent session starts from zero — it doesn't know how you work, so you re-explain yourself every time. All of that is already in your session logs. So I built emulo: it reads your history, mines how you decide and talk, and writes a you.md your agents read before every task.

• runs locally, your logs never leave your machine
• redacts secrets before processing
• open source: [link]

Also: open with the pain not the product, reply fast in the first hour, add a demo gif, and flair it correctly. Want me to write tuned variants for each subreddit?

the insight first: the mining number is your whole post. "i read 1,656 of my own sessions" is a confession, not a pitch, and nobody scrolls past a confession. lead with the mirror, not the mechanism.

one sub, not five — a skills sub, where people come looking for this instead of arguing about it.

Title: I built a Claude skill from 8 months of my own Claude Code sessions

body: I use claude code and codex every day. 8 months, solo. every session gets logged and i never really looked back at them.

then it hit me that those logs are probably the most honest record of how i actually work. not my CLAUDE.md, not my docs, not the rules i remembered to write down. the real sessions.

so i built emulo.

What I did: pulled every message i typed from my local claude/codex logs. stripped tool output, pasted errors, file dumps, and assistant replies. kept only my words. came out to around 1,656 sessions and almost 3M tokens of just me.

then i split it into chunks and had agents read each slice. each one pulled patterns like how i define done, what kind of code i reject, when i ask for proof, what makes me stop a task, and how i talk when i am actually working.

then i merged the repeated traits into one you.md.

the useful part is that it installs as a claude skill. so now instead of starting every task cold, claude reads my profile first and already knows how i work.

not memory exactly. memory is what you told the model. this is more like mining what your work already proved about you.

I posted it on r/ClaudeSkills, as written:

What it finds

The kind of rules a mine pulls out, each backed by dated verbatim receipts from real sessions:

done means it runs live. never trust "done" off a code edit. show it working first.

fix the one thing. rewriting or "cleaning up" code that isn't the problem gets rejected every time.

builds faster than they understand what they built — then asks the agent to explain their own system back.

gets frustrated by repeating the same ask until it lands, not by escalating.

Nobody wrote those rules down. They came out of one person's own history, with receipts.

This is an example. Yours is mined from your logs and will read nothing like it.

The usage report

Mining answers "who is this person." The usage report answers a different question: where are you losing time with the model.

python emulo.py --coach                   # every source it can find
python emulo.py --coach --source claude   # Claude Code only

It runs before any mining, makes no model call, and finishes in seconds. It counts what your own messages already show: asks you sent three times in a row without changing them, context you re-explained after the agent lost it, runs where you rephrased the same request instead of adding the missing constraint, and how often you open a turn by correcting the last answer.

Every finding prints the dated messages behind it. Checks that come in under their bar are printed with their counts as well, so a clean result reads as a result rather than as silence.

It reads only the messages you typed, which is all Emulo keeps. It cannot see cost, tokens, tool calls, or whether the agent was right, and it never scores those.

The card

After mining, python emulo.py --card renders your profile as a shareable card: archetype, top laws ranked by distinct supporting session receipts, coverage stats, and one sharp truth.

Share the card or one short trait, never your full profile.

Quickstart

Install the cross-agent bootstrap — runs in Claude Code and Codex, and installs profiles for Cursor and Gemini through the explicit adapters:

npx skills add ohad6k/emulo@emulo

Then tell your agent:

run emulo

That installs the bootstrap and creates a read-only full-history mining plan. Your agent must show the cost and wait for approval before model work.

Once your profile exists, the bootstrap offers the native plugin so you also get namespaced emulo: routing. It asks first and takes a no. In Codex it can run the install itself; in Claude Code /plugin is typed by you, so it hands you the two exact lines to paste.

Install the CLI

If you'd rather run Emulo yourself instead of through an agent:

pip install emulo

That puts emulo on your path. emulo runs the miner, emulo --dry-run prints the read-only plan first, and emulo mcp runs the MCP server below. uv tool install emulo works the same way, and uvx emulo runs it without installing.

emulo writes RUN_ME.md next to your chunks. It is self-contained, so the whole remaining step is one line to your agent:

read emulo-out/RUN_ME.md and follow it

Your agent makes one pass per chunk, merges them, writes you.md, and prints the install command. Nothing to paste and nothing else to download.

Check the receipts

A profile is only worth loading if its evidence is real. The failure that matters is not a missing rule, it is a confident rule quoting something you never said:

emulo verify you.md

It pulls every quote out of the profile and searches the mined sessions for it. Quotes it cannot find are reported and the command exits non-zero, because a receipt that cannot be traced was invented. Quotes resting on a single session are flagged separately: one session is context, not a rule. Add --json for machine-readable output, including which session ids support each quote.

This checks what is mechanically checkable. Whether a rule is vague, generic, or true of every developer alive is still a judgment call, and still yours.

Native Codex plugin

The native plugin adds emulo:mine, emulo:work, emulo:design, emulo:write, and emulo:video:

codex plugin marketplace add ohad6k/emulo --ref v0.6.2 --json
codex plugin add emulo@emulo --json