Get in touch.

Krate is built in the open, so everything below is public and gets a reply in public. Not sure which fits? The first one is always fine.

Ask a question, or say what is confusing

GitHub Discussions. Anything that is not obviously a bug: how to do something, why a thing works the way it does, or that a page made no sense. →

Something crashed, an app would not open, a command failed. Paste what you ran and what it printed -- that alone is usually enough to find it. →

A capability Krate does not have, an app you tried to make and could not, or a rough edge worth smoothing. →

Reporting an app in the gallery is different: every listing has a report link that opens an issue naming that app, so it does not get lost.

Before reporting a bug, krate doctor checks your setup and prints what it finds. Including that output saves a round trip.

Security problems go to a private advisory on the repository's security tab, not a public issue.

Signed-in support gets answered in a thread that follows you between the website and Studio.