> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tembo

> Connect Tembo so Sazabi can hand issue fixes to it and follow the result in the issue thread.

## Supported capabilities

Core integration

* **Core integration**: [Tembo](https://docs.sazabi.com/catalogs/integrations/tembo.md#core-integration) — Connect Tembo so Sazabi can hand issue fixes to it and follow the result in the issue thread.

Each connection method has its own setup and permissions. Connecting one method does not enable the others.

## Core integration

## About

Connecting Tembo lets Sazabi hand an issue's fix to Tembo. You choose **Fix** on an issue, Tembo works in your repository in a Tembo session and opens a pull request, and Sazabi follows its progress in the issue thread. Tembo is a **coding agent** integration: one of the agents listed under [**Settings > Integrations**](https://app.sazabi.com/settings/integrations) that Fix can hand off to.

## Prerequisites

* A Tembo organization API key.
* Organization admin access in Sazabi.
* Repository access for Tembo: Tembo works in the GitHub repositories turned on under its [Integrations](https://app.tembo.io/integrations) page.

## Set up in the dashboard

**Step 1**

### Get your credentials

In the [Tembo app](https://app.tembo.io), open your organization's **Settings > API keys** and create an **organization API key**. Tembo shows the complete key once, so copy it before you leave the page. Keys expire on the schedule you choose when creating them; reconnect with a new key when one expires.

If your organization runs [self-hosted Tembo](https://docs.tembo.io/features/self-hosted/overview), create the key in your deployment's own dashboard and note your deployment's origin (for example `https://tembo.example.com`).

**Step 2**

### Open the Tembo integration

In the dashboard, go to [**Settings > Integrations**](https://app.sazabi.com/settings/integrations) and open **Tembo**.

**Step 3**

### Connect with the key

Choose **Connect** and paste the key. Leave **Server URL** empty for Tembo's hosted service; for self-hosted Tembo, enter your deployment's origin and Sazabi calls its API there instead of `api.tembo.io`. Sazabi checks the key with Tembo before saving the connection.

**Step 4**

### Check repository access

The connection page's **Repositories** section shows which repositories Fix can hand to Tembo. **Default coding agent** is set per project, so it appears only when you open the connection from a project's settings: open the project, go to its **Integrations** settings, select Tembo, and choose **Use this account**. Fix then hands off to it without asking.

## Set up with the CLI

You can also connect Tembo with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated; see [CLI reference](https://docs.sazabi.com/reference/cli/integrations.md)).

Tembo is an API-key provider, so pass its key as the `apiKey` credential. Read the key from an environment variable rather than pasting it inline. Self-hosted deployments add `baseUrl`:

```bash theme={"system"}
export TEMBO_API_KEY=...   # your Tembo organization API key
sazabi integrations connect tembo \
  --credentials "{\"apiKey\":\"$TEMBO_API_KEY\"}"
```

Run `sazabi integrations list` to confirm the connection, or `sazabi integrations providers --json` to see each provider's credential fields.

## Fix issues

Open an issue in the project inbox, choose **Fix**, and pick Tembo. Confirm the repository, and the base branch if asked, then choose **Fix with Tembo**. Tembo starts a session in the repository and opens a pull request; the issue thread shows the attempt's card with its status, Tembo's progress and questions, and the pull request link when it opens. Reply from the card to answer a question, or stop the attempt from the same card.

From the CLI, hand the fix off and follow the attempt with `sazabi agent-dispatches` (see [CLI reference](https://docs.sazabi.com/reference/cli/agent-dispatches.md)):

```bash theme={"system"}
sazabi issues fix "$ISSUE_ID" --agent tembo
sazabi agent-dispatches list --issue-id "$ISSUE_ID"
```

`sazabi agent-dispatches reply` answers a question from the agent, and `sazabi agent-dispatches cancel` stops the attempt.

## Verify

Choose **Fix** on an open test issue and hand it to Tembo. Confirm the attempt appears in the issue thread within a minute, and that `sazabi agent-dispatches list --issue-id "$ISSUE_ID"` lists it with Tembo as the agent.

## Troubleshooting

**Tembo did not accept this key** - The key is wrong, expired, revoked, or from another organization. Create a new organization API key and reconnect. For self-hosted Tembo, also confirm the server URL is your deployment's origin.

**Tembo can't reach this repository yet** - Tembo works in the GitHub repositories turned on under its [Integrations](https://app.tembo.io/integrations) page. Install Tembo's GitHub App for the repository's organization, then turn the repository on under **Active repositories**.

**Fix doesn't offer Tembo** - Confirm the connection shows connected under [**Settings > Integrations**](https://app.sazabi.com/settings/integrations), and that the issue's project has a repository Tembo can reach.

## Further reading

> [card] [Issues](https://docs.sazabi.com/guides/detect/issues.md)
>
> Open, investigate, and resolve issues.

> [card] [Integrations](https://docs.sazabi.com/catalogs/integrations.md)
>
> Browse the core integrations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.