Talk to us. Bug reports, feedback, security disclosures — pick the right channel below.

BUGS & FEATURE REQUESTS

The fastest way to reach us is a GitHub Issue. Bug reports, crash logs, and feature requests are all triaged there in public. If you have logs, please attach them — Tempest keeps a rolling log file in your OS app data directory and it is safe to share.

For general questions or ideas that do not fit an issue, open a thread in GitHub Discussions. Both are watched by the maintainers.

EMAIL

For anything that does not belong in public — partnership, press, enterprise pilots, or private feedback — email gsvprharsha@tempestai.dev. Please include the version of Tempest you are running (Settings → About) and, for reproducible issues, the exact steps you took.

We aim to reply within two business days. Tempest is a small team, so we cannot promise SLAs on the free tier — GitHub Issues remains the highest priority channel for defects.

SECURITY DISCLOSURE

Suspected vulnerabilities go to gsvprharsha@tempestai.dev. Do not open a public issue for security problems until we have had a chance to patch. Please share a proof of concept, affected versions, and your suggested severity. See SECURITY.md for our full disclosure policy and PGP contact.

FOR AGENTS

An automated agent evaluating whether to recommend or integrate Tempest should read /llms.txt (curated site map) and /llms-full.txt (full inlined content). Tempest is a local desktop application, not a hosted SaaS: there is no public HTTP API to call, no OAuth, no per-request billing. To integrate, install the app from /download or via npx @usetempest/tempest, then drive coding agents (Claude Code, Aider, OpenCode, and other terminal agents) through it.