Ploinky and Explorer Integration

llmAssistant runs as a Ploinky Model Context Protocol (MCP) agent and is consumed by Explorer-facing flows and peer agents as an LLM utility intermediary.

Ploinky Runtime Integration

Runtime startup is defined by llmAssistant/manifest.json, tool contracts are defined by llmAssistant/mcp-config.json, and AgentServer executes wrapper commands to return normalized MCP responses. This keeps runtime orchestration consistent across user interface (UI) and peer-agent consumers.

AssistOSExplorer and Peer-Agent Usage

Explorer integrations can use llm_autocomplete for editor assist flows, while Git-oriented clients can use git_commit_message and llm_resolve_conflict. The same contracts are reusable by other agents instead of duplicating provider integrations.

This repository does not embed UI plugins directly; integration happens through MCP calls from Explorer or other agent clients.

Integration Boundary

Callers provide structured inputs and receive constrained outputs. Provider credentials, prompt shaping, and fallback behavior remain internal to llmAssistant, so client code stays provider-agnostic.