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."
• "Keep production login for reports but test Plan locally."
• "Switch env profiles / live vs testing."

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
   }