@eos-ai/cli

CLI for the EOS Memory API — query your team's knowledge graph from the terminal.

API surface evolves until Loop 3. Breaking changes in minor versions until 1.0.0.

Install

npm install -g @eos-ai/cli

Quick start

# 1. Configure your API key (stored in ~/.config/eos/credentials.json)
eos init

# 2. Search the memory layer
eos search "what changed in auth last week"
eos search "who owns the payments module"
eos search "open PRs touching the API gateway"

Commands

eos init

Interactive prompt to configure your API key. Credentials are stored at ~/.config/eos/credentials.json (mode 0600).

Get an API key at eos.dev/settings/api — Starter plan or higher.

eos search <query>

Searches the workspace memory layer and prints ranked results.

eos search "what changed in auth last week"
eos search "who reviewed the most PRs this month" --limit 10

Options:

• --limit <n> — max results (1–20, default 5)

What you get back

Each result shows:

• Node type: insight, decision, team_norm, or entity_context
• The knowledge content
• Relevance score, date, related repos and developers

  Knowledge nodes  (3)
  ──────────────────────────────────────────────────────────────────

   1. [insight]         JWT middleware refactored in PR #42 to drop session cookies.
      score 87.3%  ·  Apr 1, 2026  ·  acme/api  ·  @alice

   2. [decision]        Auth tokens now expire after 24h (reduced from 7d).
      score 72.1%  ·  Mar 20, 2026  ·  acme/api

   3. [team_norm]       All auth changes require two reviewer approvals.
      score 61.8%  ·  Feb 14, 2026

  request_id: req-abc123  ·  48ms server