Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.
Rust agentai-agentapplecomputer-usecomputer-use-agentcontainerizationcuadesktop-automationhacktoberfestlumemacosmanusoperatorswiftvirtualizationvirtualization-frameworkwindowswindows-sandbox
fix(cua-driver): tell operators to reconnect agent sessions after history enable (#3224)
Francesco Bonacci62ede45ad845
diff --git a/libs/cua-driver/rust/crates/cua-driver/src/cli.rs b/libs/cua-driver/rust/crates/cua-driver/src/cli.rsindex 669325a21e..8f68e01566 100644--- a/libs/cua-driver/rust/crates/cua-driver/src/cli.rs+++ b/libs/cua-driver/rust/crates/cua-driver/src/cli.rs@@ -2542,6 +2542,14 @@ pub fn run_history_cmd(println!("Controls: history pause | resume | status | list | disable | delete --yes");+ // An MCP host that connected while history was unadmitted owns a+ // direct in-process runtime for its whole lifetime, and that+ // runtime never registers the history hook. Its actions are+ // dropped silently while every status surface reports ready, so+ // say so here rather than let the operator infer it. See #3220.+ println!(+ "Reconnect any agent session that was already connected: sessions started before now do not record actions."+ );} else {println!("{}", serde_json::to_string_pretty(&value).unwrap());}