# How agents get credentials for Konstant

Public website access and local development do not require a Boombox login. Connected work uses the account authorized for that work.

## Install and work locally

Install the complete Boombox distribution from the [official Homebrew tap](https://github.com/KonstantCloud/homebrew-tap) or [GitHub releases](https://github.com/KonstantCloud/boombox/releases/latest):

```sh
brew install KonstantCloud/tap/boombox
```

From the project directory:

```sh
boombox project init . --client claude --client codex
```

The installation includes the CLI, TypeScript SDK, agent skills, schemas, local harness and private runtime. A separate Node, npm or Rust installation is not required. The [developer guide](https://konstant.cloud/developers) also gives the shell installer and other platform packages.

Initialization installs the `build-on-boombox` skill and registers a credential-free scan MCP connection. Reload the coding agent to use it. Repository inspection, local validation and local proof require no Boombox login. Initialization does not ingest the repository, deploy code or start a hosted runtime.

This site, its [MCP server](https://konstant.cloud/.well-known/mcp.json), [API description](https://konstant.cloud/openapi.json) and machine-readable files remain public. Requesting a conversation through the site API also requires no authentication.

## Connect a Product account

For authorized company data, capabilities, deployment or invocation:

```sh
boombox login --account
```

The browser presents authorized Product accounts by human company name. The credential is stored separately in `~/.boombox/product-account.toml` with owner-only Unix permissions. Use the returned `product_mcp` command for that connection. Account membership and grants determine which operations are available; login alone does not grant deployment or data access.

A connected application uses its own application-scoped identity. Personal CLI credentials stay separate from production service credentials. Customers do not need to create a Google token or supply an internal tenant identifier.

## Optional builder workspace

```sh
boombox login
```

Plain login connects the builder workspace for project continuity, requests for missing platform capabilities and evaluation facts. Its credential lives in `~/.boombox/config.toml`. It does not grant Product-account data, deployment, compute, billing or invocation access. Use the generated `builder_mcp` connection for that workspace and follow its project-attachment instructions when needed.

`project init --json` returns exact `scan_mcp`, `builder_mcp` and `product_mcp` commands for one project root. Only scan is registered automatically. Register a connected command explicitly after the corresponding login. Credentials are not included in project configuration, arguments or skills.

## Check, refresh and revoke

`boombox whoami --config /absolute/path/to/config.toml` checks the selected identity against its gateway. An expired credential needs a new login; missing Product-account access needs that account’s administrator. Never print or commit credential files.

`boombox credentials list` shows current-credential metadata; `boombox credentials revoke <credential_id>` revokes that credential. `boombox logout` revokes the builder-workspace credential and leaves a separate Product-account credential unchanged.

After upgrading Boombox, rerun project initialization to refresh the skill and executable path, then reload the agent. If initialization reports a changed managed file, inspect it before choosing to replace it. Unrelated project settings remain yours.

Use `boombox docs agents` and the guide included with the [official release](https://github.com/KonstantCloud/boombox/releases/latest) for the installed version. Questions: pilot@konstant.cloud.
