Installation and first setup

Verify the release package and complete local setup, pairing and recovery-key storage.

Workflow

Check the platform-specific package and SHA-256 first. 0.3.1 requires a new empty data directory; never overwrite an older database. Extract the complete native package, run verify-package, then install. Keep the program, Web assets, licenses and manifest together.

Boundary and checks

The console binds to loopback only. Accept the agreement yourself, set a PIN or longer passphrase, and store the one-time recovery key offline. The broker does not provide these values to MCP clients.

Check for an existing installation first

A new AI client or conversation does not require another broker. Inspect the existing MCP command, PATH and documented installation record, then run status with the active binary. Start a healthy stopped installation instead of creating a second data directory. If a custom data directory was used and its location is unknown, find it before installing.

Recommended installation path

Copy the request from the installation page into an assistant that can run commands on this computer. It should discover an existing installation before selecting a suitable product release.
Match the package to the platform and architecture. Verify the archive SHA-256 against the release, unpack the complete package and run verify-package. See package verification.
Review the destination and proposed command before installation or changes to the AI client. install PACKAGE copies the whole package into the current user’s installation and starts the broker.
If the management page did not open automatically, run open with the active binary from an interactive desktop on the broker’s computer. Accept the agreement, set a PIN or longer passphrase yourself, and save the one-time recovery key privately.
Generate client-specific MCP configuration from the active binary, reload the AI client and call the read-only secretbridge_terminal_capabilities tool. Finish with a disposable resource and a reviewed test operation.

Service controls and compatibility

Command	Purpose
`status`	Inspect broker, version and active installation path
`open`	Open local management; creates a fresh one-time pairing link before PIN setup
`start --no-open` / `stop`	Start or stop the broker; stopping interrupts active terminals and runs
`client-config CLIENT`	Print configuration for the active install without editing client files

Login startup is opt-in, not a system service or crash supervisor. Upgrade and rollback interrupt active terminals. Version 0.3.1 is not an in-place upgrade over earlier layouts or databases: evaluate it with an empty, separate data directory and disposable credentials while preserving an independent backup.

Next: connect a client · configure resources · backup and restore.