flameox
Runtime evidence that helps agents trace, profile, and burn down hotspots in application and native code, GPU kernels, and inference stacks.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/morluto/flameox with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/morluto/flameox'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/morluto--flameox)HTML
<a href="/listings/morluto--flameox"><img src="/api/listings/morluto--flameox/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
uv sync --extra dev --extra memory --extra trace --extra cpu uv run flameox mcp inspect uv run flameox analyze artifact.preview /absolute/path/to/artifact.json uv run flameox capture --provider direct --cwd "$PWD" -- python benchmark.py
The MCP server has no workspace or project binding:
uv run flameox mcp serve
Run the short global setup wizard through npm:
npx flameox@latest setup
Setup detects Claude Code, Cursor, OpenCode, Codex, Gemini CLI, and Google Antigravity, then asks which clients should use Flameox. It preserves unrelated client configuration and writes a Python 3.12 `uvx` launcher pinned to the exact Flameox release that ran setup. Restart or reconnect changed clients afterward. For automation, pass `--client codex --yes`, repeat `--client`, or use `--all --yes`; `--dry-run` reports the same global paths without writing them. Detection is never automation consent.
Explicit `--provider` selections prepare the exact version-pinned `uvx` environment in the saved launcher by resolving it once into uvx's cache; they do not create a persistent global `uv tool` installation. Each invocation declares the complete managed provider set for that launcher rather than adding to remembered state. Use `--timeout-seconds` for a slow cold resolution. System and vendor tools are diagnosed with external install guidance. Setup never initializes or mutates a project.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 126 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <h1 align="center">flameox</h1>
- <p align="center">
- <img
- src="docs/assets/flameox-mascot-flamegraph.png"
- width="420"
- alt="flameox mascot: an ox with a flame graph between its horns"
- >
- </p>
- <p align="center"><strong>Bounded local runtime evidence for coding agents.</strong></p>
- <!-- mcp-name: io.github.morluto/flameox -->
- Flameox coordinates profilers, benchmark tools, trace processors, and direct local targets. It
- turns an explicit artifact or command into bounded evidence while keeping durable preservation
- optional. The agent chooses hypotheses and experiments; Flameox records observed inputs,
- execution provenance, typed evidence, coverage, and limitations.
- There is no workspace to initialize or project configuration to maintain. Pass exact artifact
- paths to analysis and an explicit argv plus absolute working directory to capture. Flameox does not
- search parent directories, edit project files, or provide a hosted service.
- ## Quick start
- Configure an MCP client with the global setup command:
- ```console
- npx flameox@latest setup
- ```
- Setup detects supported clients and asks which configurations to update. For automation, select
- clients explicitly, for example `--client codex --yes` or `--all --yes`; `--dry-run` reports the
- paths and actions without writing. Setup preserves unrelated client configuration and does not
- change project files. See [the npm package guide](npm/README.md) for details.
- Update existing MCP registrations with:
- ```console
- npx flameox@latest update
- ```
- `update --check` reports available updates without changing configuration. Updates preserve each
- client's provider extras and settings, verify the new environment before changing release pins,
- and report which clients need a restart or reconnect. Use `--client codex` to select one client,
- or `--version 0.2.8` to select a specific release, including for rollback. The Python CLI exposes
- the same `flameox update` command.
- For direct CLI use, pass exact artifact paths or an explicit command:
- ```console
- uvx flameox analyze preview_artifact /absolute/path/to/artifact.json
- uvx flameox capture --provider direct --cwd "$PWD" -- python benchmark.py
- ```
- To launch the stdio MCP server manually:
- ```console
- uvx flameox mcp serve
- ```
- For local development, clone the repository, install its development dependencies, and inspect the
- available tools:
- ```console
- git clone https://github.com/morluto/flameox.git
- cd flameox
- uv sync --extra dev --extra memory --extra trace --extra cpu
- uv run flameox mcp inspect
- ```
- ## Evidence and storage
- Analysis and unpreserved capture use bounded session scratch. Session `analysis_id` values expire
- when evicted or when the server stops. Explicit preservation creates the user-level Flameox data
- directory and stores native bytes and a canonical evidence bundle by SHA-256. Set
- `FLAMEOX_DATA_DIR` to choose another location. Preservation is optional; it does not imply full
- console-output retention.
- Flameox distinguishes observed, derived, and inferred claims. Profiles guide exploration but do
- not establish causality or performance improvement. Confirmatory claims require representative
- workloads, declared metrics and estimands, compatible identities, preserved samples, and a
- semantic oracle.
- ## MCP
- The MCP server has no workspace binding. It exposes named analysis and capture tools through the
- same operation registry as the CLI. Analysis tools accept explicit sources; capture tools accept
- a typed target and provider. Tool schemas expose operation-specific fields directly. Inspect the
- catalog with `flameox mcp inspect`; use `--tool TOOL_NAME` for
- focused schemas and examples. The complete contract and current tool catalog are in
- [the interface guide](docs/interfaces.md).
- Tools return their full bounded results inline, including failures and recovery actions. Preserved
- evidence has a durable `evidence_id`; `inspect_evidence` returns its redacted metadata and replay
- sources inline.
- Capture takes argv, not a shell string. A direct target supplies an absolute working directory and
- bounded environment overrides. Results may include `next_page`; replay its named analysis tool
- and arguments unchanged. Capture continuations read collected artifacts and do not rerun the
- target. MCP work belongs to the live request, so cancellation applies directly and no detached job
- survives a restart.
- ## Documentation
- - [Architecture](docs/architecture.md) describes process and package boundaries.
- - [Storage and evidence](docs/storage-and-evidence.md) defines preservation and provenance.
- - [Investigations](docs/investigations.md) covers experiments, comparison, and evidence quality.
- - [Adapters](docs/adapters.md) documents provider compatibility and integration policy.
- - [Runtime safety](docs/runtime-safety.md) covers limits, recovery, integrity, and privacy.
- - [Interfaces](docs/interfaces.md) defines CLI and MCP contracts.
- - [Testing](docs/testing.md) describes test selections and known proof gaps.
- ## Development
- Flameox requires Python 3.12 or newer and uses the committed `uv.lock`. See
- [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and contribution guidance.
- ```console
- uv run ruff check src tests tools
- uv run ruff format --check src tests tools
- uv run mypy src tests tools
- uv run pytest -q
- ```
- Flameox is licensed under the MIT License.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.