Tama / Private release

When something goes wrong - Tama

Check the state before trying the work again.

I cannot sign in

Use the workspace token provided by your Tama operator, not your provider API key. Google sign-in appears only after your operator configures the authorized Google account. Public Google signup and email-password reset are not available. Ask your operator if you need access.

Knock or Send is unavailable

Check API keys & connections in Settings. Your key, model and execution service must be ready. A successful connection check does not itself run the model or start the execution service; ask your operator if it remains disconnected.

The connection check failed

Check the API key, its project access, chosen model and provider service availability. The connection check does not run the model. Keep keys out of screenshots, chat messages and shared files.

The task is queued

Queued work waits until it can be claimed, including waiting for current agent work to finish. A queue entry is not evidence that a provider run has started.

Work was interrupted

Review the task, available events and artifacts. Work may have completed partly even if the connection was lost. Ambiguous outcomes need reconciliation; do not repeatedly submit the same job.

A key changed

Stop or reconcile active work before replacing a key. Existing sessions require explicit verification against the new connection. Queued work with obsolete credentials does not silently change its payer.

Knowledge changed while I was reviewing it

Your proposal may be stale if the target or its sources changed. Keep the draft and review the latest evidence before applying it. Resolve upstream pending reviews first when required.

The site looks out of date

Reload the current page. Existing workspace links continue to the workspace; the public homepage is a separate introduction. If a problem remains, report what you were doing to your operator without sharing credentials.

Updated September 24, 2026