Empryoempryo.beta
concepts

How it works

How Empryo works: a live ranked code graph, an agent loop with parallel sub-agents, and embedded Neovim with layered LSP, AST, and tree-sitter intelligence.

Empryo is three things talking to each other:

  1. A live code graph - every file, symbol, and import, ranked by importance. Updated as you work.
  2. An agent loop - reads, edits, tests, commits. Can dispatch parallel sub-agents.
  3. Your Neovim - embedded. The agent edits through the same editor you use.

The agents

AgentRunsModel
ForgeThe one talking to you. Orchestrates everything.Your active model
⚡ SparkRead-only research (grep, read, analyze).taskRouter.spark
🔥 EmberCode edits and refactors. Own context window.taskRouter.ember
WebSearchMulti-step web research with citations.taskRouter.webSearch

Configure which model each one uses in the task router.

What the agents share

When Forge dispatches multiple sub-agents in parallel, they coordinate through a shared bus:

  • File cache - first reader caches; others reuse.
  • Tool cache - read-only tool results shared across agents and dispatches.
  • Edit lock - concurrent writes to the same file are serialized.
  • Findings - one agent's discovery reaches the others at their next step.

Result: N agents don't re-read the same files N times.

Code intelligence, layered

Operations (go-to-definition, rename, diagnostics…) try the best backend first, fall back if it fails:

TierBackendUsed for
1LSPprecise types, workspace rename, diagnostics
2ts-morphTypeScript/JavaScript AST ops
2tree-sitter30+ languages - outlines, imports
3regexuniversal fallback

LSP runs via Neovim when the editor is open, via standalone servers otherwise. The agent always has it.

System prompt

Every turn, the prompt is assembled from: mode, project info, git context, the Genome, your memory, forbidden files, active skills. The Genome (built by the Genome engine) is personalized per-turn - files you just edited or referenced get boosted.

See the Genome for ranking details, memory for cross-session knowledge, compound tools for the one-call tools, code intelligence for the backend router.