Skip to main content

Module install

Module install 

Source
Expand description

AI-1b / AG‑4: the crate-owned install(boot) entry point.

After the AG‑4 fold, lattice-ai owns both agent transports, so the single host-facing lattice_ai::install(&mut boot) line wires both: the ACP agent client (install_acp, below) and the MCP IDE peer (crate::mcp::install). The host’s Phase-B install list holds one line and zero host internals (no Editor:: method, no host Effect/Action variant, no Editor field for the logger). AG‑5 relocates install_acp under crate::acp and puts each call behind its #[cfg(feature = …)].

The :ai-log picker that OPENS a buffer is a later task; install_acp only wires the producer side (AiLogger), the supervisor, the ex-commands, and AiLogMode (which seeds/streams into a buffer once one is opened by name).

Functions§

install
Wire the AI subsystem into the editor at boot. The transport-neutral log substrate (AiLogger + AiLogMode + :ai-log) is always installed; each agent transport is wired only when its feature is enabled.