aboutsummaryrefslogtreecommitdiffstats
path: root/docs/TUI_DRIVING_BLUEPRINT.md (unfollow)
Commit message (Collapse)AuthorFilesLines
25 hoursdocs: sweep for the worker-only reality (drop mcp supervisor/spawn.sh/--db)blasty1-4/+4
* RPC.md: the TUI is launched via `./ida-tui <bin> --rpc <sock>` (was `idatui.tui --db`); point the "regression lock" note at rpcclient/drive + the pilot instead of the deleted rpc_smoke.py. * PAGING_FINDINGS.md: reframe the intro as the ida-pro-mcp tool functions the worker now calls in-process (shapes/caps unchanged); replace the supervisor-era "idle self-exit" + "max_workers cap" sections with the single-owned-worker lifecycle (no cap, no idle-exit, crash -> reconnect). * TEXTUAL_NOTES.md / TUI_DRIVING_BLUEPRINT.md: drop the ida-pro-mcp framing and the deleted rpc_smoke.py references (-> test_scenarios.py / rpcclient). Also updated the idatui + idatui-rpc skills (in ~/.pi, outside the repo) to the worker model: no supervisor/spawn.sh/--db, worker python + $IDATUI_WORKER_PYTHON, worker.py/worker_client.py/errors.py architecture, and the load-starvation gotcha.
2026-07-10docs: blueprint for generalizing the TUI-driving layer (e.g. gdb)blasty1-0/+355
A design reference for bringing the idatui spawn/drive/introspect experience to other terminal apps. Captures the invariants worth keeping, the reusable core vs per-target Adapter split, a target taxonomy (embedded / control- channel / black-box PTY), the three hard problems (injection, settle, introspection) with technique gradients, tmux as the universal substrate, and a concrete gdb worked example (TUI pane + gdb-Python plugin as the adapter). No code.