返回目錄

flameox

維護狀態: 活躍

morluto/flameox

執行時證據工具,幫助智慧體追蹤、剖析並消除應用與原生程式碼、GPU 核心及推理棧中的熱點。

前往 GitHub
$ dsh plugin add flameox

217

星數

19

Fork

Python

語言

MIT

授權條款

2026-07-25

建立於

2026-10-19

最近推送

採 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 外掛,絕不濫發。