Jasper guides
Shared AI coding workspaces for teams
Jasper Team gives developers shared project workspaces for AI coding terminals. A board brings a project’s terminals and web pages together, while project access controls determine which members can use it.
Shared board terminals run inside the board’s server container. Each terminal has its own session, and terminals on the same board work with the same project checkout.
One project board, one container workspace
A board’s container holds its code checkout, development tools and persistent home storage. Opening another terminal on that board creates a separate terminal session in that same environment.
Separate boards use separate container workspaces. Within one board, files are shared: if one terminal edits a file, another terminal on the board sees that change. Closing a terminal does not delete its siblings or the board’s project volume.
This arrangement lets a team work in a consistent environment while keeping the host’s filesystem separate from the container workspace.
Code synchronization uses Git
The board starts from a Git checkout of the selected project. Uncommitted files from the source checkout are not the source of that initial clone. Commit the source changes you want to bring into the board.
Board work uses a dedicated Git branch. Pulling updates is an explicit action, and dirty or divergent checkouts need attention before a fast-forward can proceed. Publishing board commits uses the repository credentials configured inside that workspace.
Git sync is not continuous file mirroring. A local edit does not appear in the board until you commit and synchronize it. Likewise, keep track of the board’s commits when you want to bring remote work back to another checkout.
Coordinate agents that share files
Use separate terminals for independent work such as investigating different modules, reviewing a change or running checks. Agree on file ownership before multiple agents edit the same project.
A separate terminal session provides a separate agent context; it does not provide a separate filesystem. Use separate Git worktrees when a job needs its own working copy, then review and integrate the resulting changes.
For example, one member can ask an agent to trace a backend error while another reviews the related UI behavior. A shared board keeps both terminals available alongside the project’s web pages.
Manage access per project
Team administrators can invite members, assign roles, grant access to selected projects and revoke access. Jasper also provides audit logs, organization security policies and OIDC single sign-on.
OIDC and SAML are different protocols: OIDC is supported, while SAML is not currently supported. Review the Team feature list and discuss requirements before choosing a deployment.
Workspace access and AI model access are separate. Members still need the provider accounts or credentials required by the AI tools running in that environment.
Set up your team’s workspace
Start with the desktop setup guide, then connect the server used by your team. The remote terminal guide explains SSH sessions and managed machines.
Existing customer? Open your account or contact Jasper support.