Troubleshooting

You are not logged in

Run /login. If the saved session expired or the API rejects it, use /login --force. Verify the result with /whoami.

If the browser does not open, use /login --no-browser and open the printed URL manually. If the local callback server cannot start, finish or stop another login flow using the same callback port and retry.

The CLI cannot reach Elyxis

The beta CLI is preconfigured to connect to Elyxis. Check your internet connection and retry. If the problem continues, contact the beta team with your CLI version and the error message. A connection problem is not evidence that a capability failed.

The Assistant keeps asking for context

Run /context and compare the selected environment with the one required by your task. Ask the Assistant to list eligible resources and select an exact result.

If each answer was sent as a new unrelated request, restate the original outcome together with the missing information in one request.

A requirement is missing

Read the reported configuration requirement literally. Common categories include an environment setting value, environment binding, catalog, endpoint, model, credential reference, build, or activation.

Do not invent values or paste secrets. Ask which Elyxis configuration resource can supply the requirement.

The confirmation is wrong

Reject it. State the correction and wait for a new confirmation. Never approve a destructive or production-targeted action merely to keep the conversation moving.

Approval did not produce a result

Approval and execution are separate. Read the response after approval for an error, expired confirmation, missing permission, validation failure, or downstream execution failure. Retry only when the failure is safe and transient or after correcting the reported cause.

The result looks unrelated or stale

Use /history and /context to inspect what the CLI retained. Start /new for unrelated work. Restate the complete outcome, target resource, and constraints when a short pronoun-based follow-up is ambiguous.

The Assistant reports an error

Follow the safe user-facing recovery message. Internal causes are intentionally not exposed. Record:

• the time of the request;
• the safe summary and error wording;
• the resource names or non-secret identifiers involved;
• whether confirmation occurred; and
• the last action that visibly completed.

Do not include tokens, passwords, private keys, or raw secret configuration in a support report.