CLI troubleshooting
Fix Pollaris CLI authorization, continuation, workspace, credential, and MCP connection problems.
The command returns requires_authorization
This is expected on first use or after a grant expires. Open authorization.url, finish sign-in and consent, then run next_action.command. Keep the same operation ID.
Authorization finishes but the agent does not continue
Pollaris cannot wake an agent host that terminated its process. Run the returned continuation command:
pollaris operations resume OPERATION_ID --wait --timeout 45 --jsonThe original prompt and idempotency key are preserved locally. Do not start a second create command.
The authorization link expired
Resume the operation. Pollaris creates a new authorization link while preserving the request:
pollaris operations resume OPERATION_ID --jsonNo supported credential store
Use the operating-system keychain, or set POLLARIS_CLI_SECRET_KEY from a secret manager on a headless system. The value must be a Fernet key. The CLI deliberately avoids a plain-text fallback.
The wrong workspace appears
One profile is bound to one Pollaris grant and workspace. Use pollaris workspaces list --json to inspect it. Create a separate --profile and authorize the intended workspace.
A create command remains pending
Check the saved operation or backend job:
pollaris operations resume OPERATION_ID --json
pollaris jobs get JOB_ID --jsonA wait timeout does not cancel the job. A failed result includes a safe error code. Generation can fail when the request is not appropriate for a form or cannot produce a valid form within the repair limit.
An idempotency conflict occurs
The same key was used with different input. Restore the original input when retrying that operation, or use a new key for a genuinely new form.
MCP host configuration was not changed
Without --config-file, pollaris mcp connect returns a configuration object for review and reports installed: false. Add it with the host's supported setup method, or rerun with an absolute JSON configuration path containing mcpServers.
The MCP bridge fails to start
Install the CLI with its MCP dependency:
uv tool install "pollaris-cli[mcp]"Then check the named connection:
pollaris mcp status --profile CONNECTION_NAME --jsonReload the host after a successful connection. Diagnostics belong on stderr; any non-protocol output on stdout can break stdio MCP.
The server says agent access is disabled
The Pollaris deployment has not enabled its CLI/OAuth/worker feature. Use the existing MCP API-key workflow or contact the deployment administrator. Enabling the API without its database migration and agent worker is incomplete.