pub struct ClientCapabilities {
pub read_text_file: bool,
pub write_text_file: bool,
pub terminal: bool,
}Expand description
What the client offers to do on the agent’s behalf (ADR-0007 §3).
These are advertised at initialize, and the defaults are a deliberate product
decision rather than a shrug — see Default.
Fields§
§read_text_file: boolServe file contents from the live buffer, unsaved changes included. This is the concrete mechanism behind “the agent shares your buffers” (ARCHITECTURE.md §9.2).
write_text_file: boolAccept writes — as proposals, never straight to disk.
terminal: boolExecute structured commands through model-owned PTY terminals.
Trait Implementations§
Source§impl Clone for ClientCapabilities
impl Clone for ClientCapabilities
Source§fn clone(&self) -> ClientCapabilities
fn clone(&self) -> ClientCapabilities
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreimpl Copy for ClientCapabilities
Source§impl Debug for ClientCapabilities
impl Debug for ClientCapabilities
Source§impl Default for ClientCapabilities
impl Default for ClientCapabilities
Source§fn default() -> Self
fn default() -> Self
Both on.
Advertising write_text_file: false is tempting and wrong: an agent told the
client cannot write files does not give up, it shells out and writes the file
itself, turning a reviewable proposal into an opaque side effect. Saying yes and
routing every write through review is what keeps edits in the loop.