LoopBack started as a solo tool. You annotate your own build, export a prompt, hand it to your AI agent. But almost immediately after launch, teams started asking how to share feedback sessions across multiple reviewers. A designer annotating the same build as a developer, a QA engineer and a product manager reviewing the same staging environment. The Team plan is our answer to that.
The foundation of team collaboration in LoopBack is the project. A project is a named collection of feedback sessions tied to a specific app or URL pattern. When you create a project and share it with teammates, everyone who has access sees the same queue of annotations. Comments added by your designer appear in your drawer alongside your own. The combined list is what you export as a prompt, so your AI agent gets the full picture from everyone who reviewed the build.
Team sync is opt-in and designed to be transparent about what leaves your machine. By default, LoopBack stores everything locally. When you enable team sync for a project, annotations are encrypted and sent to LoopBack's relay service, which distributes them to other members of your team. Screenshots are not synced by default because they can be large and may contain sensitive information from your development environment. You can enable screenshot sync per-project if your team's workflow requires it.
Managing your team happens in the LoopBack web dashboard. You invite members by email. Each invitation is tied to a seat in your plan. The Team plan includes five seats. You can see which seats are active, revoke access for members who have left the team, and transfer a seat to a new member without losing the project history attached to that seat.
Roles in LoopBack are intentionally simple. Every team member can add annotations, export prompts, and mark items resolved. The team owner can manage seats and configure sync settings. We did not build a complex permissions model because the teams using LoopBack tend to be small and trust each other. If your team grows to the point where you need role-based access control, get in touch and we will talk through what we can do.
The retest workflow works the same in a team context. When an annotation is resolved by the developer, the status updates for everyone on the team. The progress bar in the LoopBack drawer reflects the combined state of all annotations across all reviewers. When everything is marked resolved, the session is archived and you can start the next review cycle. It is a simple loop, but across a team it replaces a lot of async coordination that previously happened in chat threads and project management boards.