SecretBridge frequently asked questions

Does SecretBridge give my password to AI?

There is no credential read or export MCP API. The local broker uses saved credentials only for approved operations, and returned results remain filtered. The user approves a specific request in the local management page; AI cannot approve its own request through MCP. Read about approvals and security boundaries.

How do I connect Codex to SecretBridge?

Install and initialize the local broker first, then follow the client connection guide to export the plugin or configure stdio MCP. Current Codex CLI versions have a marketplace compatibility issue, so verify that a new conversation can actually call read-only tools. A listed plugin alone is insufficient, and connection does not grant approval.

What if I do not know the SSH host-key fingerprint?

After saving the SSH address and port in the local management page, you can retrieve a network-observed public fingerprint. Compare it with an independent trusted source such as a server console or administrator before confirming, saving and testing the connection. Never bypass verification when it changes. See the SSH host-key guide.

What editions exist, and can I upgrade in place?

The current open-source edition is licensed under AGPL-3.0-or-later; separate commercial rights require a written agreement. Enterprise is still a plan with no published price or launch date. Version 0.3.1 does not guarantee direct upgrades of older databases or configuration bundles; evaluate in a new empty data directory and keep the earlier installation and backup. The management page binds to loopback only and should not be exposed publicly.

Do I reinstall when switching AI clients?

No. Inspect the existing status and active binary path, then connect the new client to the same broker and data directory. Upgrade only after checking a suitable release; a new conversation is not a reason to upgrade. Client setup.

Can the AI request an operation without a saved task template?

Yes. It may propose an exact one-off command for an existing resource and secure terminal, or a structured SSH request. The user still reviews and authorizes it. Save a template explicitly only for stable repeated work. Fixed programs.

Can arguments change after approval?

No. Approval stores the target, operation, resolved ordinary parameters, credential slots and version snapshot. Creating the run does not accept replacement parameters. A changed template, target or secret makes an old grant unusable for the new version. Authorization scope.

Does a timeout, disconnect or cancellation mean nothing ran remotely?

No. An HTTP write, Git push, SFTP replacement, SSH command or database query may have reached the target. Inspect the original run and target before retrying with any new idempotency key. Troubleshooting.

Does a backup recover passwords and sessions?

No. SQLite backup excludes OS credential-store secret values; re-enter secrets and authorize again after recovery. PTY processes, browser sessions and MCP connections do not resume. Configuration JSON and full backup have different purposes. Backup and restore.

Why must a human still review output?

The broker filters bound secrets in supported representations. Business data, unbound secrets, hashes or deliberate transformations can still appear. Field selection and size limits do not replace human judgment. Security model.