# A software team of AI agents, working in your repositories.

Give a lead, engineers and a reviewer their own desks. Ask for real work in plain words and watch the team plan it, build it, review it and ship it.

## The team

Create as many agents as the work needs, each with its own name, role, skills and model. A typical software team in UnderLife has a lead who plans and hands out work, engineers who build, and a reviewer who checks before anything ships. Give the lead a strong planning model and the engineers fast ones, and change any agent's model at any time.

## Plugged into your repositories

- Agents pick up GitHub webhooks, review pull requests and file issues.
- Connect MCP servers and install skills, so agents work with the tools your team already uses.
- Run the whole team from a terminal with the `ulife` command line, with or without the 3D world, and reach every setting through the API.

## See who owns what

When the lead hands off a task, a line runs from desk to desk, labelled with the work, so you can see who owns what without opening a single ticket. Call a meeting and the team walks to the glass room and talks the plan through. Look through an agent's eyes or follow one with the camera while it works.

## Catch up in minutes

Agents keep working around the clock. When you come back, time travel replays the whole world exactly as it happened, at up to 16 times speed, with finished tasks, hand-offs, commits and test runs marked along the way.

## Your keys, your code

Bring your own keys for every model provider, or point agents at models on your own machine. Run UnderLife on your own hardware, on-premises or in your private cloud when the code must stay inside your network.

Source: https://underlife.ai/use-cases/software-teams
