morluto/flameox
Runtime evidence that helps agents trace, profile, and burn down hotspots in application and native code, GPU
Flameox gives coding agents local runtime evidence for investigating performance, memory, execution, concurrency, and reliability. It connects profilers, benchmark tools, and trace processors to a local evidence record — preserving native artifacts and provenance — then exposes bounded evidence to the agent. Workloads are declared in flameox.toml as typed argument arrays, experiments run against a pinned corpus snapshot, and the CLI/MCP server expose bounded task-shaped operations rather than raw shell strings.
Install
npx flameox@latest setupThe setup command installs a versioned local runtime and changes only approved client configuration; restart the MCP client and ask it to initialize Flameox in the project (creates .diagnostics/ only after the client calls the init workflow). MCP name io.github.morluto/flameox. Python 3.12+ and a committed uv.lock are required for source development.
Compatibility
Connects to any MCP host including DeepSeek Harness. Evidence sources include pyperf, py-spy, pytest-reportlog, coverage.py, Memray, Perfetto, torch.profiler, Nsight, ROCprofiler, NVBench, and typed inference-provider exports; availability depends on host and adapters.
Details
- Repo: morluto/flameox
- Category: Coding & Development
- Stars: 34
- Version: Python 3.12+; CLI + MCP server
- Last push: 2026-09-21
- First seen: 2026-07-25
Recent updates
The current README documents the guided setup, evidence adapters, named workloads, experiments/analysis commands, .diagnostics/ storage layout, and integrity/retention commands (validate, catalog rebuild, recover, gc).
FAQ
- Is Flameox a DSH plugin?
- No — it is a standalone CLI + MCP server that any MCP host, including DeepSeek Harness, can connect to.
- Where does the evidence live?
- In the project's .diagnostics/ directory: a SQLite control plane, content-addressed artifacts, immutable Parquet generations, and a rebuildable DuckDB catalog.
- Does it keep data local?
- Yes — data stays local; the control process performs network I/O only for explicit setup, upgrade, approved provider acquisition, or enabled symbol services.
Alternatives
morluto/leantoken · biociao/dsh-science · cofy-x/axern