ohad6k/emulo

Mine the messages you typed to your coding agents into a you.md profile, every rule with dated receipts, and install it where your agent can read it.
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, where every rule carries dated quotes from your own messages, and installs it where your agent can read it. The agent mining flow writes separate files for work, design, writing, and video, so a host can load only the one that fits the task.
The aim is an agent that works the way you do from the first message. That is an aim, not a result: what is tested so far is below, including the part that did not go our way.
Installing a profile and an agent actually reading it are two different things. In a host-by-host test on 2026-09-25, the profile reached the model through a project AGENTS.md in Codex (--target agents --repo ., verified end to end in one test) and was loaded into OpenCode's instructions. In Claude Code the you skill installs but is not reliably opened on its own; typing /you loads it. Cursor, Gemini, OpenClaw and Hermes Agent get the file where they look for it, and loading there is not verified. The support matrix has each one.
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:
Inside Codex:
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 or a sign-in. The tool
itself has nothing to buy. Separately, the site
offers one optional paid service, a hand edit of a profile you already mined, and
you never need it to use Emulo.
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 keeps coming up in your own sessions: 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.
What is tested so far
Emulo does three separate things, and they are held to different standards:
- **The usage report and emulo verify** are text matches on your own messages. They count and they trace quotes. They cannot tell you why anything happened.
- **Loading** means a host puts the profile in front of its model. Which hosts were seen doing that is in the support matrix.
- **Whether a loaded profile makes the agent's work better** is not shown. It is the aim, not a result.
What the published tests do show:
- An appended mined profile changed what the model produced, compared with no profile.
- In a 60 run study with every prediction written down in advance (August 2026), the mined profile did not separate from an invented profile of the same length on any of 9 comparisons. emulo.vercel.app/placebo
- In a September 2026 rerun with a later July 2026 profile (dated 2026-07-30) and a new invented profile, the mined profile separated from the invented one on 5 of 9 comparisons on Fable 5.1 and on 1 of 9 on Opus 5. emulo.vercel.app/fable
- Both tests measure whether the output changed (rounded corners, colour saturation, card containers, length), not whether it got better.
One example, not a test
An anecdote. One line to the same agent, twice: **"help me post emulo on reddit."** Once cold, once with the Emulo profile loaded. One run each way, with no control and no placebo, so it shows what two replies looked like, not what the profile does. Both replies are trimmed to their opening plan and title.