Ploinky and Explorer Integration
gitAgent is integrated as a Ploinky Model Context Protocol (MCP) agent and consumed by Explorer-facing user interface (UI) flows as a backend Git mediator.
Ploinky Runtime Integration
Agent lifecycle is controlled by gitAgent/manifest.json, while tool contracts come from gitAgent/mcp-config.json. AgentServer executes those tool commands in workspace context and returns normalized MCP responses to clients, which keeps Git execution policy centralized in the agent.
AssistOSExplorer Integration
Explorer integration uses the internal AssistOSExplorer repository. Frontend code calls callAgentTool("gitAgent", ...) and relies on this agent for Git operations, conflict checks, push/pull flows, and repository overview behavior.
Explorer remains the interaction surface, while gitAgent remains the operational boundary for Git process execution.
IDE-plugins Channel
The folder gitAgent/IDE-plugins/git-tool-button/ provides user interface plugin bundles inserted in Explorer toolbar slot file-exp:toolbar. Plugin dependencies include commit modal components, repo tree, diff viewer, conflict helper, status bar, and auth prompt components.
| Artifact | Role |
|---|---|
IDE-plugins/git-tool-button/config.json |
Registers plugin metadata, toolbar location, and component dependencies. |
IDE-plugins/git-tool-button/git-tool-button.js |
Hosts button presenter and binds controller lifecycle to Explorer host context. |
IDE-plugins/git-tool-button/git-tool-button-controller.js |
Calls MCP tools via Explorer API and orchestrates autocommit/pull/push/conflict UI logic. |