sherlock-trace 0.0.1

Post-mortem bug replay in your editor. Inferred variable values along the call path - no runtime required.

SherlockTrace

Post-mortem bug replay in your editor. Paste a stack trace - watch the execution path light up across files with inferred variable values at every frame. No runtime, no SDK, no recording.

Status

🚧 Early development - planning phase. Public release planned for Summer 2026.

The idea

Every developer has wasted time pasting kubectl logs and stack traces into ChatGPT trying to reconstruct what happened in production. SherlockTrace does this directly in your editor:

1. Paste a stack trace or error log
2. SherlockTrace walks the call graph backwards from the error site
3. Uses symbolic execution to deterministically derive variable constraints from the code path
4. Uses LLM inference to fill in plausible values for the rest
5. Displays the entire execution path inline in your editor with confidence-tiered ghost text

Why this is different

Tool	Needs runtime?	Editor-native?	Symbolic constraints?
Sentry Seer	Needs SDK	Web UI only	No
Cursor BugBot	PR-time only	Chat only	No
Lightrun / Rookout	Live agent required	Inline values, yes	No
SherlockTrace	No	Yes	Yes

Roadmap

• CLI engine + public eval suite (CPython / FastAPI / scikit-learn bugs)
• VS Code extension
• "What would have prevented this?" feature
• Language adapters beyond Python

License

MIT