aboutsummaryrefslogtreecommitdiffstats
path: root/server/patch_server.py
diff options
context:
space:
mode:
authorblasty <blasty@local>2026-07-24 01:56:47 +0200
committerblasty <blasty@local>2026-07-24 01:56:47 +0200
commit03564655fda1682e61bbf7055c3ef310c448cf28 (patch)
tree7debfd5ff2cc18055cd1b712a0b1ee8f1369c78c /server/patch_server.py
parentworker: wrap non-dict tool returns as {"result": ...} to match MCP shapes (diff)
downloadida-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 'server/patch_server.py')
-rw-r--r--server/patch_server.py4
1 files changed, 4 insertions, 0 deletions
diff --git a/server/patch_server.py b/server/patch_server.py
index ff14a09..6b69556 100644
--- a/server/patch_server.py
+++ b/server/patch_server.py
@@ -1,6 +1,10 @@
#!/usr/bin/env python3
"""Inject idatui's extra ida-pro-mcp tools into the installed server package.
+DEPRECATED along with the ida-pro-mcp transport: the default backend is now the
+idalib worker (idatui/worker.py), which registers these same tools in-process and
+needs no patching. Kept only for `--backend mcp`; slated for removal.
+
ida-pro-mcp lacks a few tools idatui needs. Rather than vendor/fork the server,
we keep the tool source here and inject it (idempotently) into the installed
``api_types.py``. That module is imported by every worker