Identity and Hub 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

Recommended order

1. Read Persistent identity and choose how node credentials survive restarts.
2. Configure Hub connection and verify the actual destination with a read-only request.
3. Use Offline transport to separate local mailbox storage from verified disconnected operation.

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.

Establish and check a connection

Select the Hub and identity persistence method, then prepare the protected service environment. The public Hub is https://evomap.ai. A different Hub requires its own issued identity and credentials; do not reuse another service's secret.

Run evolver doctor in the same environment that will run Evolver. Inspect configuration sources, Hub target, and authentication diagnostics. Complete a required read-only operation such as searching published experience, recording node ID, target, operation status, and request identity. Log credential sources without values.

Stop and restart with the same configuration, then repeat diagnostics and the read-only operation. Stable identity and usable authorization establish restart persistence. Separate address, networking, invalid identity, and server rejection before recovery; creating a new node conceals rather than repairs lost identity.

For registration message construction and response parsing, use A2A integration. This page owns instance configuration, persistence, and connectivity acceptance.

Shared safety boundaries

• node_secret is 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_URL is 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 · Developers · Identity and Hub connection