
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 for the full supported model list, BYOK details, and AWS Bedrock BYOK support.Claude Code
Claude Code
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
Codex
Codex
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
Cursor
Cursor
Multi-provider via Cursor CLI.Models: Sonnet 4.5, GPT-5.2, Gemini 3 Pro, Gemini 3 Flash, Composer 1, Grok
Opencode
Opencode
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
Amp
Amp
Claude-powered with automatic model selection.
Pi
Pi
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. 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

- Go to Agents in the dashboard
- Click Templates
- Pick a template and click Use template
- Customize the instructions and enable
From scratch
- Click New Agent
- Write your instructions
- Add triggers (schedule and/or event-based)
- Select agent harness
- Instruct MCP servers or integrations
- Save and enable
Macros
You can trigger a specific agent on demand from anywhere you can mention@tembo by using its macro.
review:
Beyond code
Agents aren’t limited to engineering work. With MCP servers, agents can work across your entire stack.| Example | Trigger | What it does |
|---|---|---|
| Daily ARR report | Daily | Pulls revenue data from Stripe and posts to Slack |
| Feature requests from calls | Daily | Scans call transcripts for feature requests and creates Linear tickets |
| Customer health check | Weekly | Summarizes support tickets, usage trends, and churn signals in Slack |
| Enrich CRM records | New deal created | Pulls company info and adds context to Attio or your CRM |
| Create CRM tickets from Slack | @tembo in Slack | Creates a ticket in your CRM enriched with context from other connected integrations |

