TaskSync
Human-in-the-loop feedback for AI coding agents. Pause your agent mid-task, give it new directions, attach screenshots, and keep it on track — without restarting the conversation.
README
TaskSync
Human-in-the-loop feedback for AI coding agents. Pause your agent mid-task, give it new directions, attach screenshots, and keep it on track — without restarting the conversation.
Reply from anywhere. Enable Remote Mode and get Telegram notifications when your agent needs input. Tap a quick-reply button or type a response from your phone — the agent picks up instantly.
Quick Start
npx tasksync-mcp-http
Server starts on port 3011 (MCP) and 3456 (web UI). Open http://localhost:3456 to see the feedback dashboard.
OpenCode Plugin (Recommended)
The opencode-tasksync plugin is the best way to use TaskSync. Add one line to your OpenCode config:
{
"plugin": ["opencode-tasksync"]
}
What the plugin gives you that raw MCP can't:
- Zero-config agent behavior — A
daemonagent is injected automatically with the complete feedback loop protocol. No prompt pasting, no manual setup. - Augment any agent — Add feedback loops to your existing
coder,ask,buildagents with one config line. They start callingget_feedbackbetween tasks. - Unbreakable connections — SSE transport with 30s keepalives and automatic reconnection (exponential backoff up to 15s). Server restarts, network blips — the agent never notices.
- Native image support — Attached images appear directly in the LLM conversation via OpenCode's
tool.execute.afterhook. No temp files, no workarounds. - Remote Mode (OpenCode exclusive) — The plugin captures the agent's latest response and forwards it to Telegram. You see what the agent is asking and can reply without touching your laptop.
- FYI status updates — When the agent works for 30+ seconds without asking for feedback, you get a status update on Telegram so you know it's still making progress.
How the plugin makes this possible: It hooks into OpenCode's event system — experimental.text.complete for capturing agent context, tool.execute.after for native image injection, and the config hook for automatic agent/prompt injection. The SSE connection lives inside the tool's execute() function, which is a regular async function that can do anything before returning a string. All of this happens transparently — agents just call get_feedback and get back your response.
See the OpenCode Plugin Guide for configuration, agent augmentation, and remote mode setup.
MCP Server (Universal)
For VS Code Copilot, Claude Desktop, or any MCP-compatible client — connect directly to the MCP endpoint.
Add to .vscode/mcp.json:
{
"servers": {
"tasksync": {
"url": "http://localhost:3011/mcp"
}
}
}
Or for OpenCode in MCP mode (opencode.json):
{
"mcp": {
"tasksync": {
"type": "remote",
"url": "http://localhost:3011/mcp"
}
}
}
MCP gives you the tasksync_get_feedback tool with full image support (ImageContent blocks). You'll need to provide the daemon agent prompt manually — see prompts/ for ready-to-use templates.
How It Works
- Agent calls
get_feedbackand blocks - You see the waiting session in the web UI at
http://localhost:3456 - Type your feedback, attach images if needed, and submit
- Agent receives your response and continues working
- Repeat — the agent stays in a feedback loop until you tell it to stop
Feedback UI
The web dashboard at http://localhost:3456 provides:
- Multi-session support — Route feedback to different agent sessions
- Image attachments — Paste, drag-drop, or file-pick images
- Markdown toolbar — Bold, italic, code, lists, headings with keyboard shortcuts
- Live status — See which sessions are waiting, idle, or have queued feedback
- Desktop notifications — Get alerted when an agent is waiting
- Remote mode toggle — Enable/disable Telegram notifications per session
- Session management — Rename, prune stale, delete sessions
See Feedback UI Guide for details.
Remote Mode (Telegram)
Get notified on Telegram when agents are waiting for feedback, and reply directly from your phone.
Setup
- Create a Telegram bot via @BotFather and copy the token
- Set the token:
# .env file (recommended) TASKSYNC_TELEGRAM_BOT_TOKEN=your-bot-token-here # or CLI flag npx tasksync-mcp-http --telegram-token=your-bot-token-here - Start the server, then send
/startto your bot in Telegram - Enable remote mode per session via the web UI toggle
When an agent calls get_feedback, you'll receive a Telegram message with the agent's question and quick-reply buttons (Approve / Reject / Continue / Stop / Pause). Reply with text or tap a button — the feedback goes straight to the agent.
One bot per server. Telegram only allows one process to poll for updates per bot token. If you run multiple TaskSync servers, create a separate bot for each via @BotFather.
CLI Options
| Option | Default | Description |
|---|---|---|
--port=<n> |
3011 |
MCP Streamable HTTP port |
--ui-port=<n> |
3456 |
Feedback UI port |
--telegram-token=<tok> |
— | Telegram bot token for remote notifications |
--heartbeat |
off | Enable legacy [WAITING] timeout mode |
--timeout=<ms> |
3600000 |
Wait timeout (only with --heartbeat) |
--no-ui |
off | Disable embedded feedback UI |
Environment Variables
| Variable | Description |
|---|---|
TASKSYNC_TELEGRAM_BOT_TOKEN |
Telegram bot token (alternative to CLI flag) |
TASKSYNC_TELEGRAM_CHAT_IDS |
Pre-authorized Telegram chat IDs (comma-separated) |
TASKSYNC_LOG_LEVEL |
debug, info, warn, error (default: info) |
TASKSYNC_LOG_FILE |
Path to log file (default: stderr) |
A .env file in the project root is loaded automatically. See .env.example for all options.
Updating
Server
npm install -g tasksync-mcp-http@latest
If you run via npx, just restart — npx fetches the latest version automatically.
OpenCode Plugin
OpenCode caches npm plugins locally in ~/.cache/opencode/. Restarting OpenCode does not fetch the latest version — it reuses the cache. To update:
rm -rf ~/.cache/opencode/packages/opencode-tasksync@latest
Then restart OpenCode. It will re-install the latest version on startup.
Building from Source
git clone https://github.com/vikrant82/tasksync-mcp.git
cd tasksync-mcp
npm install && npm run build
node dist/index.js
Documentation
- Architecture — Current module map and Excalidraw architecture diagram
- OpenCode Plugin Guide — Plugin setup, configuration, agent augmentation, remote mode
- API Specification — MCP tools, HTTP endpoints, REST API
- Session Workflow — Session lifecycle and routing
- Feedback UI Guide — Web UI features and controls
- Examples — Curl commands, client configs, multi-session flows
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。