Agent Settings
Every agent has a settings page where you control its name, AI model, data source connections, connected agents, and knowledge context. The settings page is organized into three tabs.
General Tab
Section titled “General Tab”The General tab contains the agent’s basic configuration.
- Agent name — Edit the display name at any time. Choose a name that clearly describes the agent’s role (e.g., “Backend Debugger” or “Growth Analyst”).
- AI model — By default, each agent uses the global AI model set in your account settings. You can override this on a per-agent basis by selecting a specific model from the dropdown. This is useful if you want certain agents to use a more capable model while keeping others on a lighter, faster option.
Settings Tab
Section titled “Settings Tab”The Settings tab controls which data sources and agents are available to this agent.
Connections
Section titled “Connections”Connections are displayed as a checkbox list grouped by category:
- Analytics — PostHog, Amplitude, GA4
- Logs — Axiom, Cloudflare, Google Cloud Logging, AWS CloudWatch
- Code — GitHub
- Databases — Cloudflare D1, Supabase, SQL, DynamoDB, Firestore
Only categories compatible with the agent’s type are shown. A Debugger agent sees logs, code, and databases. An Analyst agent sees analytics and databases. Enable or disable individual connections by toggling the corresponding checkbox.
Before a connection appears here, it must first be created in the Connections section of OpsTower.
Connected Agents
Section titled “Connected Agents”Below the connections list, you can toggle other agents as data sources for this agent. When enabled, the agent can delegate questions to the connected agent during a conversation. This is useful for cross-domain investigation — for example, a Debugger agent asking an Analyst agent about recent metric changes while investigating an error.
For more details on how this works, see Agent-to-Agent Communication.
Knowledge Tab
Section titled “Knowledge Tab”The Knowledge tab lets you attach additional context that the agent includes when answering questions. There are three types of knowledge you can configure:
- Custom knowledge — Free-form text that appears in the agent’s system prompt. Use this for business context, architecture notes, or naming conventions.
- Knowledge files — PDF, TXT, or Markdown files from your shared knowledge library. Attach relevant files so the agent can reference them.
- Attached reports — Analytics reports that provide historical data context.
For detailed information on each knowledge type and its limits, see Knowledge.