Contact

SAY
SOMETHING.

ONE MAINTAINER · ONE ADDRESS · NO TICKET QUEUE

Codescry is built and maintained by one person. Bugs, feature ideas and questions all go to one address — support@codescry.app — and are read by the person who wrote the app. There is no ticket system and nobody to escalate past.

Security issues go to the same address, tagged [SECURITY]. Please report a vulnerability privately before discussing it anywhere public.

(01)

PICK A CHANNEL

01 / GENERAL Email the maintainer

Bugs, feature ideas, questions. One address, read by the person who wrote the app.

support@codescry.app → 03 / SECURITY Report a vulnerability

Email first, privately. Please don't file a public issue for a vulnerability before it's fixed.

support@codescry.app →
(02)

DRAFT IT HERE

This form doesn't submit anywhere — there is no server behind codescry.app to submit to. It composes your message and hands it to GitHub or your mail client, so you see exactly what gets sent before it is sent.

✉ SEND AS EMAIL

▸ Nothing is transmitted from this page. The button opens a prefilled draft in your own mail client — you still press send there.

(03)

WHAT TO INCLUDE

Codescry runs entirely on your machine, so nothing is visible from here. A report is only as good as what you paste into it.

  • Version and platform. The app version from Settings → About, your OS and its version.
  • Model and engine. Which local model was selected, and the Ollama version behind it.
  • What you expected, and what happened. Plus the steps that reproduce it.
  • The run log, if a scan was involved — the log pane copies out as plain text.
  • Scrub it first. Absolute paths, project names, findings text and screenshots can carry things you don't want public. Redact before you paste.

A screenshot of the UI is welcome for anything visual — but check the window for project names and paths before attaching it.

(04)

WHAT TO EXPECT

  • No SLA. This is a free, MIT-licensed side project, answered when there's time — not a support contract.
  • No ticket system. No account, no case number, no chatbot in the corner.
  • No mailing list. Writing in doesn't subscribe you to anything; there is nothing to subscribe to.
  • One address. Bugs, ideas and questions all go to the same inbox — there is no public tracker to search first.

▸ How your data is handled — including anything you choose to send — is described in the privacy policy.