Dailybot Env

Dailybot per-repo API key override (env.json)

Requires dailybot-cli >= 3.9.0 (the skill-pack baseline). The dailybot env command group and .dailybot/env.json loader shipped in 3.7.0 and are included in this floor. If dailybot --version reports below 3.9.0, ask the developer to run dailybot upgrade before continuing. See ../SKILL.md § Required Dailybot CLI version.

This sub-skill lets an agent configure and manage <repo>/.dailybot/env.json — an opt-in, gitignored file that pins API keys + URL overrides per environment (live, local, staging) for the enclosing repo. When a profile is active, it overrides DAILYBOT_API_KEY, config.json, and the login Bearer session only for that repo.

The full workflow, schema, security rules, and worked examples live in ../shared/env-json.md. Read it first — it is the single source of truth. This file is the routing entry-point and quick-reference.

When to use

Route here when the developer says any of:

• "I want a local API key just for this project."
• "How do I test against staging without breaking my prod login?"
• "Can I be in org A in this repo and org B in another repo?"
• "Set up per-project Dailybot credentials for me."
• "Switch this repo to my localhost Dailybot instance."

Do not route here when:

• The developer is in CI. Use DAILYBOT_API_KEY as an env var — leaves no on-disk secret.
• The developer wants team-shared identity (agent name, default metadata). That's .dailybot/profile.json — see ../shared/repo-profile.md.
• The developer has one Dailybot org and a working login session. dailybot login + global config is simpler.

Pre-flight — before writing anything

1. Confirm the CLI meets the pack baseline (>= 3.9.0):

   dailybot env --help >/dev/null 2>&1 || {
     echo "This feature requires dailybot-cli >= 3.9.0. Run: dailybot upgrade" >&2
     exit 1
   }
   

2. Ensure the repo's .gitignore covers .dailybot/*. The Dailybot skill pack expects this pattern:

   .dailybot/*
   !.dailybot/profile.json
   

   If missing, add it (creating .gitignore if needed):

   grep -q '^\.dailybot/\*' .gitignore 2>/dev/null || cat >> .gitignore <<'EOF'
   
   # Dailybot per-repo state (env.json contains API keys — never commit it)
   .dailybot/*
   !.dailybot/profile.json
   EOF
   

   If the developer skips this step and later commits env.json, the CLI will refuse to load it and print an actionable error. dailybot env add also fires a soft warning when the file isn't gitignored yet.

The commands (quick reference)

# CREATE a profile (creates the file if needed; first profile auto-becomes active)
dailybot env add --name NAME --key KEY [--api-url URL] [--app-url URL]

# SWITCH active profile
dailybot env use NAME       # switch active
dailybot env use ""         # clear active (fall through to global auth)

# INSPECT
dailybot env show           # resolved profile (API key masked)
dailybot env list           # all profiles, active marked

# DELETE
dailybot env remove NAME [--yes]

# KILL SWITCH (preserves active)
dailybot env off            # disable the file
dailybot env on             # re-enable

All API keys are masked in output (sk_l****). The CLI never echoes the full key back.

Common recipes

First-time setup for a local dev org

dailybot env add \
  --name local \
  --key sk_local_xxxxxxxx \
  --api-url http://localhost:8000 \
  --app-url http://localhost:8090

dailybot env show   # verify

Because this is the first profile, it becomes active automatically. Every subsequent dailybot command in this repo now talks to http://localhost:8000. Other repos are unaffected.

Toggle between staging and prod

dailybot env add --name prod    --key sk_prod_xxxx           # first → auto-active
dailybot env add --name staging --key sk_staging_yyyy \
                                --api-url https://staging-api.example.com

dailybot env use staging   # switch to staging for bug repro
# ... work in staging ...
dailybot env use prod      # switch back

Temporarily disable env.json without losing setup

dailybot env off   # env.json ignored; CLI falls through to global auth
# ... test something with your global login ...
dailybot env on    # restores the previously active profile

env off sets disabled: true at the top level; active is preserved so env on instantly restores the previous selection.

Delete a profile

dailybot env remove staging --yes
# If 'staging' was active, active is cleared and the CLI falls back to
# global auth until you run `dailybot env use <name>` again.

Security — what an agent must never do

1. Never cat or otherwise print raw env.json. It contains API keys. Use dailybot env show / dailybot env list — they mask.
2. Never suggest committing env.json. The CLI has a fatal RepoEnvError guard that fires on load if the file is tracked.
3. Never write API keys into .dailybot/profile.json. That is a hard error in the CLI. env.json is the ONLY sanctioned place inside .dailybot/ for credentials.
4. If the developer accidentally committed env.json: tell them to rotate every key immediately (assume compromise), then git rm --cached + fix .gitignore + rewrite env.json with newly generated keys. Do NOT try to git filter-repo the leak away — assume the world has seen the keys.

Full four-layer protection story (gitignore, 0o600, fatal refuse-if-tracked, write-time gitignore warning): see ../shared/env-json.md § Security.

Interaction with existing auth (short version)

Precedence order (full table in ../shared/env-json.md § Auth resolution order).

Troubleshooting (quick reference)

• "The CLI is not using my env.json." → dailybot env show; check disabled, active, and the walk-up path. Are you overriding with --profile / --api-url / --app-url flags?
• "The CLI refuses to run and complains about tracked env.json." → run the exact fix printed in the error message. Staged-but-uncommitted counts as tracked. (dailybot hook * commands print the error but still run and exit 0 — by design, per their harness contract.)
• "I edited env.json by hand and now nothing works." → dailybot env show surfaces schema warnings; if unrecoverable, delete the file and re-add profiles via dailybot env add.
• "I set disabled: "true" and it's still active." → disabled must be a JSON boolean; the CLI warns and treats a string as false. Use dailybot env off.

See also

• ../shared/env-json.md — full schema, precedence, security posture, worked examples.
• ../shared/repo-profile.md — the sibling profile.json file (agent identity, tracked in git).
• ../shared/auth.md — general authentication flow (OTP login, API key alternatives, CLI installation).