返回目录

flameox

维护状态: 活跃

morluto/flameox

运行时证据工具,帮助智能体追踪、剖析并消除应用与原生代码、GPU 内核及推理栈中的热点。

前往 GitHub
$ dsh plugin add flameox

114

星标

4

Fork

Python

语言

MIT

许可证

2026-07-25

创建于

2026-09-21

最近推送

采用 MIT 许可、本地优先的 Python 工具,将性能分析、基准测试与追踪转化为智能体可据以行动的边界化证据——通过 `uv` 运行,或作为 DeepSeek Harness 的 MCP 服务器使用。

DSH 适配

原生运行时

作者声明

安全审计

未审计

最后核验

2026-09-01

许可证

MIT

01它能帮你完成什么?

  • Trace and profile hotspots in application and native code, GPU kernels, and inference stacks from a coding agent

    bounded, inline runtime evidence — profiler / benchmark / trace output — without a durable control plane

    Developers and coding agents (including DeepSeek Harness) that need local-first performance evidence

  • Capture runtime evidence from a live command or an existing native artifact inside an agent loop

    process-lifespan evidence with optional preservation to `<project>/.flameox`

    Performance engineers who want agents to burn down hotspots with explicit, auditable evidence

02如何接入 DeepSeek Harness?

前置条件

  • Python project managed with `uv` (the README installs extras via `uv sync` / `uv run`)
  • A local target: an existing native artifact (with its exact path and format) or a live command to benchmark

安装步骤

  1. 01

    Sync the optional extras you need: `uv sync --extra dev --extra memory --extra trace --extra cpu`

  2. 02

    Discover capabilities for an intent: `uv run flameox capabilities discover --intent "CPU hotspots"`

  3. 03

    Analyze an existing artifact: `uv run flameox analyze artifact.preview /absolute/path/to/artifact.json`

  4. 04

    Or capture live evidence: `uv run flameox capture --provider direct -- python benchmark.py`

  5. 05

    Run the MCP server for an agent: `uv run flameox mcp serve --project-root "$PWD"` (the MCP server fixes its project root at startup)

验证接入成功

  • Print the stdio client configuration with `flameox setup` to confirm the MCP wiring
  • Confirm capabilities are discovered for your intent before analyzing or capturing

回滚

  • Stop the `flameox mcp serve` process and drop the `--project-root` MCP config printed by `flameox setup`
  • Version 0.2 has no SQLite control plane, so removing `<project>/.flameox` leaves no stale state

03DSH 适配与能力边界

DSH 适配原生运行时

MCP server (`flameox mcp serve`) exposing profiler / benchmark / trace capabilities to DeepSeek Harness agents; also runnable as direct `uv` CLI commands

  • Capabilities discovery

    an intent such as "CPU hotspots"→the matching profiler / benchmark / trace capabilities for an agent to use

  • Artifact analysis

    an explicit native artifact path (e.g. artifact.preview with exact path and format)→bounded inline evidence for the supplied artifact

  • Live capture

    a direct target command (e.g. `python benchmark.py`) via `--provider direct`→bounded runtime evidence from the live command

    writes optional session scratch/cache and, on explicit preservation, to `<project>/.flameox`

04适合谁?何时不该用?

适合

  • Developers and coding agents (including DeepSeek Harness) that need local-first performance evidence
  • Performance engineers who want agents to burn down hotspots with explicit, auditable evidence

不适合

  • Version 0.2 is a clean break: old `.diagnostics` state is not migrated, and there is no workspace to initialize, no `flameox.toml`, and no SQLite control plane.

05兼容性、维护与安全提示

  • Version 0.2 is a clean break: old `.diagnostics` state is not migrated, and there is no workspace to initialize, no `flameox.toml`, and no SQLite control plane.
  • Flameox is local-first: evidence stays in a bounded process-lifespan runtime, and preservation to `<project>/.flameox` is optional and only happens on explicit request.
2026-07-252026-09-01v0.1.15

MIT · actively maintained (latest release v0.1.15, 2026-08-30)

06常见问题

如何将 flameox 接入 DeepSeek Harness?

使用 `uv run flameox mcp serve --project-root "$PWD"` 启动 MCP 服务器(服务器在启动时固定其项目根目录);`flameox setup` 会打印等价的 stdio 客户端配置供智能体使用。

flameox 具体做什么?

它协调性能分析器、基准测试工具、追踪处理器与直接本地目标,使智能体能够从明确的原生产物或实时命令快速获得有边界的证据,且结果保存是可选的。

需要初始化工作区或配置文件吗?

不需要。0.2 版本是一次彻底重构:无需初始化工作区、没有 `flameox.toml`,也没有 SQLite 控制面——你直接将精确的产物路径与格式传给 `analyze` 即可。

我的数据会被上传吗?

不会。flameox 是本地优先的;证据保留在生命周期受控的运行时中,仅当你显式请求时,才会将可选的会话缓存保存到 `<project>/.flameox`。

08数据与来源

  • 作者声明github.comc7b584fb6549…

    Bounded local runtime evidence for coding agents.

  • 作者声明github.comc7b584fb6549…

    Flameox coordinates profilers, benchmark tools, trace processors, and direct

页面基于项目公开文档、仓库元数据和 DSH Plugins 的结构化解析生成;最后核验于 2026-09-01。发现错误?提交更正。

🏆

最佳 DeepSeek Harness 插件

从全目录挑出的 12 个值得优先安装的插件,覆盖各个分类。

DSH Plugins 是独立的 DeepSeek Harness 插件市场,与 DeepSeek 官方无关,也不代表官方背书。第三方插件未经安全审计,安装前请审查源码。

每周获取最新的 DeepSeek Harness 插件,绝不滥发。