Tracely

Trace a bug to the code and user flow behind it, using your own model: local Ollama or your own API key.

Tracely is a side panel for engineers who get bug reports. Describe what went wrong, paste an error, or open the GitHub, Jira, or Sentry issue, and Tracely follows the flow through your repository to the likely cause. • Findings, not guesses. Every finding names the user flow it breaks, cites the exact lines it came from, and says how to verify it. Confidence stays at medium until a test confirms it. • Plain-language reports work too. "Checkout is slow sometimes" is translated into the code terms and files behind it, then followed along the call flow. • A code map without a model. Routes, call paths, and linked tests for Python, Java, Go, JavaScript and more. • Find risks. Scan your branch's changes, one folder, or the whole repository with built-in rules and your own Semgrep rules, and optionally a model review. • Verify. Run the related test (after you confirm) or draft a new one. • Share. Export a run as Markdown or JSON, copy a finding for Jira, open a prefilled GitHub or GitLab issue, or create a Jira issue in one click. • Your model. Use Ollama on your machine, or your own Anthropic, OpenAI, Google and more. Local-only mode keeps all code on this machine. • Private by design. There's no Tracely server and no telemetry. Keys and tokens are encrypted in your browser. Code goes to a remote provider only after you confirm, once per repository. Tracely needs its small companion service, which reads your repository locally. Install it from the link in the panel.