Skip to main content

Module integration

Module integration 

Source
Expand description

The contract every AI-harness integration implements.

There are several distinct surfaces an integration may expose:

Each surface is its own trait so callers cannot accidentally call install_mcp on a harness that does not support MCP, the type system forbids it. Use crate::registry::mcp_capable to enumerate the agents that implement McpSurface.

Structs§

InstallReport
Outcome of a successful Integration::install.
UninstallReport
Outcome of a successful Integration::uninstall.

Enums§

MigrationReport
Outcome of a successful Integration::migrate.

Traits§

InstructionSurface
One AI harness’s standalone-instruction installer.
Integration
One AI harness’s hook installer.
McpSurface
One AI harness’s MCP-server installer.
SkillSurface
One AI harness’s skill installer.