Supported capabilities
Core integration- Core integration: Tembo — Connect Tembo so Sazabi can hand issue fixes to it and follow the result in the issue thread.
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 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 page.
Set up in the dashboard
1
Get your credentials
In the Tembo app, 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, create the key in your deployment’s own dashboard and note your deployment’s origin (for examplehttps://tembo.example.com).2
Open the Tembo integration
In the dashboard, go to Settings > Integrations and open Tembo.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 ofapi.tembo.io. Sazabi checks the key with Tembo before saving the connection.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 (installed and authenticated; see CLI reference). Tembo is an API-key provider, so pass its key as theapiKey credential. Read the key from an environment variable rather than pasting it inline. Self-hosted deployments add baseUrl:
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 withsazabi agent-dispatches (see CLI reference):
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 thatsazabi 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 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, and that the issue’s project has a repository Tembo can reach.Further reading
Issues
Open, investigate, and resolve issues.
Integrations
Browse the core integrations.