Architecture

tasksAgent is an intermediary layer between Explorer task user interface (UI) actions and repository backlog file operations, routed through Ploinky over Model Context Protocol (MCP).

Component Overview

Component	Location	Role
Model Context Protocol tool contracts	`tasksAgent/mcp-config.json`	Declares task tools, schemas, wrapper command, and per-tool `TOOL_NAME`.
Wrapper command entrypoint	`tasksAgent/tools/tasks_tool.sh`	Starts one Node process per invocation and forwards tool identity.
Dispatcher and handlers	`tasksAgent/tools/tasks_tool.mjs`	Parses Model Context Protocol envelope data, validates paths and arguments, executes tool logic.
Markdown backlog persistence	`tasksAgent/tools/backlog_markdown.mjs`	Parses and serializes `.backlog` and `.history` Markdown files with persisted task ids.
Explorer user interface plugin channel	`tasksAgent/IDE-plugins/tasks-tool-button/`	Injects task tooling in Explorer toolbar and task modals.

Runtime Boundary

AgentServer executes task tools from MCP configuration. Each operation runs through the wrapper script, then through dispatcher logic that validates repoPath/backlogPath constraints, and then applies backlog CRUD behavior through the shared Markdown persistence layer.

{
  "name": "task_list",
  "command": "tools/tasks_tool.sh",
  "cwd": "workspace",
  "env": {
    "TOOL_NAME": "task_list"
  }
}

Intermediary Guarantee

Explorer does not write backlog files directly as a backend authority. It calls tasksAgent contracts, and the agent enforces repository scope, task normalization, and persistence behavior before returning results.

The architecture objective is contract-safe task operations, not moving backlog logic into Explorer host internals.