Desktop and mobile

Use the browser to collaborate on repositories. Desktop adds local workspaces and agent sessions. Mobile client work is being qualified separately. A feature in source or a private test package is not evidence of a supported public release.

Choose an offered desktop build

Start at the Download page and select a build offered for your operating system and architecture. Read its release notes and channel information before installing. If no download is offered, use the browser or ask your preview coordinator whether you have access to an approved preview package.

Unsigned evaluation installers, private previews, and a published stable channel have different release guarantees. Do not disable operating-system protection just because a package exists in an issue or a build artifact.

Connect your account and repository

Open the client and follow its sign-in flow for the intended deployment. Confirm the host and account before approving access. Select an authorized repository or an existing local checkout in the workspace controls offered by your build.

A local checkout and a remote repository view are different working contexts. Confirm which one you are editing and review the branch and diff before pushing. Keep work that belongs to different tasks on separate branches or worktrees according to your repository's contribution rules.

Use an agent session

Select the provider, workspace, and permissions available in your build. Read an approval request before granting file writes, commands, or access to a remote device. Review the resulting diff and run the repository's checks before publishing changes.

Provider availability and data handling depend on your deployment and configuration. Do not assume an agent session can use an unconfigured provider or that private repository access implies permission to send its contents to every provider.

Mobile availability

There is no general public mobile installation procedure in this guide. Use only the package and enrollment instructions supplied for an explicitly offered mobile test channel. The mobile source does not establish store release readiness, physical-device performance, or reliable reconnection.

If a client fails to connect, record the client version, operating system, host, and visible error without including credentials. Continue in the browser when appropriate and follow Troubleshooting.