<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticktick on René Zander | AI Automation Consultant</title><link>https://renezander.com/tags/ticktick/</link><description>Recent content in Ticktick on René Zander | AI Automation Consultant</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 30 May 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://renezander.com/tags/ticktick/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent Memory From Your Task Manager: CLI + MCP, No Vector DB</title><link>https://renezander.com/guides/agent-memory-task-manager/</link><pubDate>Sat, 30 May 2026 09:00:00 +0200</pubDate><guid>https://renezander.com/guides/agent-memory-task-manager/</guid><description>&lt;p>Most &amp;ldquo;agent memory&amp;rdquo; projects ask you to build a &lt;em>new&lt;/em> store: a vector database, a bespoke framework, a fresh pile of markdown. It drifts from reality the moment you stop feeding it. But you already maintain a curated knowledge base by hand, every day: your task manager. Years of prioritized, deduplicated context, pre-filtered by the most reliable ranker there is, which is you.&lt;/p>
&lt;p>&lt;a href="https://github.com/renezander030/agentic-task-system">&lt;code>ats&lt;/code>&lt;/a> (Agentic Task System) makes that context agent-native without a migration. Keep the app you already live in, TickTick or an Obsidian vault today, and give your agent a fast, structured, two-way channel into it.&lt;/p></description></item></channel></rss>