> ## 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.

# Implement issues

> Assign issues from Linear, Jira, or GitHub and get code written for you.

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

<Steps>
  <Step title="Issue assigned">
    Create or assign an issue in [Linear](/integrations/linear), [Jira](/integrations/jira), [GitHub](/integrations/github), or mention it in [Slack](/integrations/slack). Tembo picks it up via webhook or [agent](/features/agents) trigger.
  </Step>

  <Step title="Context gathered">
    Tembo reads the issue description, pulls in related code, linked docs, and conversation history to understand the full picture.
  </Step>

  <Step title="Code written">
    A [agent harness](/features/agents#agent-harness) works in an isolated [sandbox](/features/sandbox-environment), implements the solution, and opens a [PR](/features/pull-requests) linked back to the original issue.
  </Step>

  <Step title="Review and iterate">
    Review the PR. Use the [feedback loop](/features/feedback-loop) to request changes. The agent iterates until the solution is right.
  </Step>
</Steps>

## Set up issue-to-PR workflows

### Connect your issue tracker

Navigate to the [Integrations page](https://app.tembo.io/integrations) and connect one or more of:

* [Linear](/integrations/linear)
* [Jira](/integrations/jira)
* [GitHub Issues](/integrations/github)
* [Slack](/integrations/slack)
* [Notion](/integrations/notion)

### Create an agent

**Trigger**: Issue created, issue assigned, or label added
**[MCP Servers](/integrations/mcp)**: GitHub + your issue tracker

Example instructions:

```text theme={null}
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 [agents](/features/agents) only on specific labels (e.g., `tembo`, `auto-implement`) to control which issues get picked up.
* **Start with small sessions**: Begin with well-scoped bugs and small features before tackling larger work.