On this page
Setup and message-delivery problems
First identify the phase. An application launch failure, an uncertain Birth result and an unconfirmed chat message are not interchangeable. Repeating an action can create another request and another charge without resolving the original uncertainty.
Preserve information before retrying
Keep the relevant text and exact error in a trusted private place before dismissing a card, navigating away or restarting. Temporary session text is not a backup. For support, share only the necessary sanitized error, app version/build if known, operating system, time and action attempted. Remove credentials, personal conversation, private paths and account identifiers; do not upload an entire log, database, key or identity record.
No generic deletion or reset command is supplied here. In particular, do not remove identity files to make a setup screen reappear.
Match the symptom to the phase
| Phase / symptom | Conservative response | What not to infer |
|---|---|---|
| Application launch fails or the dashboard does not open | Keep the launcher error and identify whether an existing identity was expected. Use support appropriate to your installation; a platform-specific launch repair is not yet tested here. | Do not assume the identity is absent or solve a port error by stopping an unrelated process. |
| Before Birth: local model discovery fails or no model is listed | Check that the intended server is running at the intended address and offers a compatible model. Verify provider authorization privately. In the inspected UI, local Birth waits for that address to list models. | Discovery is not a completed founding conversation. Do not substitute an arbitrary endpoint or bypass verification. |
| Before Birth: signed founding material is unverified or unavailable | Keep the exact verification/service error and seek help resolving it. | Do not bypass signed-material checks. A local model does not remove the platform-service dependency. |
| Birth loses its connection before confirmation | Pause. After connection returns, establish identity state through the supported UI/support route before any repeat request. If state cannot be established, stop and ask for help. | “No confirmation” does not mean “no identity.” This draft does not yet give a tested state-reconciliation procedure. |
| Birth reports that an identity already exists, was created but startup failed, or greeted but recording failed | Preserve the error and treat the state as existing or partial. Seek a specific recovery for that state; any restart must follow the product's state-specific guidance. | Do not click Birth again or manually delete partial artifacts. A late error is not evidence that the founding request had no effect. |
| Birth reports a provider rejection, empty answer or output-limit failure | Review the exact error and provider/model requirements before deciding on another authorized request. Establish that identity creation did not occur if the phase is uncertain. | A failed attempt can still have contacted the provider or incurred charges. No blanket retry is safe. |
| Ordinary chat: pending, refused, connection lost or contradictory confirmations | Preserve the text, status and any receipt details privately. Reconcile the intended identity's recorded history and any explicitly transient view before considering a resend. If the result stays uncertain, seek help instead of retrying automatically. | Pending is not saved; missing confirmation is not absence of effect. Dismiss is not cancellation. Exact navigation remains untested. |
| Ordinary chat: recording failure or a reply marked temporary/not saved | Preserve needed text privately while available and investigate the recording error. | A visible reply is not durable history; restarting can lose temporary content. Do not resend merely to repair reply recording. |
The composer reference identifies the source-defined labels. What happens in a conversation? explains the checkpoints behind them.
Limits of this page
This is safety-oriented triage, not an executed repair recipe. It does not prove a backup can restore your state, that cancellation stops every effect, or that a restart resolves a partial birth. Verified launch, history inspection, cancellation and restore procedures still need separate replay on the current release. Faults must not be induced in a personal identity just to test this page.