pub struct Client {
pub id: String,
pub display: String,
pub docs: String,
pub verified: String,
pub cli: Option<ClientCli>,
pub file: Option<ClientFile>,
pub detect_dirs: OneOrMany,
pub mcp_names: Vec<String>,
pub instructions: Option<ClientInstructions>,
pub hooks: Option<ClientHooks>,
pub unverified: Option<String>,
}Expand description
One MCP client.
Fields§
§id: StringStable identifier, used by --client.
display: StringHuman-readable name.
docs: StringWhere this entry’s facts came from.
verified: StringThe date docs was last checked.
cli: Option<ClientCli>How to register through the client’s own command, if it has one.
file: Option<ClientFile>How to register by editing the client’s config file.
detect_dirs: OneOrManyDirectories the client creates for itself, used to tell “installed but never configured” apart from “not installed”. Any one existing is enough; a client with a different home on each OS lists them all.
mcp_names: Vec<String>The names this client gives in MCP initialize, so what it writes can
be shown under display. A trailing * matches a prefix.
instructions: Option<ClientInstructions>Where this client reads a repository’s instructions from.
hooks: Option<ClientHooks>The client’s hook system, for autopilot’s automatic forks. Absent for a client whose hooks are unverified or that has none: autopilot then never runs anything through it.
unverified: Option<String>What could not be confirmed against docs on verified, in a
sentence: a client name never seen in a shipped build, a path the
documentation does not give for one OS. Shown by memfork doctor
and never silently assumed.
Implementations§
Source§impl Client
impl Client
Sourcepub fn detect_dirs_here(&self, home: &str) -> Vec<PathBuf>
pub fn detect_dirs_here(&self, home: &str) -> Vec<PathBuf>
The client’s own directories on this machine, as the registry names them.
Sourcepub fn file_writable(&self, scope: Scope) -> bool
pub fn file_writable(&self, scope: Scope) -> bool
Whether MemFork may write this client’s file for a scope.
A missing path is the prohibition: the registry simply does not carry the location, so no code path can reach it.