@oracle-agent/oracle 0.18.0 → 0.18.1

package/README.md

@@ -27,12 +27,18 @@ The private operator configuration, approval flow, wire units, and holder waiver
 Specialist agent profiles, real protocol intents, self-custody by default,
 receipts or it didn't happen.
 
-Built for [Hermes](https://github.com/NousResearch/hermes-agent), the
-open-source agent runtime from [Nous Research](https://nousresearch.com).
-Oracle runs native chat directly — no external agent required.
-`oracle chat` starts the Oracle-native agent loop directly.
+Oracle runs its own agent loop. `oracle chat` starts the Oracle-native agent
+directly — no external agent runtime required.
 
-Hermes remains available as an optional delegate: `ORACLE_CHAT_BACKEND=hermes oracle chat`.
+Any MCP-capable harness can drive it instead: run `oracle mcp install <target>`
+for Claude Code, Claude Desktop, Codex, ChatGPT, Cursor, VS Code, or Copilot, or
+install it as an [Agent Plugin](https://agent-plugins.org/). In that direction
+the harness calls Oracle as a tool and Oracle's native loop stays in charge.
+Run `oracle harness detect` to see what is installed and how to wire it.
+
+[Hermes](https://github.com/NousResearch/hermes-agent) is one such harness, and
+also remains available as a legacy delegate that takes over the model loop
+entirely: `ORACLE_CHAT_BACKEND=hermes oracle chat`.
 
 Oracle can run standalone model auth directly with API keys or Claude, Codex,
 and Grok OAuth. OAuth credentials use the OS keychain when available, with a
@@ -349,12 +355,13 @@ npx oracle-data         # local read plane on 127.0.0.1:8787
 npx oracle-data-mcp     # MCP stdio server (any MCP client); needs oracle-data up
 ```
 
-It is better under [Hermes](https://hermes-agent.nousresearch.com/docs), because
-a trading stack is several workloads with opposite needs and **per-profile
-routing** gives each its own model, tools, and key scope: cheap wide context for
-research, a fast model for execution where latency is money, the strongest model
-for risk review, something small for unattended crons. The research profile can
-hold no signing key at all.
+Per-profile routing is worth setting up under a multi-profile harness such as
+[Hermes](https://hermes-agent.nousresearch.com/docs), because a trading stack is
+several workloads with opposite needs and **per-profile routing** gives each its
+own model, tools, and key scope: cheap wide context for research, a fast model
+for execution where latency is money, the strongest model for risk review,
+something small for unattended crons. The research profile can hold no signing
+key at all. Oracle's native loop covers the single-agent case on its own.
 
 Oracle's own pre-release audit ran four model lineages — Grok 4.5, Opus 5,
 Fable 5, GPT-5.6 — and **each found a critical bug the others missed**. One
@@ -392,14 +399,15 @@ can't pass review quietly. An existing `SOUL.md` is never overwritten without
 `--force`, and `--force` writes a timestamped backup first.
 
 Oracle does not issue its own model credential. Standalone chat uses the OAuth
-login or API key the user configured; Hermes mode uses whichever provider that
-Hermes installation already supports.
-
-**Why "built for Hermes" and not just "works anywhere":** Oracle's read plane is
-an MCP server, so any MCP client can call it. But the *mesh* — per-lane memory,
-skills, sessions, and separate model choice per specialist — is Hermes profile
-machinery. You can use Oracle from any agent; you get the architecture in the
-diagram above from Hermes.
+login or API key the user configured; a delegate harness uses whichever provider
+that installation already supports.
+
+**What you get where:** Oracle's read plane is an MCP server, so any MCP client
+can call it, and the native loop brings its own memory, skills, scheduler, and
+bounded tools. The multi-lane *mesh* in the diagram above — per-lane memory,
+skills, sessions, and a separate model choice per specialist — is profile
+machinery from a multi-profile harness such as Hermes. Use Oracle from any
+agent, or on its own; add a profile mesh only if you want that topology.
 
 ## Best-execution routing
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oracle-agent/oracle",
-  "version": "0.18.0",
+  "version": "0.18.1",
   "description": "Oracle: standalone prepare-only multichain agent control plane. Runs its own agent loop, or plugs into any MCP-compatible harness. Policy-bounded intents for a user-signed wallet; the public package never takes your key.",
   "license": "BUSL-1.1",
   "type": "module",