On this page

For Teams

Give every engineer the same Claude Code environment — configured and authenticated — in a single command.

Standardized environments

When every engineer runs streb init, they get the same versions of Git, Bun, Claude Code CLI, jq, and yq, configured the same way. No manual setup guides. No "works on my machine" mismatches.

  • New engineers are productive on day one
  • Everyone uses the same tool versions
  • streb doctor gives a consistent health-check baseline

Choosing an auth provider for your org

Provider Best for Setup
adesso AI Hub adesso teams with a managed Anthropic endpoint Distribute STREB_AIHUB_KEY or ANTHROPIC_AUTH_TOKEN as a secret in your CI/CD and onboarding docs
Anthropic API key Teams with direct Anthropic accounts Each developer creates their own API key at console.anthropic.com
Claude subscription Individual developers with Claude Pro/Max Each developer logs in via claude login — no shared key
Note

For team environments, prefer env vars (STREB_AIHUB_KEY) over committed config. This keeps keys out of the repository and allows rotation without code changes.

What to commit vs. keep local

Item Commit? Notes
.streb/config.yaml ✅ Yes Project name and shared team settings. No tokens.
.streb/session ❌ No Device-encrypted. Contains API keys. Add to .gitignore.
~/.streb/config.yaml ❌ No User-level. Each developer manages their own.

Recommended .gitignore entry:

.streb/session

Security posture

Secrets at rest

All API keys and tokens stored in .streb/session are encrypted with AES-256-GCM. The encryption key is derived from a device fingerprint (stable per machine: machine-id on Linux, IOPlatformUUID on macOS, MachineGuid on Windows). The session file is only readable on the machine that created it.

Fingerprint change behavior

If the device fingerprint changes (hardware replacement, VM snapshot), streb surfaces a warning and asks you to re-authenticate. It does not silently fail or expose partial data.

CI/CD

Use environment variables (STREB_AIHUB_KEY) injected by your CI secrets manager. streb env vars override the session file, so no session file is needed in CI.

No outbound calls except on demand

streb only makes network calls when explicitly asked (during streb init validation). It does not phone home or send telemetry.

Rollout checklist

  1. Choose an auth provider — AI Hub (recommended for adesso teams), Anthropic API key, or Claude subscription.
  2. Add .streb/config.yaml to the repository — Set project.name and any shared team settings.
  3. Add .streb/session to .gitignore — Prevent accidental token commits.
  4. Share the auth key — Distribute STREB_AIHUB_KEY via your onboarding docs or secrets manager. Never commit it.
  5. Tell developers to install streb and run streb init — They'll pick up the project config automatically.
  6. Verify with streb doctor — Run on a sample machine to confirm the green across all checks.