persistent-planning vs Agentic Task System (ATS)
persistent-planning is a plugin bundle for AI coding tools published by TheGlitchKing. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agentic Task System (ATS) is an MCP server published by renezander030. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  persistent-planning |  Agentic Task System (ATS) |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 3.0.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.18.0 Downloads/month (npm): 1 515 Downloads/week (npm): 314 Forks (GitHub): 3 Stars (GitHub): 16 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | persistent-planning | Agentic Task System (ATS) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 16 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@reneza/ats-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 10 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/theglitchking/persistent-planning | github.com/renezander030/agentic-task-system |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
persistent-planning
Transforms Claude Code into a Manus-style persistent planner using on-disk markdown files as working memory. Creates structured task directories with task_plan.md and notes.md that persist across sessions. Enables multi-step project tracking, progress visibility, and knowledge storage that survives context resets. Based on proven context engineering principles for long-horizon AI tasks.
Agentic Task System (ATS)
Persistent task context across TickTick, Notion, GitHub, Obsidian, Taskmaster and Beads
How to run each
persistent-planning As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install persistent-planning@claude-communityAgentic Task System (ATS) As a local MCP server: npm package
claude mcp add --env "ATS_ADAPTER=<YOUR_ATS_ADAPTER>" --transport stdio agentic-task-system -- npx -y @reneza/ats-mcpRequires: ATS_ADAPTER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of persistent-planning publish no settings it asks for, so we do not compare settings.
What it can do: persistent-planning · What it can do: Agentic Task System (ATS) · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.