Complete agent monitoring and Galaxy Control integration
- expose command-monitor conversations and preserve visible agent transcripts - add bounded polling and a dedicated shell interrupt tool - improve direct-provider images, skills, tool history, and usage handling - package and brand Galaxy Control across releases, installers, persistence, and docs
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
//! Blocking client helpers used by the standalone `warpctrl` CLI.
|
||||
//! Blocking client helpers used by the standalone `galaxyctrl` CLI.
|
||||
//!
|
||||
//! Authentication is a two-transport flow:
|
||||
//!
|
||||
@@ -14,7 +14,7 @@
|
||||
//! issuing a short-lived, action-scoped credential.
|
||||
//! 4. The client keeps that credential in memory and presents it as a bearer
|
||||
//! token only to the selected instance's loopback HTTP endpoint. The running
|
||||
//! Warp app revalidates the credential, current settings, action scope, and
|
||||
//! Galaxy app revalidates the credential, current settings, action scope, and
|
||||
//! request before dispatch.
|
||||
//!
|
||||
//! Client-side validation prevents accidental use of inconsistent discovery
|
||||
|
||||
Reference in New Issue
Block a user