Who it is forAn engineer who already has a profiler or trace file from an earlier run and needs a structured read of it.
The problemRerunning a slow or hard-to-reproduce workload just to read its profile wastes time and may change the result.
The outcomeBounded evidence extracted from the exact artifact file, with its provenance and limits recorded.
What you need first
- Node.js (for npx) or uv (for uvx) installed
- Python 3.12 or newer for the local development path
- An absolute path to an existing artifact file, or an explicit command to run from an absolute working directory
Steps
- Find the exact absolute path to your saved artifact file, such as an artifact.json from an earlier run.
- Run
uvx flameox analyze preview_artifact /absolute/path/to/artifact.jsonwith that path. - Review the returned evidence, noting the observed inputs and listed limitations.
- Keep the analysis_id only for the current session, since analysis IDs expire when evicted or when the server stops.
Prompt for your agent
Using the flameox repo, run `uvx flameox analyze preview_artifact <absolute artifact path>` on the file at <absolute artifact path>. Report the typed evidence and coverage, separating observed from derived claims. Verify that the artifact path you passed is the exact file and that no parent directory was searched.
Caveat. Flameox only reads the exact artifact path given and does not search parent directories, so the path must be correct and absolute.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for morluto/flameox and "Analyze an existing profiler artifact without rerunning it"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer