blob: 1f6b11918d7ceadb66c90eb63066f048c3874bc0 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
## RPC functionality
we need some way to drive an instance of our IDA tui programatically,
with all UI interactions actually being shown as if a regular user was driving
the software.
the rationale is we'll be doing some machine-assisted reverse engineering
and livestreaming the work/progress on our little terminal streaming platform,
sl0p.foo !
come up with a plan on how to architect this, remember the machine (you, the LLM)
that will eventually be driving our TUI is running inside a tmux pane.
I think it'd be most sensible if you assume we run the TUI in some kind of rpc/server
mode in a second pane and talk to it over unixsocket/tcp.
I think we want some "highlevel" RPC primitives for UI actions, but also a
more raw RPC primitive that lets us send "keystrokes" to the TUI.
carefully go through our current architecture and the requirements I vaguely
sketched out above and propose an implementation.
|
