Sign in to cloud first
Start in https://my.looky.studio and complete OTP login before touching CLI. This confirms your role and account access independently from local machine state.
- Open
https://my.looky.studio. - Authenticate with email OTP.
- Confirm shell loads without access errors.
Link CLI to the same instance and local root
The CLI stores authentication and billing context per linked root. Pick one stable root folder and keep using it.
looky login https://my.looky.studio <local_root>
looky whoami
If your CLI asks for email during login, provide the same identity you used in UI.
Activate billing context from root
cd <local_root>
looky billing list
looky billing use <billing_account_id>
Set-Location <local_root>
looky billing list
looky billing use <billing_account_id>
Run billing commands from the linked root itself. Billing context is root-scoped and must be set before workspace operations.
Verify CLI link before moving on
looky whoamireturns your email and the instance URL.looky billing listshows at least one billing account.looky billing use <billing_account_id>succeeds from<local_root>.
Workspace-scoped checks (looky status, looky validate) belong in the next step once a workspace exists — see Create Your First Workspace. If a colleague already shared a workspace with you, looky workspaces from the linked root lists the ones you can access; you can cd into any of them and run workspace commands from there.
Cloud and local runtime parity
Cloud (my.looky.studio) is your shared target. Local runtime (http://localhost:8000) is optional for quick iteration and debugging. Use both for verification when needed.
If cloud and local differ, start with looky status and looky diff in the workspace root. Most mismatches are context or sync issues, not chart bugs.