Skip to content
Browse documentation

Agents

Manage your studio, team and scene

Create a team with AI or the native team, recover a previous studio, import a scene or return to team selection.

Start with the native team

A new project opens team selection with three choices: Create your team with AI (Build my studio), Create a base team (Create team) and Import a team (Import team, then Choose a team file, Choose a source project or, when available, Recover previous workspace). The native team contains ten editable agents. Orchestrator, Planner, Developer, Researcher and Reviewer are enabled initially. UI/UX Designer, Documentator, DevOps, Ticketer and Git Manager start disabled; enable them when their missions are useful for your project.

Once the team is created, from scratch, with AI or by import, Vopit opens the Getting started guide: ten short steps, each with a picture of the feature, from meeting your team and connecting a model to the Board, meetings, Cranks and Quick actions. Some steps have a button that takes you straight to the feature. Skip the guide closes it; open it again at any time with the question-mark button in the header, or Getting started guide in Quick actions (Ctrl+K).

Edit agents and Cranks inside Settings. Review missions, connections, models, capabilities and completion criteria before running work. Where supported, select reasoning effort for a connection or override it for an agent. A richer team does not replace clear goals and verification of the delivered result.

Create a team with AI

Create your team with AI proposes a team and Crank automations shaped around your activity, for software or for research, content, business and personal projects. Generation is configuration only: it runs no actions and changes no files until you create the studio.

  1. Choose Build my studio. Pick an AI connection with a selected model (a CLI connection can use its default model); Configure connections opens Settings if none is ready.
  2. Write Your brief, or start from an example activity. With Read this project to fit the team to it checked (the default), the brief is optional. Without it, describe your activity in at least 20 characters.
  3. Choose Generate my studio. Cancel generation stops it without creating a team.
  4. Review the preview: the studio name and summary, 2 to 8 teammates whose name and Mission & completion criteria you can edit under Review mission & access, the suggested automations, and A first request to try. Generate a new proposal replaces the preview.
  5. Each suggested Crank starts disabled and set to Ask before each execution. Complete any missing target, such as a repository or channel ID, or uncheck the suggestion to skip it. Private credentials are added later in Settings → Cranks.
  6. Choose Create this studio. The agents start enabled and use the connection chosen for generation, which also becomes the workspace default; infrastructure access is not granted. Existing furniture and rooms are kept, and the suggested Cranks replace any previous Cranks. Vopit keeps a backup of the previous configuration. Review the agents, then send the first request.

AI creation is offered in team selection, for a project without a team. To use it in a project that already has one, first choose Dissolve team in Settings → Studio.

What project reading sends

  • Vopit selects the files without a model call: up to 10 files that describe the project, such as the README, agent instructions like CLAUDE.md or AGENTS.md, manifests like package.json, and documentation near the root. Excerpts total at most 40,000 characters, plus counts of files by top-level folder and file type.
  • Secrets found in excerpts are masked. .env files, key files and the .vopit folder are never read; the project’s exclusions and protected paths apply. The folder’s full path is not sent.
  • If the project Read permission is set to Never, no folder is open, or the folder is empty, the team is based on your brief only, and the preview says so.
  • The preview shows Based on your project · N files read of M, with the list of files used and which ones were excerpts. The brief and these excerpts are sent to the selected connection.

Recover or import an existing studio

  1. Open Settings → Studio. Recovery remains available even if you skipped it during project setup.
  2. Choose Recover previous workspace when a previous workspace is available, Choose a source project to select another project, or Import team and scene file to load an exported studio.
  3. Review the replacement before confirming. A full export includes agents, Cranks, furniture with its notes, rooms, their saved placement and the connection configuration (connections and the default connection, without API keys). Included sections replace the current sections, including this project’s connections; absent sections in older files remain unchanged. Vopit keeps a backup of the current configuration before importing.
  4. Imported Cranks start disabled and set to Ask before each execution. Review the imported agents, restore API keys and reconfigure any required access before enabling them. Private credentials are not copied and infrastructure grants must be assigned again.

The destination keeps its project identity, request history and project permissions. Use Export team and scene in the same Studio category to save a reusable studio file. Review that file before sharing: instructions, configuration and scene content can still contain project information. Teams from the public library on Vopit.fr, including official studios, are imported with Import team and scene file; see Share and discover community teams.

Return to team selection

  1. Finish or stop active requests and Cranks first, including queued or paused work.
  2. In Settings → Studio, choose Dissolve team and read the confirmation. Cancel leaves the current team in place.
  3. Confirm to remove the current agents and their workstation positions, then return to team selection. Create the native team or import another studio.

All documentation