v0.1.3 — now on npm as engineering-os

Your AI finally remembers your codebase

Stop re-explaining your architecture every session. Engineering OS gives your AI tools the memory they've always been missing. They finally write code like someone who actually knows your project.

Get Started Star on GitHub
$ npm install -g engineering-os

Install, init, and you're done.

Your AI recalls decisions, enforces conventions, learns from every session, and plans across repos. This is what that looks like.

One local server. All your AI tools. Always in sync.

Run engineering-os once and it learns your entire codebase. Then it serves that knowledge to whichever AI tool you open. No cloud, no accounts, just instant answers.

AI Clients
Claude Code
Cursor
Codex
VS Code
Any AI Editor
MCP Protocol (stdio)
Engineering OS Engine
🔍
Search
FTS5 + BM25
🌐
Graph
Service topology
🧠
Skills
Persists forever
🛡
Security
OWASP + CVE
📋
Decisions
Never re-debates
Workflows
DAG engine
SQLite (100% local)
Your Codebase
Primary Project
Backend API
ML Pipeline
Mobile App

Install, init, and you're done.

1

Point Engineering OS at your project

One command. It reads your code, figures out how things connect, and builds a local knowledge base. Takes about 10 seconds for most repos.

$ npm install -g engineering-os $ eos init --claude --cursor ✓ Repository indexed (847 files, 4201 chunks) ✓ Architecture discovered (12 services, 3 patterns) ✓ Graph built (156 calls, 4 contracts) ✓ CLAUDE.md + .cursor/rules/ generated
2

Your AI just knows things now

Open your editor. Your AI already has access. It pulls context, recalls past decisions, and finds code instantly. You didn't have to configure a thing.

// Your AI now calls these automatically: eos_context({ task: "add retry to uploads" }) // Returns: routes, architecture, conventions, skills eos_search({ query: "file upload" }) // Returns: ranked results in 2ms eos_recall_skills({ query: "uploads" }) // Returns: "Chunks must be uploaded in order"
3

It gets smarter every day

Found a tricky bug? Discovered a hidden dependency? Your AI remembers it next time. The more you use it, the better it gets at your specific codebase.

// AI discovers something → persists it forever: eos_learn({ type: "gotcha", content: "FlatList items must not be memoized...", tags: ["react-native", "performance"] }) // Next session, auto-recalled when relevant.

The stuff your AI should've had from day one

🧠

Never explains twice

Your architecture, conventions, and team decisions persist forever. No more "here's how our project works" at the start of every session.

🔗

Sees all your repos

Working on a mobile app that talks to a backend that uses an ML pipeline? Link them. Your AI sees the full picture, not just one folder.

📚

Learns your tricks

That weird workaround you found last week? That gotcha with the upload service? Your AI remembers — and warns you before you hit it again.

🛡

Catches security issues

Scans for secrets, injection flaws, and known CVEs across your dependencies. You don't have to remember to check — it does it for you.

🔍

Finds code instantly

Ask "where's the auth middleware?" and get the answer in milliseconds. No more grepping through 500 files hoping you spelled it right.

🏗

Maps your architecture

It figures out your services, layers, and patterns automatically. Works with whatever stack you're running — from Express to Spring Boot to Ktor.

Whether you're one dev or fifty

📱

Teams with multiple repos

Your mobile app calls your BFF which calls your ML service. Link them all and your AI understands the full system, not just the file it's looking at.

🧑‍💻

Solo devs who move fast

After a few sessions, Engineering OS knows your naming conventions, your file structure, your quirks. Your AI codes like a teammate who's been on the project for months.

🏢

Enterprise teams who need guardrails

Security scanning, compliance checks, audit trails, shared conventions. All baked in. Every developer on your team gets the same standards enforced by Engineering OS.

Works with

What changes when your AI has a memory

✕ Today (without EOS)
✓ With EOS
"Let me explore your project structure..."
Already knows. Starts working immediately.
"Should we use Redux or Zustand?"
"You decided on Zustand last month. Here's why."
Suggests code that breaks another service
Sees the dependency graph. Avoids breakage.
You explain the same gotcha every session
Learned it once. Warns you proactively.
grep-ing for 30s trying to find that function
Instant answer. It's pre-indexed.
Security review is something you do "later"
Already scanned. Flags issues as you code.

Try Engineering OS on your project. Takes 30 seconds.

Runs entirely on your machine. Nothing leaves your laptop. npm install -g engineering-os and you're in.

Install from npm Read the Docs