Repository navigation
Troubleshooting
This normally means the selected endpoint or shared upstream pool is temporarily rate-limited. Wait and retry, configure BYOK if the provider supports it, or select another compatible route/model. It is not a database error.
The provider used its available output budget before producing a complete answer. Eligible post-Reveal analytical work has one controlled recovery attempt. Field Guide/Viewer Notes capacity retry is a separate mechanism.
Some models may consume unusually large outputs while processing the Field Lexicon. The application does not silently change the user's reasoning setting. If both controlled attempts fail, use a model that completes the workflow reliably.
Messages such as Windows error 10054 or “error reading a body from connection” mean the remote endpoint closed the stream. The application applies only its bounded transport recovery rules because the provider may already have generated or billed part of the response.
Provider continuation state is validated before it is stored or replayed. Current OpenRouter streaming canonicalization merges compatible text/summary fragments before the logical block limit is applied. Opaque encrypted/signature blocks remain unchanged.
v0.7.13 uses schema 27 and a controlled data-compatibility epoch. Unverified older or inconsistent databases are classified before migrations are loaded. Use the compatibility screen to preserve data and start fresh, or use the matching older application version.
Verify that the AppImage checksum and attestation match the public release, then grant execute permission with chmod +x. For DEB, use the distribution package manager so missing system dependencies are reported. The public v0.7.13 AppImage and DEB were built from the accepted main commit and passed practical launch testing, but distribution-specific runtime dependencies may still differ.
Human labels do not require a provider or API credential. Provider status belongs to the AI identity. v0.7.13 presents these roles separately.
Use GitHub Releases as the authoritative source. Do not treat a locally built or branch-only package as the published release unless its checksums and commit match the release entry.