No. Agent OS does not include an OAuth integrations server. For channels (Telegram, Slack, Discord, Signal, Viber), you only configure tokens and default agents in Settings → Channels. Skills that need OAuth (e.g. Gmail) can use a Portal (external OAuth service) with a runtime-supplied base URL, or store credentials in skill config (e.g. user pastes a token). See Channels and Skills authoring.
In ~/.agent-os/config.json (or under AGENT_OS_HOME). The server and CLI read from this file; env vars can override. Never commit this file. Skill-specific config (e.g. API keys for a skill) is in ~/.agent-os/configs/<skill_id>.json.
Yes. Agent OS supports an optional store: set the store’s registry URL in Settings (or config). The dashboard can then list and install skills by slug. You can also install skills by copying to ~/.agent-os/skills/ or using Install system skills from the seed dir. See Store.
~/.agent-os/skills/<name>/) with skill.yaml (or SKILL.md) and optional tools.yaml. It registers tools and may require config (API keys, etc.).~/.agent-os/skills/ or use Install system skills (dashboard or API).~/.agent-os/skills/<name>/ with skill.yaml (or SKILL.md) and optional tools.yaml, then restart the server (or use Install system skills if the skill is in the seed dir).See Skills authoring.
By default, no. The server binds to 127.0.0.1 (localhost). Only processes on your machine can reach it unless you set HOST to another address or put the server behind a reverse proxy and expose it.