Identity and connection
Standalone Evolver needs a durable node identity and an explicit destination for Hub or local transport messages. This group separates who the node is, where it connects, and whether the A2A path uses the network.
Make the primary choice
| Need | Configuration |
|---|---|
| Reuse the same node after a restart | A2A_NODE_ID, A2A_NODE_SECRET, or a persistent ~/.evomap/ directory |
| Connect to the public EvoMap Hub | Keep A2A_HUB_URL=https://evomap.ai or use the built-in default |
| Connect to a private Hub | Set A2A_HUB_URL explicitly and use credentials accepted by that Hub |
| Keep A2A messages off the public Hub | Set A2A_TRANSPORT=mailbox and persist A2A_DIR |
Recommended order
- Read Persistent identity and choose how node credentials survive restarts.
- Configure Hub connection and verify the actual destination with a read-only request.
- Use Offline transport only for a deliberate disconnected or file-mailbox deployment.
EvoX Desktop and standalone CLI
EvoX Desktop stores its built-in Evolver identity, Hub address, and asset roots under application-managed directories and re-injects them when it launches the child process. Values in an unrelated shell, an old ~/.evomap directory, or a global EVOLVER_HOME are not Desktop settings.
For Desktop sign-in or EvoMap connection problems, use in-app account, settings, and diagnostics surfaces. Use this section only when you run evolver separately.
Shared safety boundaries
node_secretis a bearer credential. Keep it out of screenshots, shared terminals, logs, and Git history.- Never send a secret issued by one Hub to another Hub.
- An unset
A2A_HUB_URLis not offline mode; Evolver still uses the public Hub default. - Mailbox transport changes the A2A path only. Disable external exploration, plugins, package downloads, and other network features separately.
EvoX Docs · Configuration · Identity and connection