Ploinky and Explorer Integration
tasksAgent is consumed as a Ploinky Model Context Protocol (MCP) agent and integrates with Explorer task user interface (UI) through dedicated IDE plugin components.
Ploinky Runtime Integration
Agent lifecycle and environment exposure are defined in tasksAgent/manifest.json, while task contracts are declared in tasksAgent/mcp-config.json. AgentServer executes these tools in workspace context and returns MCP responses to Explorer clients without exposing backlog internals directly.
AssistOSExplorer Integration
The practical consumer is the internal AssistOSExplorer repository. Explorer plugin UI triggers task operations through MCP calls and depends on this agent for safe backlog CRUD, listing, and reorder behavior.
Explorer remains presentation and interaction layer; tasksAgent remains backend authority for task-file operations.
IDE-plugins Channel
The folder tasksAgent/IDE-plugins/tasks-tool-button/ defines toolbar integration at file-exp:toolbar and includes backlog panel and task modal components.
| Artifact | Role |
|---|---|
IDE-plugins/tasks-tool-button/config.json |
Declares plugin metadata, toolbar location, and component dependencies. |
IDE-plugins/tasks-tool-button/tasks-tool-button.js |
Handles button behavior, backlog file filters, and modal flows in Explorer context. |
components/* |
Provides backlog panel, create modal, conflict modal, and document tasks modal behavior. |