Dashboard, secrets, and usage

Your coding agent uses the Bahama CLI to plan infrastructure and deploy code. The Bahama dashboard gives you a clear view of the same Cloud account: projects, live status, resources, usage, secrets, and local-development access.

Projects

A project page shows the current framework, deployment URL and status, bound resources, recent activity, usage, and development tokens. You can create a project in the dashboard, but asking your agent to create it through a reviewed Bahama plan keeps bahama.yaml and bahama.lock synchronized from the start.

Use the CLI for deployments:

Deploy the latest version of this project with Bahama and tell me when the live
URL is verified.

The dashboard is the place to observe the result; it is not a replacement for the repository’s manifest and lock.

Project secrets

Open Project → Secrets to add credentials used by server code, such as an API key or webhook signing secret.

• Names use uppercase letters, numbers, and underscores and must begin with a letter or underscore.
• BAHAMA_* names and platform binding names are reserved.
• Values are write-only. The dashboard cannot reveal them later.
• Replacing or deleting a secret takes effect without redeploying source.
• Each value may be at most 5 KB.

Server code reads the chosen name from its environment object:

type Env = {
  OPENAI_API_KEY: string;
};

Do not paste the value into a coding-agent conversation. Tell the agent which variable name will exist, then enter the value yourself in the dashboard.

Usage

The account and project usage pages report requests, errors, compute time, and database activity for the selected period. The project page also shows the most active route groups and current resource storage.

Usage is attributed to the Bahama account and project. If an account reaches a current plan limit, the dashboard explains which category caused the pause and where to review the limit.

During the alpha, billing is disabled and accounts receive Pro-level access. The dashboard will announce pricing or billing changes before they take effect.

Development tokens

Development tokens authorize server-side local access to one project. The normal agent workflow creates one through the reviewed manifest bindings and writes it directly to the local environment file.

The dashboard can also create a token for recovery or a nonstandard local setup. Its raw value is shown once. Copy it directly to the server environment, then close the dialog. You can review its expiration and last use or revoke it from the project or account page.

Never put a development token in frontend code, a public environment variable, source control, logs, or chat.

Deleting a project

The project settings page can permanently delete a Cloud project and its managed resources. You must type the exact project slug, and deletion cannot start while deployment or provisioning is active.

This is different from bahama detach --approved, which deletes nothing remote and only removes the repository’s local lock.

If you delete a project in the dashboard, a repository that still contains its old bahama.lock will report the resource as missing. Do not re-plan unless you intend to recreate the project. Remove or change the manifest intent first if the application should stay offline.