Skip to content
Tembo Agent Studio

Introduction

Tembo Agent Studio (TAS) is a control plane for AI agents. Agent definitions live as files in a Git repository you own. Every change — whether an engineer typed it, a PM described it in chat, or an end user clicked “this is wrong” — lands as a diff in your repo, through pull-request review by default or a direct commit when YOLO mode is enabled. Runs and audit logs stay tied to your workspace.

Agents are software. Most teams treat them as something else: prompts edited in vendor consoles, with no diff, no review, and no rewind. TAS lets agents inherit the discipline you already use for production code — version control, code review, audit logs, identity, and RBAC.

And they don’t just sit in a repo — they run: on demand, on a schedule, or from an event, acting through per-user Connections to the services your team already uses. When a run needs a human in the loop, it surfaces the work in the Tasks Inbox — where you review, edit, and approve the action (reply, complete, archive…) instead of the agent acting blindly. The corrections you make there feed back into the agent as reviewable Improvements. The whole loop — from definition to action to adaptation — stays governed.

Principles

Section titled “Principles”
  • Git is the system of record. Agent definitions live in your repo.
  • Every change is a commit. Human or AI author — the artifact is always a reviewable diff in your repo (a pull request by default; a direct commit in YOLO mode).
  • Adaptation is allowed; drift is governed. Agents may evolve; they may not evolve in ways you can’t explain.

Who builds and maintains your agents

Section titled “Who builds and maintains your agents”

You don’t have to be an engineer to create or evolve an agent. Authoring and changes are handled by Tembo, an AI software engineering platform: describe what you want in plain language — a new agent, a tweak, or “this run was wrong” — and Tembo turns it into a pull request by default, or a direct commit when YOLO mode is enabled. It serves everyone on the team, from operators to PMs to the people who use the agents, not just developers — and it’s backed by real human engineers at Tembo who step in when a change needs them.

What’s in this manual

Section titled “What’s in this manual”

Setting up or operating the instance? See the admin introduction.

See the Changelog for what’s shipped, by release, and the Roadmap for where it’s headed.