Why am I signed into OfficeCubs but tasks need login?

OfficeCubs accounts and AI-provider authentication serve different purposes. Marketplace sign-in gives catalog and account access; the selected CLI still needs its own usable credentials.

Before you begin

A work engine is the CLI process that performs the task. OfficeCubs supplies the task context and records its progress, while authentication, model availability and usage charges come from your chosen provider. Successful detection is a setup check, not proof that every model or task will work.

Steps

1. Read the failing task’s authentication error.
2. Open the selected tool in a terminal and complete its supported sign-in.
3. Return to OfficeCubs and check installation.

Example

A role can be recruited successfully while its first model request fails because the CLI session has expired.

Check the result

Run a small new task after reauthorization and inspect its execution events.

Limits and troubleshooting

Never put a password, token or recovery code into a task brief to resolve login. Use the provider’s authentication mechanism.