What is Agentic Task System (ATS)?
ATS is an MCP server and CLI that gives your AI agent memory from the task system you already use — TickTick, Taskmaster, Beads, Obsidian, Notion, GitHub, Airtable, Google, or all at once via the composite adapter with Reciprocal Rank Fusion (RRF) retrieval. It is an adapter, not a migration — it makes your existing task app agent-native without re-homing any data.
How to use Agentic Task System (ATS)?
Install the CLI and an adapter globally (npm install -g @reneza/ats-cli @reneza/ats-adapter-ticktick), configure with ats config use ticktick, authenticate with ats auth login, then query with ats find "deployment runbook". For MCP clients, install @reneza/ats-mcp and set the ATS_ADAPTER environment variable; the binary (ats-mcp) works over stdio with Claude Code, Claude Desktop, Cursor, Windsurf, and OpenCode.
Key features of Agentic Task System (ATS)
- Two-way bus for agent reads and writes.
- First-fetch relevance via hybrid RRF-fused retrieval.
- Durable typed links (decision, depends-on, output, supersedes).
- Execution context: intent, lifecycle, security, ledger, promote, hierarchy.
- Bounded NDJSON events with recovery and dedup.
- Task graph linking structured nodes with proof and edges.
- Session-index handoff for durable task-linked summaries.
- Curated at write time using “trunk” themes.
Use cases of Agentic Task System (ATS)
- Give a coding agent persistent memory between sessions using your task app.
- Fuse retrieval across Notion, GitHub, and TickTick with one
ats find query.
- Hand off context (intent, links, lifecycle) from one agent to another in a fresh session.
- Manage a task backlog with dependency links and auto-computed next actions.
- Audit agent actions via the action ledger while keeping writes add-only.
评论