Environment variables.
Give your agents the tokens and settings their tools need —
GH_TOKEN for gh, a database URL, a proxy —
without putting them in a prompt. DayMug has two places for
variables: yours, and the provider account's.
Your variables
- Open Settings → Advanced → Environment variables. Every user has this page.
-
Write one
VAR=VALper lineNames start with a letter orGH_TOKEN=ghp_… GITLAB_TOKEN=glpat-… HTTPS_PROXY=http://proxy.internal:3128_and contain only letters, digits and_. Values may be empty or contain=. Blank lines are ignored; a malformed line is rejected when you save, with its line number. - Save environment — the next turn of every agent you own picks it up, in the browser, in IM and in scheduled tasks. A task already running keeps the old values.
The values apply to all your agents — agents have no variables of their own. Admins don't see them in the user list.
Provider account variables
Admins can set variables on each provider account (Settings →
Administration → Providers & models → account →
Environment variables). They reach every conversation on
that account, for every user bound to it — the place for an
endpoint's ANTHROPIC_BASE_URL or
OPENAI_API_KEY (see
Compatible endpoints).
Which value wins
Each agent process gets, in this order — a later layer overrides an earlier one:
| # | Layer | Set by |
|---|---|---|
| 1 | The DayMug service's own environment | whoever runs the service |
| 2 | Provider account variables | admins |
| 3 | Your variables | you |
| 4 | CLAUDE_CONFIG_DIR / CODEX_HOME from the account's credential directory | DayMug — can't be overridden |
Variables are stored in DayMug's database. Anything an agent can read it can also print, so give each token only the permissions the agent needs.