Let teammates start sessions in your repository

Grant server users or groups the right to start sessions in a repository, Project group or repository set, separately from session sharing. Each user works in a private copy, and every session gets its own clone and branch. Revoking access blocks new work at once.

Different users still run in separate containers. Shared-repository clone and push have not been proven live yet.

How it works

  1. Grant repository use

    Choose the users or groups and the repositories, Project groups or repository sets they may use. This right is separate from viewing or controlling one of your sessions.

  2. Keep Git access explicit

    For each repository, use your Git access through a broker that never exposes the token and pushes only the session branch, or let each user connect their own Git account.

  3. Limit and revoke

    Share the Project configuration or keep it per user, and set a per-user session limit. Revoking access blocks new sessions immediately and can also stop running ones.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.