Install SecretBridge with your AI assistant

Install or reuse SecretBridge on this computer and connect it to the MCP-capable AI client I am using. Product repository: https://github.com/qq940500529/secretbridge. Carry out the deployment and read-only connection check where possible; do not stop at listing instructions. Start from any directory and do not assume the repository is cloned.

1. First check the current client's SecretBridge MCP entry, PATH, and the documented platform-default installation record. Run status with any candidate binary. Reuse a healthy, suitable installation; if its broker is stopped, start it with the active installed binary. Do not install another copy just because this is a new chat or client. Ask me for an unknown custom install location before proceeding.
2. For a new installation, read AGENTS.md, SECURITY.md, and docs/getting-started/AI辅助部署.md, 自动化部署运行手册.md, and 安装与服务管理.md in the repository. Check this computer's OS and architecture. Prefer the latest suitable native GitHub Release, download its .sha256 sidecar, compare the digest, and run verify-package. Build the latest main in a new directory with the documented checks only if no suitable release package exists.
3. Before changing installation directories, system settings, or MCP client configuration, show the target, commands, and necessary backup, then wait for my approval. Version 0.3.1 cannot be installed over older data; retain the old installation and an independent backup, and use a separate empty data directory for evaluation. Stop and diagnose any failed download, verification, build, or install step. Do not skip checks, overwrite old data, or weaken local security settings.
4. Start or reuse the broker and confirm healthy status and a loopback-only console. Use the active binary returned by install or status to run client-config CLIENT. Merge only the SecretBridge entry into this client's format and reload it. Confirm the tools appear, then call the read-only secretbridge_terminal_capabilities tool. If safe configuration is not possible, give me a precise paste-ready fragment and reload steps.
5. After a new installation, inspect install.management_page. If it is opened, do not call open again. If it is manual_open_required and this computer has an interactive desktop, use the active binary's open command to show the local console. I will personally accept the terms, set a PIN/passphrase, save the recovery key, and optionally bind an authenticator in the local page. Do not read, enter, capture, or relay those values or a one-time pairing link.
6. Recheck broker health and the read-only MCP capability, then report whether you reused or installed, the version, verification results, and remaining human steps. Do not inspect existing credential-store entries or expose secrets, personal paths, private hosts, or pairing material in chat, commands, environment variables, logs, or shared reports.

Based on the product repository's deployment guide Use the reference below if your AI client cannot run commands locally.