ida-tui.git/idatui/drive.py, branch main

drive: make `dis` drive the live UI too (generalize _show_decomp -> _show_view)

2026-07-11T19:09:45Z

drive pc: render pseudocode in the TUI, not just the driver

2026-07-11T08:09:03Z

The pc command called only the read-only pseudocode RPC (runs off the UI loop, never touches the screen), so LLM-driven sessions showed nothing on the live pane. Compose goto + toggle_view + search so the real TUI navigates to the function, makes the decomp pane the visibly-active view, and jumps the cursor to the needle — then return the same text as before.

drive: add save + retype; point docs/skills at the ergonomic frontend

2026-07-10T14:21:36Z

Round out idatui.drive with 'save' and 'retype ' so the whole common RE loop (orient/understand/act/persist) has a terse command. Update docs/RPC.md and both skills (idatui, idatui-rpc) to recommend idatui.drive as the day-to-day driving surface, with rpcclient/raw as the fallback for unwrapped verbs.

drive: ergonomic RE helper over the RPC socket (terse text, auto socket)

2026-07-10T14:17:50Z

Driving via rpcclient meant re-exporting the socket every fresh shell, long invocations, and piping ~every call through python -c to pull one field or grep pseudocode. idatui.drive fixes that: it auto-resolves the socket (the single live pane from the registry), prints compact text instead of JSON, and bundles the common gestures: where | go | pc [substr] | dis [n] | callees/callers | names | rename | mv old=new... | note | screen | raw k=v So 'goto+rename+parse' becomes 'drive rename old new', and 'pseudocode | python -c grep' becomes 'drive pc fn needle'. rpcclient stays the raw transport. rpc_smoke drives it end-to-end (29 green).