Mateusz Sych fdec948abc Control channel: control.running lists what the app is running, across connections (#3654) (#3689) ...

* claim: #3654

* Control channel: control.running lists what the app is running, across connections (#3654)

control.pending answers only for the connection that asks, so a second client,
the MCP bridge after a reconnect or a script saw {"pending": null} while the app
was busy. control.running answers for the whole app, the same on every
connection and at once (the connection's own thread answers it, also while it
is busy with a timed-out request): every request the app has been sent and not
answered yet, oldest first, with its connection, id, method, command id (or a
batch's step count), seconds since it arrived and whether it still waits its
turn. A timed-out request stays listed until the app answers it, also after its
connection closed. Parameters are never shown.

The window marks a request started when it takes it (ControlRequest.started),
which tells queued from running. The MCP server gets a read-only `running` tool.

---------

Co-authored-by: MateuszSychXpl <151755914+MateuszSychXpl@users.noreply.github.com>

2026-10-21 00:54:33 +00:00

..

src

Control channel: control.running lists what the app is running, across connections (#3654) (#3689)

2026-10-21 00:54:33 +00:00

build.rs

Collect application resources for #433 (#833)

2026-10-14 00:49:32 -04:00

Cargo.toml

Macos space mouse support (#1815)

2026-10-17 18:15:15 -04:00