flameox

项目详情摘要

flameox Bounded local runtime evidence for coding agents. Flameox coordinates profilers, benchmark tools, trace processors, and direct local targets. It gives an agent a short path from an explicit native artifact or live command to bounded evidence, while keeping preservation optional. There is no workspace to initialize, `flameox.toml`, SQLite control plane, durable job to poll, or parent-directory discovery. Analyze existing artifacts by passing their exact paths and formats. Quick start The MCP server has no workspace or project binding: Run the short global setup wizard through npm: 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. Authority model Analysis and unpreserved capture make no durable Flameox writes. Capture artifacts stay in bounded session scratch until preservation, least-recently-used eviction, or server shutdown. An evi