gonuAccount & session access
Use one Gonu account across supported surfaces and keep workspace access separate from device sign-in.
WHEN IT HELPS
Put it to work.
Connect a new local client, recover an expired session or understand why a resource is not visible.
Before you begin
- Your existing Gonu sign-in method.
- Access to the email/account used for Gonu.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Sign in on the website. For Worker/CLI/VS Code device login, compare the displayed code before approving the request.
Select the intended personal or business workspace in the relevant tool. A valid login alone does not grant every project’s access.
Open account settings for available profile/session controls. When a session expires, sign in again through the supported flow.
Account / Sign-in checklist
THE USEFUL RESULT
What you should leave with.
A consistent identity with the right workspace and client access.
Know the boundaries.
- A workspace owner is not automatically a platform administrator.
- No separate account or personal provider key is required just to use a Gonu-hosted model.
IF SOMETHING DOESN’T WORK
A local client shows different tasks.
Verify the account, API environment and workspace. Development and production are separate environments even when the UI looks similar.
Contact support