# Flowork Settings: Managing API Keys, Global Defaults, and Agent Configuration > Source: > Published: 2026-06-16 14:00:37+00:00 Your owner-level control panel lives here — global stuff that isn't tied to any one agent, kept in the global `flowork.db` . Every API key, token, and default lives in one place, never hardcoded in code. The **Account** section lets you change your password or log out. Keep these credentials secure; they gate everything below. This is where every external credential goes — your Dev.to key, social cookies, and so on. Nothing is ever written into the source code; agents read these at boot from here. **The easy path: service chips.** Under the input there's a row of **service chips** (Dev.to, X, LinkedIn, Telegram…). Tap one and it auto-fills the exact variable name for you — you don't have to guess whether it's `DEVTO_API_KEY` or `DEVTO_KEY` . Then paste the value and hit **Save**. A chip turns **green** once its key is set, so you can see at a glance what's already configured. **Manual entry.** Type the name yourself (must be `UPPER_SNAKE_CASE` , e.g. `ETHERSCAN_API_KEY` ) in the first box, the value in the second, then **Save**. Name suggestions appear as you type. **Edit and delete.** Each saved key shows masked — only the last 4 characters visible. *Edit* re-fills the name and clears the value box for a fresh paste; *Delete* removes it entirely. **Reserved names are blocked on purpose** — anything that could hijack the process or its child commands (`PATH` , `LD_*` , `DYLD_*` , `FLOWORK_*` , `HOME` , `GIT_*` , …). That's a safety rail, not a limitation. **How it reaches agents.** When you save a key it's stored in `flowork.db` *and* injected into the running process immediately (no restart needed). On the next boot, keys are loaded **before** agents start, so an agent always sees them in its environment. A dev platform agent, for example, reads its own key via `os.Getenv("DEVTO_API_KEY")` . The **global default** that agents fall back to when they don't pin their own: `claude-haiku-4-5` . Leave it empty to use the built-in default.`http://127.0.0.1:2402` . Leave it empty for the built-in local router. Must be a localhost address — an external URL is rejected and falls back to the default (a safety rail against routing traffic somewhere it shouldn't go).**Per-agent settings always win.** If an agent sets its own model, that choice is kept. These two values only fill the blank for agents that set nothing. Saving takes effect live and is also applied before agents boot. Why use the local router? It injects the anti-hallucination antibody — your agent's most-recurrent, most-relevant past mistakes ranked by relevance — before the model answers. A raw third-party API gets none of this. The router is model-agnostic; swap the model in one place and route to a subscription service or a local model seamlessly. Paste your bot token + chat ID, hit **Save**, then **Test** (it sends you a test message). This is the token the whole system uses to ping you — yours, never hardcoded. It's how agents (and the system itself) reach you when something matters. Connect a YouTube account by OAuth for automations that need it. The credential is stored securely here and available to agents that declare it in their tools list. The Guardian shows you which files it's watching for integrity violations. It's your immune system: monitoring the agent's doctrines and memories for poisoned or corrupted data, and quarantining threats before they spread. Everything global belongs here — never paste a key into a file, a per-agent box, or environment directly. If a tutorial asks you to, it's out of date. Your keys, your defaults, your Telegram token, your OAuth creds — one place, kept apart from each agent's private settings. Agents are isolated citizens; they share nothing unless you wire them. Disable one and nothing else notices. 💬 **Join the Flowork community on Telegram:** [https://t.me/+55oqrk75lc43YWE1](https://t.me/+55oqrk75lc43YWE1)