From 03564655fda1682e61bbf7055c3ef310c448cf28 Mon Sep 17 00:00:00 2001 From: blasty Date: Fri, 24 Jul 2026 01:56:47 +0200 Subject: deprecate: make the idalib worker the default backend; mark mcp path for removal MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- TODO | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'TODO') diff --git a/TODO b/TODO index 2311d7d..4dd215e 100644 --- a/TODO +++ b/TODO @@ -4,6 +4,14 @@ bugs: current: +[~] DITCH ida-pro-mcp -> our own idalib worker (idatui/worker.py + WorkerClient) + [x] worker + WorkerClient (drop-in for IDAClient, same tool shapes) + [x] --backend {worker,mcp}; worker is now the DEFAULT for opening a binary + [x] worker spawns under the IDA python; {"result":...} wrapping to match MCP + [ ] run the pilot suite against --backend worker (blocked: idalib reaping here) + [ ] progress reporting during analysis (worker streams notes to the overlay) + [ ] once solid: delete client.py, server/patch_server.py, spawn.sh, and + launch.py's whole supervisor/ensure_server/lock-sweep dance [x] RPC endpoint for robot-spectator-ida -> progressssss -- cgit v1.3.1-sl0p