Quickstart

From nothing to a memory every AI tool can read, in three steps. No credit card, and your source never leaves your machine.

1. Sync your repo

Run the CLI at the root of any repo. It parses your code into a structure-aware map — symbols, signatures, routes — on your machine.

bunx @secondos/cli push .

The first run builds the full map. Every run after that is incremental: only what changed is re-parsed and re-embedded, so a re-sync is fast.

2. Understand what uploaded

Two artifacts leave your machine: the map and the embeddings. Your file bodies do not. Secrets like .env, *.key and *.pem are never read, and inline keys are redacted before anything is embedded.

map.json      symbols, routes, signatures
vectors.json  embeddings only
your source   never uploaded

Want richer search that hits logic, not just names? Add --deep to embed symbol bodies locally (only the vector persists, never the source).

3. Connect an AI tool

Add the SecondOS MCP server to any tool that speaks MCP — Cursor, Claude Code, GitHub Copilot, Cline, Windsurf and more. They all read the same map, so you sync once and every tool remembers.

See the MCP server page for the exact configuration and the tools each editor gets.

4. Keep it fresh (optional)

Install the GitHub App and every push re-extracts the changed files on the runner and updates the cloud map. Sync once, stay fresh forever — no manual re-runs.

Next

Read the CLI reference for ask and drift, or the MCP page to wire up your editor. When you are ready for team freshness and rollback, see pricing.