ida-tui.git/spawn.sh, branch maintui for headless idahttps://git.sl0p.foo/ida-tui.git/atom/spawn.sh?h=main2026-07-11T19:09:45Zspawn.sh: run location-independent + env-configurable host/port/target2026-07-11T19:09:45Zuseruser@clank2026-07-11T19:09:45Zurn:sha1:4e68fbb9e052d874704162254a07a854e9dcc82eserver: inject a del_type tool into ida-pro-mcp (enables struct delete)2026-07-10T09:55:33Zblastyblasty@local2026-07-10T09:55:33Zurn:sha1:25590831d851e9e8ab8ff15b4122e01dfafd6d58
ida-pro-mcp has no delete-type tool, so struct-editor delete couldn't work. We
don't vendor/fork the server; instead server/patch_server.py idempotently appends
a del_type @tool to the installed ida_pro_mcp/ida_mcp/api_types.py, which every
worker (python -m ida_pro_mcp.idalib_server) imports -> it self-registers on the
shared MCP_SERVER. spawn.sh runs the patch before launching, so it's re-applied
on each start (survives reinstalls) and tracked in-repo instead of hand-editing
site-packages.
del_type calls ida_typeinf.del_named_type(get_idati(), name, NTF_TYPE). After a
supervisor restart, Program.delete_type() now succeeds; the struct editor's Del
removes the type and the list refreshes. Verified end-to-end; pilot 84/84.
stop piling up idalib workers; raise max-workers headroom2026-07-09T13:55:38Zblastyblasty@local2026-07-09T13:55:38Zurn:sha1:4a83deb7bc2dcfed4696cd1bf2542a947ad7c4fb
Root cause of 'Maximum idalib worker count reached': the app bumped idle_ttl to
~never on every open, so sessions never freed and hit the default cap of 4.
- app: drop the immortal bump_idle_ttl(1e9); rely on the KeepAlive heartbeat
(120s) to keep the running session warm, and open with a moderate idle_ttl
(1800s) so the worker self-exits and frees its slot after the TUI closes.
- spawn.sh: set IDA_MCP_MAX_WORKERS (default 8) for headroom.
- doc: supervisor prunes unreachable workers before counting, so killing an idle
worker frees a slot on the next open.
(Verified separately: big/truncated decompile results propagate renames fine via
the earlier force_recompile fix.)
persistent MCP client: warm handshake, keep-alive pool, error taxonomy, thread-safe2026-07-09T09:14:23Zblastyblasty@local2026-07-09T09:14:23Zurn:sha1:eec630887ce72a7dafae4c33f5e85ad7c746b038
- IDAClient: single handshake, ~7ms warm calls (vs ~60ms cold CLI)
- keep-alive connection pool over http.client; concurrent-safe (40 threads OK)
- grounded error taxonomy: IDAToolError on isError, soft per-item errors as data
- session-expiry recovery (404 -> re-handshake -> retry), bounded transport retries
- auto db-injection + resolve_db (ignores stale empty-id sessions)
- live smoke test: 13/13 pass