Agents
Teams and members
A team is a group of members - and not every member is an AI. Browsers, notes and terminals take a seat too.
A team is a group of members
Press + on a team and the first question is what the member IS - not which AI drives it. An AI member is one option. So is a browser, a notes surface, or a plain terminal.
Every member gets its own row in the team, its own name and photo, and its own view. A browser member holding your API docs sits next to the agent that reads them, because both are part of how the team works.
- AI member - its own working folder, memory, and AI runtime
- Browser - a page that stays open in the team
- Notes - a Markdown writing surface over the team folder
- Terminal - a plain shell, no AI attached
What each kind costs you
Only AI members set up a repository and a memory scaffold, so only they take a moment to appear. A browser, notes or terminal member is created instantly: it points at the team folder and opens straight away.
Removing a member never deletes a folder it merely worked in. Only a working copy ReplicaMD created for that member alone is cleaned up - your team folder stays exactly where it is.
Non-AI members need the team to have a working folder. Set one on the team first if the options are greyed out.
Start a member from a preset
When you add an AI member you can start it from a preset published on the website. A preset carries the runtime, the role, a system prompt, and the plugins that member should have - and applying one installs those plugins before the member is created.
You can go the other way too: right-click any AI member and choose Save as preset to publish how it is set up, so the next one starts there.