EMPLOYEE CLOUD WORKSPACE
Connect once. Work from the cloud.
Sign in to Claude and Codex in your assigned company workspace. The clients and their working repositories remain there when your laptop is offline.
What Confer receives
Quota percentages, reset times, account fingerprints and connection status. You may also share response token counts. Prompts, code and file paths are excluded from usage reports. Your provider credentials stay with the official clients in your cloud workspace.
Your administrator verifies the company account before its limits appear on the team dashboard. Connecting usage does not start assignments. Buzz and repository access are activated separately.
This is the first cloud enrollment pilot. A successful sign-in remains saved even if you close this page. Keep this tab available while completing both providers; if you lose the browser connection, contact your administrator for recovery.
1. Connect your invitation
If you lost this browser’s connection, use the recovery invitation from your administrator. It restores access to the existing cloud workspace; it does not replace its provider sign-ins or usage history. If the page reports a connection problem after submitting it, retry here before clearing this browser’s data: the same browser secret makes that recovery safe to retry.
2. Sign in to your company accounts
Open each provider’s link and sign in with the company account assigned to you. Sign-in links expire in ten minutes. A provider may occasionally require you to sign in again.
Forgetting clears this browser’s reporting connection, and cancels unfinished sign-ins. Ask your administrator to revoke reporting or disable the cloud worker.
Working repositories
GitHub remains the shared source of truth. Each assignment uses a cloud working copy and its own branch. Push laptop changes to GitHub before handing them to a cloud agent.