Support

Start with reproducible evidence.

Use GitHub Issues for reproducible bugs and feature requests. Include your CodeCaddie version, operating system, selected provider, expected behavior, exact visible error, and whether each context file was Ready, Stale, Unsupported, or Unreadable.

The provider activity panel is designed for safe progress reporting, but review screenshots before sharing them. Never attach repository source, extracted document text, provider credentials, recovery exports, absolute private paths, or customer data. Security issues belong in private vulnerability reporting.

Try these first

Which file should I download?

Use the macOS download for the signed and notarized universal app. GitHub source archives require a local build. The Windows installer is not available yet.

The provider is unavailable or needs authorization

Run your selected provider CLI in a terminal and complete its own authorization flow, then retry in CodeCaddie. Never paste provider credentials into an issue.

The report does not reflect my latest edits

Analysis covers a committed snapshot. Commit the intended changes and run another analysis; check the report’s commit identity.

Goal generation or analysis failed

Read the visible error, confirm the provider works independently, and retry. Approved goals remain intact. Include sanitized reproduction steps if the failure persists.

A context document is stale or unreadable

Reattach changed files. Use a supported, text-bearing document within the documented limits; image-only documents require a text version.

Community support is best effort and has no guaranteed response time.