Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Open Context Engine

by Dhaxorversion 0.7.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.Dhaxor/open-context-engine

How to install

What it does

Local-first code retrieval: hybrid search over an AST-aware index of your codebase. Fully offline.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 468,7331 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,3321 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 150,2871 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity10/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score22/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Open Context Engine. Follow https://mcp.popnx.com/i/dhaxor-open-context-engine.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Open Context Engine for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "open-context-engine": { "command": "npx", "args": [ "-y", "@dhaxor/open-context" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Open Context Engine tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "open-context-engine": {
          "command": "npx",
          "args": [
            "-y",
            "@dhaxor/open-context"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Open Context Engine and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Open Context Engine or shows a Open Context Engine tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Open Context Engine yet

Open Context Engine runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Open Context Engine

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Open Context Engine for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user open-context-engine -- npx -y @dhaxor/open-context 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Open Context Engine tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user open-context-engine -- npx -y @dhaxor/open-context
  4. Type /mcp in Claude Code

    You should see Open Context Engine listed as connected

  5. Try it

    Use Open Context Engine and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Open Context Engine or shows a Open Context Engine tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Open Context Engine for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "open-context-engine": { "command": "npx", "args": [ "-y", "@dhaxor/open-context" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Open Context Engine tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Open Context Engine and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Open Context Engine or shows a Open Context Engine tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Open Context Engine for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "open-context-engine": { "type": "stdio", "command": "npx", "args": [ "-y", "@dhaxor/open-context" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Open Context Engine tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Open Context Engine and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Open Context Engine or shows a Open Context Engine tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Open Context Engine💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user open-context-engine -- npx -y @dhaxor/open-context

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "open-context-engine": {
      "command": "npx",
      "args": [
        "-y",
        "@dhaxor/open-context"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "open-context-engine": {
      "command": "npx",
      "args": [
        "-y",
        "@dhaxor/open-context"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "open-context-engine": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dhaxor/open-context"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
354/wk
Connection
Runs on your computer
Latest versioni
0.7.1
Published to registryi
Nov 8, 2026
Code last changedi
Nov 16, 2026
Maker
Dhaxor
Packages
npm: @dhaxor/open-context
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Dhaxor, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @dhaxor/open-context@0.7.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/dhaxor-open-context-engine.svg)](https://mcp.popnx.com/en/servers/dhaxor-open-context-engine)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 0% of the other 6136 servers in this category
  • Published to the registry more recently than 69% of the other 6136 servers in this category
  • Basic checks equal to or better than 99% of the other 6136 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Open Context Engine safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 3 days ago, and the latest version (0.7.1) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
Open Context Engine
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Open Context Engine

Local. Semantic. Instant.

Turn any codebase into a searchable knowledge base for AI.


Open Context Engine (OCE) is a local-first, high-performance retrieval engine that indexes your entire codebase, embeds it into vectors, and serves it up to LLMs via semantic search, keyword search, and the Model Context Protocol (MCP). No cloud required. No code leaves your machine.

Whether you're building a coding assistant, automating PR reviews, or just want to ask natural-language questions about your own code—OCE gives your AI ground truth.

📘 Docs, benchmarks & guides: opencontextengine.com — MCP setup for Claude Code & Cursor, the agentic-workflow guide, and measured retrieval benchmarks.

✨ What Makes It Special

FeatureDescription
🧠 AST-Aware ChunkingUses Tree-sitter to split code along semantic boundaries (functions, classes, methods) rather than naive line counts. Understands TypeScript, JavaScript, Python, Go, Rust, Java, C#, C, C++, Ruby, PHP, Kotlin, and Swift.
🔍 Hybrid SearchFuses dense vector similarity (cosine) with BM25 keyword search via Reciprocal Rank Fusion for results that are both semantically relevant and lexically precise.
⚡ Local SQLite + VectorsStores everything in a local SQLite database with sqlite-vec—no external vector DB, no network latency, no subscription fees.
🏠 Fully-Local EmbeddingsThe default: in-process ONNX embeddings — zero API keys, zero servers, models cached on disk. Ollama also supported; Voyage is the drop-in upgrade for the best code retrieval.
🔗 Symbol ExpansionAutomatically resolves identifiers in search results, pulling in definitions of functions, classes, and types referenced in snippets.
🎯 Optional Re-rankingPlug in Voyage or Cohere re-rankers to boost result quality for complex queries.
🕸️ Code GraphA tree-sitter AST pass extracts import/call/definition edges into a queryable graph; top search results are graph-expanded so callers and callees ride along.
🔭 TraceThe agent workspace in your browser, terminal, or desktop: an evidence rail showing what is in the model's context (ranked, pinnable, evictable), checkpoint rewind, approvals with a blast-radius score, watchable sub-agents, and parallel sessions in isolated git worktrees you can review and land.
🤖 Agent HarnessA full tool-use agent with codebase retrieval, file editing, shell execution, and web search — plus parallel read-only tool execution, pre/post tool-call hooks, token-usage accounting, session export/import, model routing, and cross-session memory.
🔌 MCP NativeExposes retrieval, file, and symbol tools through the Model Context Protocol over stdio or Streamable HTTP (shared endpoint with bearer auth). Works with Claude Desktop, Cursor, and any MCP-compatible client.
🧰 VS Code ExtensionSidebar chat grounded in the index, agent edits with per-file diff/undo/redo, live re-indexing on save, and an index-health panel. Ships per-platform; one Node-API SQLite binding runs on every VS Code from 1.103.
🛡️ Policy ControlsPin what the engine may do per workspace or org: disable shell/edits/web-search, pin command allowlists, force local-only embeddings, exclude paths. Org-signed policy locks cannot be loosened locally.
🧾 Tamper-Evident Audit LogHash-chained JSONL of every agent run, tool call, and MCP invocation. oce audit --verify detects any alteration, deletion, or reordering.
👥 Team Index SyncBuild the index once in CI, publish it as an artifact (S3/HTTP/shared drive), and teammates oce pull-index it — only their local diff re-embeds. A content-hash embedding cache means identical code never bills twice.
🚀 Parallel IndexingWorker-thread parse/chunk pool kicks in automatically on large repos; oce bench measures throughput on yours.
🛟 Degrades, Never DiesNo sqlite-vec build for your platform? The engine runs keyword-only (BM25) instead of crashing — indexing and search keep working, and every surface tells you which mode you're in.
📏 Measured, Not GuessedRetrieval quality is scored against committed gold sets — this repo's own and an external codebase — in both search modes, with adaptive fusion that tilts BM25/semantic weights per query shape: hybrid recall@10 0.943 · keyword-only 0.886 here, parity (0.926) on Flask where hybrid previously lost. Ranking changes ship with before/after deltas. The coding agent itself is scored too: oce eval-agent runs end-to-end tasks graded by verification scripts.

🚀 Quick Start

1. Install
npm install -g @dhaxor/open-context     # Node 22+
2. Pick a model — free options included
oce setup

oce setup checks what you already have (a running Ollama, keys in your environment) and lists every way to get a working model, free ones first:

-pCost
ollamafree, localRuns on your machine. No key, no quota, works offline.
googlefree tierGemini — the most generous free tier; key at aistudio.google.com/apikey
groqfree tierVery fast; key at console.groq.com/keys
cerebrasfree tierKey at cloud.cerebras.ai
openrouterfree modelsModels ending :free cost nothing; key at openrouter.ai/keys
openai, anthropicpaid

oce setup -p google records your choice; after that oce trace just works.

Hybrid search out of the box — no key, no account. The first index embeds with local MiniLM (in-process, on-device, nothing sent anywhere), so semantic + keyword search works immediately. Want the strongest code retrieval? A Voyage key upgrades the embedding model — oce setup --embeddings voyage — and the index rebuilds with it. Local does the job fine if you'd rather not.

3. Open Trace
oce trace      # the workspace, in your browser

oce # the same thing, in your terminal

Both index the current directory on start and keep one conversation going — see Trace below for what makes it different.

4. Or search from the command line
oce index                                        # full index (incremental afterwards: --incremental)

oce search "how does the auth middleware work?"

🔭 Trace

Trace is the agent workspace. Every coding agent shows you what it *did*; Trace also shows you what it *knew* — because OCE owns the retrieval, not just the chat loop.

  • Evidence rail. What is in the model's context window right now: every retrieved chunk ranked by its fusion score, the graph edge that pulled it in ("called by search.ts"), and a budget meter split into retrieval / files / history / system. Pin a chunk and it survives compaction; evict one and it is genuinely removed from the next request.
  • Retrieval readout instead of a spinner — retrieved 5 · top 0.94 · graph +2 · 251ms.
  • The spine. A timeline of checkpoints, one per turn, on the same hash chain as the audit log. Click one to rewind: the conversation *and* the files the agent changed roll back — and a file you edited by hand since is left alone.
  • Approvals with a blast radius. Every edit and shell command waits for y / always / n, showing the diff, a risk score, and how many indexed callers the file has.
  • Sub-agents you can watch. Delegated research streams into its own collapsible block instead of going silent for minutes.
  • Parallel sessions. In a git repository, each new session gets its own worktree and branch, so agents never edit the same checkout. Review a session's diff and land it (commit + --no-ff merge) when it's done — uncommitted work is never discarded when you close one.
  • The composer. @path pins a file into context (fuzzy-matched against the index), !command runs a shell command through the same approval flow, and /command for everything else — the same in the browser and terminal.

oce trace binds to 127.0.0.1 only and mints a fresh access token each launch. Useful flags: --port, --no-open, --headless (API only), --no-parallel.

In the terminal

Bare oce opens the same workspace full-screen in your terminal: the same evidence rail (from 100 columns wide, or Ctrl + R ), the same checkpoint gutter, the same approvals. Esc or Ctrl + C interrupts a run; Ctrl + C twice or /exit quits. Pipes, --print, and dumb terminals fall back to the classic line-by-line REPL, which you can also ask for with oce --classic.

As a desktop app

desktop/ wraps Trace in an Electron shell that adds desktop notifications (only when an approval is waiting, a turn finishes in the background, or something fails), an application menu, and trace:// deep links. It is built from a source checkout for now — see desktop/README.md.

The classic REPL

oce --classic streams styled output, shows each tool call with a live spinner and timing, and — before any file edit or shell command — prints a diff/command preview and asks for approval (y / always / n). Ctrl+C interrupts the current run without quitting the session.

Approval modes (as in the other leading coding CLIs):

  • default (suggest) — every edit and shell command asks first
  • --auto-edit — file edits apply automatically; shell still asks
  • --full-auto — nothing asks (for containers / CI)

Switch mid-session with /mode. Interactive sessions have the edit and shell tools available behind approvals; the non-interactive --print path keeps them opt-in via --allow-edits / --allow-shell.

Slash commands: /help /reset /compact /plan /diff /usage /tools /mode /sessions /resume /exit.

Sessions persist automatically to .open-context/sessions/. oce --continue resumes the last conversation in the workspace; oce --resume restores a specific one (list them with /sessions).

Harness features:

  • Plan tracking — the agent maintains a live step checklist for multi-step work, rendered as you watch.
  • Sub-agent delegation — broad explorations run in a scoped read-only child agent, so their large intermediate output never floods the main context.
  • Summarizing compaction — when history gets long, older turns are condensed into a context note *by the model* rather than dropped, so decisions and file paths survive; force it with /compact.
  • Environment awareness — platform, git branch/status, date, and index stats are injected into the system prompt.
  • Cost + parallelism — every turn ends with a stats line (steps, tool calls, token usage, wall time); read-only tool calls in a turn run in parallel, while any turn with an edit or shell call stays strictly ordered.
  • --route sends each query to a cost-appropriate model tier; --memory remembers codebase insights across sessions; --audit logs runs to the tamper-evident audit log.

Non-interactive use for scripts and CI:

oce --print "where is the auth middleware defined?"           # one answer, then exit

oce --print "list the exported symbols in src/core" --json # {answer, stats, toolCalls}

The programmatic API mirrors all of this: defaultAgentTools({ context }) stays read-only unless you pass includeEdits/`sh

Only the beginning is shown; read the rest in the repo