Skip to main content

Module plugins

Module plugins 

Source
Expand description

Plugin discovery and manifest types.

Structs§

Manifest
Declarative metadata a plugin ships with — the on-disk objectiveai.json at <base_dir>/plugins/<owner>/<name>/<version>/objectiveai.json. The CLI reads and writes this shape verbatim (install writes the fetched manifest exactly as authored); the plugins get wire response is a lean projection of it.
McpServer
MCP server entry inside Manifest::mcp_servers. A host-exposed upstream identified by a name that agent declarations reference (via objectiveai_sdk::agent::ClientObjectiveaiMcpPluginEntry::mcp_servers), plus an authorization flag.
ViewerRoute
One HTTP route a plugin’s viewer registers on the host viewer’s embedded axum server. The full path served is /plugin/<repository>/<self.path>; on a hit, the body is JSON-decoded and forwarded as a PluginRequest { type: self.type, value: body } event to the frontend.

Enums§

HttpMethod
HTTP methods supported by ViewerRoute. Serializes as upper-case ("GET", "POST", …) on the wire.