TemboMigrate the billing cron to the new queue
Fix the flaky onboarding e2e test
Add retry logic to the webhook dispatcher
BenjaPatch the rate-limit bug in the auth service
AntoineReview pull requests to identify bugs, security issues and code quality problems
Retrieve organization group ID fβ¦
Extract organization name anatβ¦
Determine charging policy for bβ¦
Create snapshot logs system wβ¦
List all accessible MCP tools in the menu
feat(ui-components): introduce chat components
Metabase MCP
Notion components: introduceβ¦
Database MCP
Home
Auto Fix Sentry Errors
Diagnoses new Sentry errors, finds the root cause, and opens a fix PR.
Use templateEnrich Linear Issue
Adds context and implementation suggestions to new Linear issues.
Use templateDaily Slack Changelog
Summarizes daily code changes and posts a formatted changelog to Slack.
Use templateReview pull requests to identify bugs, security issues and code quality problems
Generate a description whenever a new pull request is opened
Design and Construct a Spaceship Prototype
BenjaAdd new line to README using Cursor and Composer 2.5
Antoine
The Tembo stack
Large Language Models
Run any frontier model and switch between them as they improve. Tembo stays model-agnostic, so every agent uses the best LLM for the task at hand.
Agentic Harness
The orchestration that turns a model into an agent through planning, tool use, and multi-step runs. Harness-agnostic, so youβre never locked in.
Cloud Runtime
Every agent runs in its own isolated cloud VM, preloaded with your repo, tools, and dependencies. No local machine or setup required to start.
Context & Connections
Shared context across all your repos, tickets, docs, and the tools you connect, so agents and your team always work from the same picture.
Product / Control Plane
The control plane that ties every layer together, with one place to deploy, observe, and operate every agent across your whole organization.
Security & Governance
SOC 2 Type II, SSO, and role-based access come built in, with the option to self-host so the entire platform runs inside your own environment.
Tembo
Every layer above brought together in one platform your team owns, deploys, and scales end-to-end, from model to production. Thatβs Tembo.
The infrastructure layer for engineering.
When work is done by software, it no longer needs to live on a personal machine. Engineering becomes collaborative, observable, and programmable.
Tembo connects to repos, tickets, alerts, and tools to understand the work.
An agent runs in an isolated cloud environment with your dependencies and tools.
// auth.ts
export async function validateSession(token: string) {
const session = await getSession(token);
if (!session) {
throw new Error("Session not found");
}
if (session.expiresAt < Date.now()) {
await revokeSession(token);
throw new Error("Session expired");
}
return {
userId:
Reviewable PRs, updates, and artifacts your team can inspect and trust.
Benjamonorepo
Darrenmonorepo
ConnormonorepoBenjamonorepoHumans review, iterate, and approve before anything merges or ships.
The infrastructure layer for engineering.
When work is done by software, it no longer needs to live on a personal machine. Engineering becomes collaborative, observable, and programmable.
Deploy Tembo inside your own infrastructure, so your data, repos, integrations, and access policies stay within your environment.
Regulated industries
Financial services, healthcare, and government organizations.
Security-first teams
Companies that cannot send source code to third-party environments.
Any cloud provider
Organizations operating within their own AWS, Azure, or GCP environments.
Isolated environments
Teams in fully isolated networks with no public internet access.
Deploy Tembo in the environment you already trust
On PremiseTag @Tembo where the work is happening
From Slack, Linear, GitHub, the Mac app, mobile, or the web. Tembo runs agents in the background and pings your team when there is output to review.
8D8 days ago
7D7 days ago30M30min ago@Tembo what customer context should we know before scoping this?
15M15min agoI checked Attio, the latest customer call, and a Slack thread from last week. Northstar needs clearer SCIM group-to-role mapping after SSO setup.
Triggers, context, and output from Slack, Linear, GitHub, Sentry, Datadog, and more.
Agents shouldn't become your platform
Models, harnesses, and vendors will change. Your workflows shouldnβt. Use Claude Code, Codex, OpenCode, or whatever comes next. Tembo gives teams a stable system while the agent layer evolves underneath.
Use agents by mention. Call on agents directly from Slack, Jira, Linear, and more using simple @mentions.
Swap agents with a dropdown. No contract changes, no migrations. If a new model drops tomorrow, use it today. Anthropic, OpenAI, AWS Bedrock, and more.
Your configs work the same way. Existing agent configs, repo instructions, and local workflows work the same way in Tembo.
Filter models...
Auto
Composer 2.5
Claude Opus 4.7
Claude Sonnet 4.6
GPT-5.5
GPT-5.5 Pro
Gemini 3 Pro
Grok 4.20
Multiple agents
Filter agents...
Claude Code
Codex
OpenCode
Cursor
Pi
Amp
Grok Build
Antigravity
Use agents by mention. Call on agents directly from Slack, Jira, Linear, and more using simple @mentions.
Swap agents with a dropdown. No contract changes, no migrations. If a new model drops tomorrow, use it today. Anthropic, OpenAI, AWS Bedrock, and more.
Your configs work the same way. Existing agent configs, repo instructions, and local workflows work the same way in Tembo.
Review pull requests to identify bugs, security issues and code quality problems
Retrieve organization group ID for future reference
Extract organization name anatomy
Determine charging policy for breach of contract
List all accessible MCP tools in the menu
Create snapshot logs system when
Design and construct a spaceship Prototype
Performance review and feedback Implementation
feat(ui-components): introduce chat components
Metabase MCP
Fast to start, pausable, resumable. Sessions spin up in seconds and can be paused, resumed, shared with teammates, or inspected at any time.
Collaborate across the team. Involve your teammates and let them see what is running, inspect sessions, and pick up where someone else might have left off.
Any size you need. Provision any sandbox size and configuration you want: up to 128GB of RAM and 500GB of disk.
Cloud development environments for agents
Every session gets a real computer with your repo, tools, dependencies, network access, and context. Not a sandboxed prompt runner.
Fast to start, pausable, resumable. Sessions spin up in seconds and can be paused, resumed, shared with teammates, or inspected at any time.
Collaborate across the team. Involve your teammates and let them see what is running, inspect sessions, and pick up where someone else might have left off.
Any size you need. Provision any sandbox size and configuration you want: up to 128GB of RAM and 500GB of disk.
The future isnβt one agent. Itβs many.
Run agents across repos, tickets, teams, and tools in parallel. Tembo keeps the work coordinated, visible, and reviewable.
Foreground development. Work hands-on in live cloud sessions using Cursor, Claude Code, or Codex. Resume, share, or hand off anytime.
Background agents. Hand off work from Slack, Linear, GitHub, schedules, or webhooks. Tembo runs it and pings your team when output is ready.
Remove exposed API keys from audit log messages
Foreground development. Work hands-on in live cloud sessions using Cursor, Claude Code, or Codex. Resume, share, or hand off anytime.
Background agents. Hand off work from Slack, Linear, GitHub, schedules, or webhooks. Tembo runs it and pings your team when output is ready.
Cloud execution wins. Trust decides who adopts it.
The blocker isnβt capability. Itβs security, governance, compliance, and trust. Run Tembo in your own cloud, your own VPC, even air-gapped. The future of engineering doesnβt require giving up control.
Humans approve
Review, iterate, and approve every change from Tembo before anything merges.
One auditable layer
Every foreground session and background agent run is centrally logged, traceable, and reviewable.
Deploy inside your perimeter
Use Tembo Cloud, your VPC, or a self-hosted deployment. Keep code access, data, integrations, and policies under your control.
Plugs into your stack.
Logs everything
Tembo connects to the tools your team already works in and centrally logs every session from foreground to automations so nothing runs without a trail.
Implement Linear tickets end-to-end
Generate test coverage for critical flows
Create a daily engineering standup summary from Jira
Optimize slow database queries
Audit technical debt and create remediation plan
Find tickets that have been stale for a long tine
Agent templates
Pre-built agents for your most common workflows, ready to run.
- Slack thread (12 messages)
- Linear issue ENG-421
- Previous PR #184
Centralized audit logs
Every session, whether started by a human or an agent, is centrally logged.
Migrate session tokens to the new auth format
Q3 enterprise pipeline analysis
Backfill missing firmographics for ICP accounts
Update BDR lead-routing workflow
Audit API rate limits across services
Generate weekly revenue digest for leadership
Sync Salesforce account owners after re-org
Deprecate legacy webhook endpoints
Team visibility
See what teammates are working on across the team. No more hiding on a developer's laptop.
Problem:
Pagination is silently capping results again. Enterprise repos with 20+ pages of PRs come back truncated, so reviews miss the most recent commits.
Verified:
What happened then: we capped page sizes to unblock the release, but the root pagination issue in Clerk was left for later, and never came back to it.
Why it's back: enterprise accounts have more repos and users now, so the old workaround isn't enough.
Solution:
Fixing it properly this time: β Capping GitHub PR pagination at 20 pages, Bitbucket at 40 β Per-repo timeout of 30s so one slow integration can't cascade β 55s API handler timeout, returning a 504 instead of hanging.
Session memory
Session history powers context improvement and memory that compounds over time.