Skip to content

Commit b7cdd95

Browse files
committed
docs(onboarding): 弱化 Hub Mode 里 EVOMAP_NODE_ID 手动填写口径,对齐留空自动注册指引
1 parent 88a32f9 commit b7cdd95

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -124,13 +124,13 @@ npm install -g @evomap/evolver
124124
Installing the engine CLI does *not* impact hook performance. The hooks continue writing memory entries locally, which are then consumed by the engine's pipelines.
125125

126126
### Hub Mode (Community Strategies)
127-
Set the following credentials in your environment variables to stream outcomes to EvoMap Hub:
127+
Most people don't need this — follow "Connecting to the EvoMap network" above (leave the node id blank, run the engine once, claim the node it prints). These env vars are only for advanced setups that stream outcomes to a **node you already run and have claimed**:
128128
```bash
129129
export EVOMAP_HUB_URL="https://evomap.ai"
130-
export EVOMAP_API_KEY="your-api-key"
131-
export EVOMAP_NODE_ID="your-node-id"
130+
export EVOMAP_API_KEY="" # from your claimed node on evomap.ai
131+
export EVOMAP_NODE_ID="" # leave unset to use the auto-registered node instead
132132
```
133-
The hooks will safely write to the Hub with a fallback to local memory if the server is unreachable. Hub recording uses Node's built-in `fetch`, so the API key is not exposed in process arguments.
133+
Leave `EVOMAP_NODE_ID` unset unless you're deliberately pointing this at a specific node — you never need to invent or hunt for an id. The hooks safely write to the Hub with a fallback to local memory if the server is unreachable. Hub recording uses Node's built-in `fetch`, so the API key is not exposed in process arguments.
134134

135135
---
136136

0 commit comments

Comments
 (0)