Skip to main content
Tembo picks up issues from your project management tools and writes code to solve them, whether it’s a bug, a feature, or a refactor.

​
How it works

1

Issue assigned

Create or assign an issue in Linear, Jira, GitHub, or mention it in Slack. Tembo picks it up via webhook or automation trigger.
2

Context gathered

Tembo reads the issue description, pulls in related code, linked docs, and conversation history to understand the full picture.
3

Code written

A coding agent works in an isolated sandbox, implements the solution, and opens a PR linked back to the original issue.
4

Review and iterate

Review the PR. Use the feedback loop to request changes. The agent iterates until the solution is right.

​
Set up issue-to-PR workflows

​
Connect your issue tracker

Navigate to the Integrations page and connect one or more of:

​
Create an automation

Trigger: Issue created, issue assigned, or label added MCP Servers: GitHub + your issue tracker Example instructions: 
When a new issue is assigned to Tembo:
1. Read the issue description and any linked context
2. Identify the relevant files in the codebase
3. Implement the solution following our coding standards
4. Write tests for the changes
5. Open a PR and link it to the original issue

​
Your team stays in control

Tembo generates solutions autonomously, but your team decides what gets deployed:
  • Review PRs using your standard review process
  • Mention @tembo in PR comments to request changes. It iterates on the feedback
  • Approve and merge when you’re satisfied

​
Best practices

  • Write clear issue descriptions: The more context in the issue, the better the implementation.
  • Use labels: Trigger automations only on specific labels (e.g., tembo, auto-implement) to control which issues get picked up.
  • Start with small tasks: Begin with well-scoped bugs and small features before tackling larger work.