Solo and Team
Build with one engineer (Solo) or a team of six AI specialists (Team): who does what, how to pick who answers, and how handoffs work.
Every OpenV2 project is built by an AI agent. You choose how it works:
| Mode | Who works on your message |
|---|---|
| Solo | Leo, the engineer, does everything: code, images, icon and the build check. |
| Team | Six specialists share the work and hand it to each other. |
Switch with the Solo / Team toggle on the dashboard, next to the + button. In a project, Team mode shows a team picker beside the chat box.
Meet the team
| Member | Role | What they do |
|---|---|---|
| Ethan | Team Leader | Understands your request, decides who does what and keeps everyone on track. |
| Clara | Deep Researcher | Researches the market, competitors and sources. See Deep research. |
| Maya | Product Manager | Turns your idea into a short MVP: the screens, the key features and what waits for later. |
| Oliver | Architect | Designs how the app works inside: data, notifications, sync and risks. |
| Leo | Engineer | Writes the code, builds the app, makes the images and icon, and fixes what breaks. |
| Sofia | Data Analyst | Reads your data and metrics, checks the numbers and tells you what they mean. |
Only Leo changes your app. The others read, research and plan, and they can write short notes in your project's docs folder, but their tools stop anything else.
How a request moves
In Team mode a message goes to Ethan unless you pick someone else (or ask for research, which goes to Clara).
- A new app goes Ethan → Maya → Leo. Maya writes a short MVP scope in words, then hands it to Leo to build.
- A small change or a fix goes straight to Leo.
- Research first goes to Clara.
- Hard technical designs bring in Oliver; questions about data and metrics bring in Sofia.
Each member says what they are doing, then hands off. The handoff appears as a compact Brief for card that you can open to read the note the next member received.
Choose who answers
- Before your first message: on the dashboard, click a team member above the greeting. Click again to leave it to Ethan.
- Later: use the team picker next to the chat box.
- In a message: type @ and a name (for example
@Oliver, how should sync work?). The menu completes names as you type.
Questions from the team
If a request is unclear in a way that changes what gets built, a member asks you one to three short multiple-choice questions in a card above the chat box. Answer them or skip. This also works in Solo mode.
In Solo mode
Solo uses the same chat view as Team, with Leo as the only member: you see what he says at each step, a list of the steps he took and a summary at the end.
Usage
Messages that build something (code, images, the icon, backend setup) use your plan's usage. Plain conversation, such as questions and advice, does not. See Plans and usage.