diff options
| author | blasty <blasty@local> | 2026-07-24 01:56:47 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-24 01:56:47 +0200 |
| commit | 03564655fda1682e61bbf7055c3ef310c448cf28 (patch) | |
| tree | 7debfd5ff2cc18055cd1b712a0b1ee8f1369c78c /idatui/worker.py | |
| parent | worker: wrap non-dict tool returns as {"result": ...} to match MCP shapes (diff) | |
| download | ida-tui-03564655fda1682e61bbf7055c3ef310c448cf28.tar.gz ida-tui-03564655fda1682e61bbf7055c3ef310c448cf28.tar.xz ida-tui-03564655fda1682e61bbf7055c3ef310c448cf28.zip | |
deprecate: make the idalib worker the default backend; mark mcp path for removal
Opening a binary now defaults to our own idalib worker; the ida-pro-mcp HTTP
supervisor path is deprecated (kept only for --db/attach and --backend mcp).
* launch.py: --backend default resolves to worker for a fresh binary open, mcp
for the attach modes (--db / bare `ida-tui`, which have no worker equivalent);
explicit --backend or IDATUI_BACKEND still wins. Logs a deprecation notice when
the mcp path is used.
* Deprecation markers on client.py and server/patch_server.py; the ida-tui shell
header and README now describe the worker as primary and note
$IDATUI_WORKER_PYTHON. TODO tracks the removal checklist.
No code deleted yet — the mcp fallback stays until the worker is proven on a box
where idalib can spawn (pilot against --backend worker is the gate). Backend
resolution matrix verified: `ida-tui bash`->worker, bare/`--db`->mcp, explicit
flag/env honored.
Diffstat (limited to 'idatui/worker.py')
0 files changed, 0 insertions, 0 deletions