Support OmniView

Use GitHub Issues for reproducible installation, discovery, grounding, prompt, rendering, package, drop-in, documentation, and accessibility defects.

Before opening an issue:

  1. remove credentials, private coordinates, personal data, unpublished research, account identifiers, and provider receipts that should not be public;
  2. record the OmniView version, source commit when known, host and host version, and artifact used;
  3. distinguish placement, installation, discovery, invocation, prompt-only operation, dispatch, returned image, and healthy behavior;
  4. include the exact request, expected result, observed result, render state, and complete error;
  5. state whether retrying could spend money or duplicate an external action.

For a GL4SS patch problem, include the upstream commit, patch hashes, git apply check result, and whether either patch changed the checkout. Do not publish an uncertain partial candidate.

Security-sensitive reports follow Security policy. This project is maintained on a best-effort basis; no response-time or service-level commitment is implied.

Continue with Troubleshooting, Lifecycle, or Contributing.