By default a coding agent reports to your personal workspace. Pin it to a team project when the work belongs to the team: an application project the whole team debugs, a shared machine, or an initiative whose agent spend you want accounted together.
This mints an ingest key for this device, scoped to the project, and pins the tool to the project. LangWatch creates one key per device and never replaces another device’s key, so any number of machines can report to one project at the same time. You need a login and the traces:create permission on the project.
A member on a Developer seat holds no permission on any shared project, so the pin is refused and the device keeps its current connection. Ask an administrator to move you to a Member seat and add you to the team that owns the project.
The wrapper takes the same flag and then starts the agent:
--project and --personal are LangWatch flags. LangWatch removes them from the command line before the agent reads it. The pin is per device and per tool: your laptop’s Codex can stay personal while its Claude Code reports to the team.
What the project gets
Once the project records coding-agent activity, Sessions and Pull requests appear in its sidebar, the same views as on your personal page, project-scoped. Session traces land with the project’s traces, costs land in the project’s analytics, and the pull request rollup attributes the project as a contributor.
Who sees what inside the project follows the project’s access rules and permissions, exactly as on any project. See Privacy.
Back to personal
This removes the project pin on this device and writes the personal connection again.
Also check: Headless machines and CI for machines that never log in, and Access Control (RBAC) for what traces:create covers. Last modified on October 6, 2026
