What problem does it solve?
trace helps you quickly find the right project files, code, and related knowledge even when you don’t know where it lives or when it was last changed.
Core Features & Use Cases
- Unified discovery across history and memory: searches current repo contents plus Oracle memory traces and prior knowledge/logs to surface where something exists.
- Depth options for hard-to-find items: runs in fast Oracle-only mode, a smart Oracle-then-escalate mode, or a wave-based deep search across files, git history, cross-repo matches, and GitHub issues/PRs.
- Distills results into a persistent trace log: writes a dated trace record with friction scoring and goal-backward confidence checks so future searches get faster and more reliable.
Real-world use case: you remember a project feature name or config key but can’t recall which repo or file it’s in; trace can search your codebase, git history, and Oracle memory and then log the findings for later reuse.
Quick Start
Ask for a trace of what contains the keyword by running: /trace <query>