Skip to main content
Bug reports are tracked as GitHub issues. A clear, reproducible report gets a fix faster than a vague one.

​
Before you report

1

Update Tempest

Make sure you are on the latest version. The bug may already be fixed.
2

Search existing issues

Search GitHub Issues for your error message or a description of the behavior. Add a comment to an existing issue rather than opening a duplicate.
3

Reproduce it

Try to reproduce the bug in a clean workspace. If you cannot reproduce it consistently, include that in your report.

​
What to include

Environment

OS version, Tempest version, Node.js version, and Rust version. Run npm run tauri info in the repo for a complete summary.

Steps to reproduce

The exact sequence of actions that triggers the bug. Number each step. Start from a fresh app launch.

Expected behavior

What you expected to happen.

Actual behavior

What actually happened. Include error messages, stack traces, or screenshots.

​
Logs

Tempest logs are written to the Tauri log directory for your platform:
PlatformLog path
Windows%APPDATA%\tempest\logs\
macOS~/Library/Logs/tempest/
Linux~/.local/share/tempest/logs/
Attach the latest log file to your issue when reporting crashes or silent failures.

​
Severity labels

Maintainers apply one of the following labels after triage:
LabelMeaning
bugConfirmed unexpected behavior
criticalData loss, crash on launch, or security issue
needs-infoCannot reproduce without more details from the reporter
wont-fixKnown limitation or out of scope

​
Security vulnerabilities

Do not open a public GitHub issue for security vulnerabilities. Email tempestai.dev@gmail.com directly with a description of the issue, steps to reproduce, and any relevant logs or proof-of-concept code.