aboutsummaryrefslogtreecommitdiffstats
path: root/ida-tui
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 /ida-tui
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 'ida-tui')
-rwxr-xr-xida-tui12
1 files changed, 7 insertions, 5 deletions
diff --git a/ida-tui b/ida-tui
index d1f4179..ed4db09 100755
--- a/ida-tui
+++ b/ida-tui
@@ -2,12 +2,14 @@
# Caveman launcher for the IDA TUI:
#
# ./ida-tui foo.elf # open a binary and drive it — that's it
-# ./ida-tui # attach to the sole open session
-# ./ida-tui --db <id> # attach to a specific session
+# ./ida-tui # attach to the sole open session (mcp)
+# ./ida-tui --db <id> # attach to a specific session (mcp)
#
-# It starts the ida-pro-mcp supervisor if it's down, recovers a binary left
-# wedged by a crashed worker, opens/adopts the session, and drops you into the
-# TUI. Uses the venv python that has textual (override with $IDATUI_PYTHON).
+# Opening a binary now spins up our own idalib worker (a unix-socket subprocess;
+# no HTTP, no supervisor). --db/attach still use the deprecated ida-pro-mcp
+# path; pass --backend mcp to force it. Uses the venv python that has textual
+# (override with $IDATUI_PYTHON); the worker auto-picks the python that has
+# ida_pro_mcp (override with $IDATUI_WORKER_PYTHON).
set -eu
SCRIPT_DIR=$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)