secret-setup

Configuring secret storage for API tokens involves choosing between Bitwarden, local encrypted storage, or manual entry. The setup verifies CLI availability, manages the login flow, and persists the session state without exposing your credentials.

Managing Bitwarden session state is done by logging in through a setup workflow that persists the session. This allows the main Instar setup to continue smoothly and avoids interactive CLI hangs during future agent operations.

Bitwarden secret management works without interactive CLI hangs by collecting only the needed login details and managing the unlock flow programmatically. This prevents the terminal from stalling during the agent onboarding process.

You can use local encrypted storage instead of Bitwarden for bot credentials. The setup workflow guides you through backend selection, allowing you to choose local storage and record the selected backend for the Instar agent configuration.

Securely restoring agent secrets on a new machine without retyping is achieved by configuring a centralized backend like Bitwarden during the initial setup. The persisted session state allows the agent to retrieve API tokens and bot credentials automatically.