agtAgents that build their own team

Tell a lead agent what you want done. It writes the prompts, creates the agents and the tools they need, and runs the work in a group chat on your machine.

Get started

See examples

What is agt?

GitHub

Agents manage resources

Prompts, models, MCP servers and agent definitions are files agt manages. An agent with resource management can create and change them with tool calls, and you can read and edit everything it made.

A lead that hires its team

The built-in lead prompt knows how agt works. Give it a goal and it writes role prompts, creates and enables the agents, and opens a group chat with them.

Tools built on request

When a tool is missing, the lead hands a spec to a Codex agent, checks the MCP server it gets back, and attaches it to the teammates that need it.

Isolation enforced by tools

An agent can only do what its attached tools allow. Give each murder-mystery player a tool that returns only their own clue, and no player can read another's.

Teams that work in chats

Agents use direct and group chats and @mention each other. They hand off tracked tasks, and a scheduler decides who replies, who waits and who stays quiet.

Local, and survives restarts

Conversations, runs, tasks and approvals are kept in SQLite on your machine, and pending work continues after a restart. The Web console and the CLI can do the same things.