Skip to main content
Delegate work to any coding agent. Tembo works autonomously with Claude Code, Cursor, Codex, and more to ship features, review code, and take on work from Slack, Linear, or anywhere else. How Tembo Works

What can Tembo do?

  • Fix production bugs — Monitor error tracking tools like Sentry and automatically generate PRs to fix the errors.
  • Implement from issues — Assign issues from Slack, Linear, Jira, Github, etc. to Tembo and it writes code to solve the issue, whether it’s a bug, a feature, or a refactor.
  • Reduce technical debt — Periodic analysis of your codebase to identify technical debt, security vulnerabilities, and refactoring opportunities, then submits PRs for quick wins.
  • Write & update documentation — Using your monorepo as the source, update your docs repo to ensure features are well-documented.
  • Automations keep you moving. Offload repetitive work to Tembo, powered by full MCP support, so you can stay focused on what matters.
  • Multi-repository support. Easily spin off a single task and have Tembo open PRs across multiple repositories when you request it or when the situation calls for it.

How It Works

Tembo functions through a cycle of detection, execution, and review:
  1. Detection - Issues are identified through integrations (Sentry errors, database metrics) or manually assigned (Linear/Jira tickets, direct task creation)
  2. Execution - Tembo analyzes the codebase using your configured coding agent and generates a solution in an isolated sandbox environment
  3. Pull Request - Changes are submitted as a pull request with context about the problem and solution
  4. Feedback Loop - You can provide feedback by mentioning @tembo in PR comments, and it will iterate on the changes

What about my team?

Your team maintains control over what code gets merged:
  1. Review pull requests created by Tembo using your standard review process
  2. Provide feedback through PR comments (mention @tembo to trigger updates)
  3. Approve and merge changes when satisfied with the implementation
  4. Configure which issues and signals Tembo responds to through integration settings
Tembo generates solutions autonomously, but your team decides what gets deployed. We have a Feedback Loop for reviewing Tembo’s work from your source control provider. If you use AI-powered code review tools like Graphite, CodeRabbit, or Cursor Bug Bot, Tembo will validate and commit relevant changes if you enable this feature.

Work from Anywhere

Tag @tembo from wherever you already work—whether that’s triaging in Slack, planning in Linear or Jira, reviewing code on GitHub, or launching tasks from Raycast and the Tembo Dashboard. No context switching required.

Supported Integrations

TypeIntegrations
Source ControlGitHub, GitLab, Bitbucket
Project ManagementLinear, Jira
Monitoring & ObservabilitySentry
DatabasesPostgreSQL, Supabase, AWS RDS
CommunicationSlack, Raycast
Most integrations use OAuth for secure connection. After authorization, Tembo syncs your data and you can activate the repositories or projects you want monitored.

Available Coding Agents

Coding AgentModel ProvidersDefault ModelRule Files
Claude CodeAnthropicclaude-4-5-sonnetclaude.md
CodexOpenAIgpt-5-mediumagents.md
OpencodeAnthropicclaude-4-5-sonnetagents.md
AmpAnthropic (auto-selected)claude-opus-4-5agents.md
CursorAnthropic/OpenAI/Google/Cursor/XAIclaude-4-5-sonnetagents.md
See Coding Agents for detailed information on each coding agent and how to choose the right one for your tasks.

Configuration

Rule Files You can provide coding agent-specific instructions through rule files in your repository. These define coding standards, project conventions, and architectural patterns for Tembo to follow. Hooks Hooks allow you to execute custom logic before and after Tembo’s actions, enabling integration with your existing CI/CD pipelines and workflows. MCP Servers Model Context Protocol (MCP) servers extend Tembo’s capabilities by providing additional tools and context sources that coding agents can access during task execution.