Emulo

Emulo

Your AI agents act like they just met you. Emulo fixes that.

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.

Open source and Emulo Pro

Emulo's local engine stays MIT licensed and useful without an account. Your session extraction, redaction, caches, profile, and agent adapters remain on your machine unless you explicitly choose a model provider for mining.

Emulo Pro is the optional hosted layer for client-encrypted approved-generation continuity across up to five devices, managed pairing and revocation, conflict-preserving history, and a bounded encrypted recovery/export window. Raw session evidence, decryption keys, and model-provider tokens do not enter the hosted service. Ending Pro access never disables local Emulo, its history, or rollback.

The hosted Worker source is public so its authentication, checkout, webhook, and entitlement rules can be audited. Production credentials and customer records are held by Cloudflare and Polar and are never stored in Git. Public source code is not public access to the hosted service or its data.

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.

🡒 agent

🡒 agent + emulo

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 full reply 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?