> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tembo.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Agents
> Run coding agents on a schedule or triggered by events.
Run coding agents in the background, on a schedule or triggered by events. A Sentry error gets fixed within seconds. Docs stay in sync with your code. Security vulnerabilities get caught before they become problems.
Each agent runs in a secure [sandbox](/features/sandbox-environment) with full codebase and repository access and your configured [MCP servers](/integrations/mcp).
## Agent harness
Tembo is harness and model agnostic. For each agent you configure, you pick the harness (and model) that runs in the session it spawns, for example Claude Code with Sonnet 4.6, Codex with GPT-5.4, or Cursor. Set a default per agent, or override per session.
See [Models](/features/models) for the full supported model list, BYOK details, and AWS Bedrock BYOK support.
}>
Anthropic's Claude models. Best balance of quality, reliability, and cost.
**Models:** Opus 4.6, Sonnet 4.6, Opus 4.5, Sonnet 4.5, Haiku 4.5
}>
OpenAI's GPT-5 family with configurable reasoning effort (minimal, low, medium, high).
**Models:** GPT-5.4, GPT-5.4 Mini, GPT-5.4 Nano, GPT-5.3 Codex, GPT-5.2, GPT-5.2 Codex, GPT-5.1, GPT-5.1 Codex Max, GPT-5.1 Codex Mini
}>
Multi-provider via Cursor CLI.
**Models:** Sonnet 4.5, GPT-5.2, Gemini 3 Pro, Gemini 3 Flash, Composer 1, Grok
}>
Multi-provider support: Anthropic, OpenAI, and OSS models.
**Models:** Opus 4.6, Sonnet 4.5, GPT-5.4, GPT-5.4 Mini, GPT-5.4 Nano, GPT-5.2, GPT-OSS 120B, Qwen 3 32B, Llama 3.3 70B, Kimi K2.5, GLM 5
}>
Claude-powered with automatic model selection.
}>
A minimal, extensible terminal coding harness with multi-provider support.
**Providers:** Anthropic, OpenAI, Google Gemini, GitHub Copilot, Azure OpenAI, Amazon Bedrock, Mistral, Groq, xAI, OpenRouter, and more
## Triggers
These are just examples to give you a rough idea. You decide how to set this up, there are no limitations.
### Scheduled
Run agents at regular intervals.
| Schedule | Example |
| ----------- | ------------------------------------------- |
| **Hourly** | Monitor for CI failures, new Sentry errors |
| **Daily** | Generate changelogs, post standup summaries |
| **Weekly** | Clean up stale TODOs, security scans |
| **Monthly** | Dependency audits, documentation reviews |
### Event-driven
React to events from your integrations in real-time.
| Integration | Events |
| ----------- | -------------------------------------------------- |
| **GitHub** | PR opened, PR merged, issue created, comment added |
| **GitLab** | Merge request opened, merged, issue created |
| **Sentry** | New error, error spike, regression detected |
| **Linear** | Issue created, issue updated, status changed |
| **Slack** | Message in channel, @tembo mention |
#### Trigger through webhooks
You can trigger an agent on demand from external systems using the agent's [webhook trigger endpoint](/api/trigger-agent).
The payload is passed to the agent as event context, so your instructions can reference it directly. For example, you could write instructions like *"Fix the issue at the URL provided in the event payload"*.
## Creating an agent
### From a template
1. Go to **Agents** in the [dashboard](https://app.tembo.io)
2. Click **Templates**
3. Pick a template and click **Use template**
4. Customize the instructions and enable
[Browse all templates](https://tembo.io/for)
### From scratch
1. Click **New Agent**
2. Write your instructions
3. Add triggers (schedule and/or event-based)
4. Select [agent harness](#agent-harness)
5. Instruct MCP servers or integrations
6. Save and enable
## Macros
You can trigger a specific agent on demand from anywhere you can mention `@tembo` by using its macro.
```txt theme={null}
@tembo !
```
Tembo routes the request to the agent with that macro and passes the rest of the message as the prompt.
For example, this triggers the agent named `review`:
```txt theme={null}
@tembo !review please review this PR
```
## Beyond code
Agents aren't limited to engineering work. With [MCP servers](/integrations/mcp), agents can work across your entire stack.
| Example | Trigger | What it does |
| ----------------------------- | ---------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Daily ARR report | Daily | Pulls revenue data from [Stripe](/integrations/mcp) and posts to [Slack](/integrations/slack) |
| Feature requests from calls | Daily | Scans call transcripts for feature requests and creates [Linear](/integrations/linear) tickets |
| Customer health check | Weekly | Summarizes support tickets, usage trends, and churn signals in [Slack](/integrations/slack) |
| Enrich CRM records | New deal created | Pulls company info and adds context to [Attio](/integrations/mcp) or your CRM |
| Create CRM tickets from Slack | `@tembo` in [Slack](/integrations/slack) | Creates a ticket in your CRM enriched with context from other connected integrations |
Any tool with an [MCP server](/integrations/mcp) can be used as an agent.
You can also do this on-demand from [Slack](/integrations/slack) without setting up an agent:
```
@tembo What's our ARR right now? Check Stripe.
```
```
@tembo Summarize the feature requests from this week's sales calls and create Linear tickets for the top 5.
```