zubo 0.1.20 → 0.1.22

package/migrations/024_personal_features.sql

@@ -0,0 +1,96 @@
+-- Personal agent features: todos, notes, preferences, topics, follow-ups
+
+CREATE TABLE IF NOT EXISTS todos (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  title TEXT NOT NULL,
+  description TEXT,
+  priority TEXT NOT NULL DEFAULT 'medium' CHECK(priority IN ('low', 'medium', 'high', 'urgent')),
+  status TEXT NOT NULL DEFAULT 'pending' CHECK(status IN ('pending', 'in_progress', 'done')),
+  due_date TEXT,
+  tags TEXT NOT NULL DEFAULT '[]',
+  created_at TEXT NOT NULL DEFAULT (datetime('now')),
+  completed_at TEXT
+);
+
+CREATE INDEX IF NOT EXISTS idx_todos_status ON todos(status);
+CREATE INDEX IF NOT EXISTS idx_todos_priority ON todos(priority);
+CREATE INDEX IF NOT EXISTS idx_todos_due ON todos(due_date);
+
+CREATE TABLE IF NOT EXISTS notes (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  title TEXT NOT NULL,
+  content TEXT NOT NULL,
+  tags TEXT NOT NULL DEFAULT '[]',
+  pinned INTEGER NOT NULL DEFAULT 0,
+  created_at TEXT NOT NULL DEFAULT (datetime('now')),
+  updated_at TEXT NOT NULL DEFAULT (datetime('now'))
+);
+
+CREATE VIRTUAL TABLE IF NOT EXISTS notes_fts USING fts5(
+  title,
+  content,
+  tags,
+  content='notes',
+  content_rowid='id'
+);
+
+CREATE TRIGGER IF NOT EXISTS notes_ai AFTER INSERT ON notes BEGIN
+  INSERT INTO notes_fts(rowid, title, content, tags)
+  VALUES (new.id, new.title, new.content, new.tags);
+END;
+
+CREATE TRIGGER IF NOT EXISTS notes_ad AFTER DELETE ON notes BEGIN
+  INSERT INTO notes_fts(notes_fts, rowid, title, content, tags)
+  VALUES ('delete', old.id, old.title, old.content, old.tags);
+END;
+
+CREATE TRIGGER IF NOT EXISTS notes_au AFTER UPDATE ON notes BEGIN
+  INSERT INTO notes_fts(notes_fts, rowid, title, content, tags)
+  VALUES ('delete', old.id, old.title, old.content, old.tags);
+  INSERT INTO notes_fts(rowid, title, content, tags)
+  VALUES (new.id, new.title, new.content, new.tags);
+END;
+
+-- Upgrade user_preferences from migration 008 (simple key/value)
+-- to the expanded schema with category, confidence, source
+CREATE TABLE IF NOT EXISTS _user_preferences_new (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  category TEXT NOT NULL DEFAULT 'general',
+  key TEXT NOT NULL,
+  value TEXT NOT NULL,
+  confidence REAL NOT NULL DEFAULT 0.8,
+  source TEXT NOT NULL DEFAULT 'inferred',
+  created_at TEXT NOT NULL DEFAULT (datetime('now')),
+  updated_at TEXT NOT NULL DEFAULT (datetime('now')),
+  UNIQUE(category, key)
+);
+
+INSERT OR IGNORE INTO _user_preferences_new (key, value, updated_at)
+  SELECT key, value, updated_at FROM user_preferences;
+
+DROP TABLE IF EXISTS user_preferences;
+
+ALTER TABLE _user_preferences_new RENAME TO user_preferences;
+
+CREATE INDEX IF NOT EXISTS idx_prefs_category ON user_preferences(category);
+
+CREATE TABLE IF NOT EXISTS conversation_topics (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  name TEXT NOT NULL UNIQUE,
+  description TEXT,
+  status TEXT NOT NULL DEFAULT 'active' CHECK(status IN ('active', 'archived')),
+  last_message_at TEXT NOT NULL DEFAULT (datetime('now')),
+  created_at TEXT NOT NULL DEFAULT (datetime('now'))
+);
+
+CREATE TABLE IF NOT EXISTS follow_ups (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  context TEXT NOT NULL,
+  message TEXT NOT NULL,
+  follow_up_at TEXT NOT NULL,
+  status TEXT NOT NULL DEFAULT 'pending' CHECK(status IN ('pending', 'sent', 'cancelled')),
+  created_at TEXT NOT NULL DEFAULT (datetime('now'))
+);
+
+CREATE INDEX IF NOT EXISTS idx_followups_status ON follow_ups(status);
+CREATE INDEX IF NOT EXISTS idx_followups_time ON follow_ups(follow_up_at);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zubo",
-  "version": "0.1.20",
+  "version": "0.1.22",
   "description": "Your AI agent that never forgets. Persistent memory, 25+ tools, 7 channels, 11+ LLM providers — runs entirely on your machine.",
   "license": "MIT",
   "author": "thomaskanze",

package/site/docs/agents.html

@@ -89,11 +89,11 @@
       <p>By default, Zubo operates as a single agent that handles all messages across every connected channel using a unified session identified as "owner." This default agent has access to all registered tools &mdash; both built-in tools and any user-installed skills &mdash; and its personality and behavior are defined by the system prompt stored at <code>~/.zubo/workspace/SYSTEM.md</code>.</p>
       <p>For many use cases, the default agent is all you need. It can search the web, manage your calendar, write code, read and write memory, and use any skill you install. Custom agents become valuable when you want to restrict tool access, provide specialized instructions, or build multi-step workflows.</p>
 
-      <h2>Custom System Prompt</h2>
+      <h2>Personality</h2>
       <p>The system prompt defines your agent's personality, rules, and background knowledge. There are two ways to customize it:</p>
       <ul>
         <li><strong>Edit the file directly</strong> &mdash; Open <code>~/.zubo/workspace/SYSTEM.md</code> in any text editor and modify it.</li>
-        <li><strong>Use the dashboard</strong> &mdash; Navigate to the System Prompt panel in the web dashboard and edit it there. Changes are saved to <code>SYSTEM.md</code> automatically.</li>
+        <li><strong>Use the dashboard</strong> &mdash; Navigate to the Personality panel in the web dashboard and edit it there. Changes are saved to <code>SYSTEM.md</code> automatically.</li>
       </ul>
       <p>Here is an example <code>SYSTEM.md</code> that defines a personalized assistant:</p>
 <pre><code># System Prompt

package/site/docs/api.html

@@ -200,7 +200,7 @@ file: &lt;document&gt;</code></pre>
   "Status": "running"
 }</code></pre>
 
-      <h3>System Prompt</h3>
+      <h3>Personality</h3>
 <pre><code>GET /api/dashboard/system</code></pre>
       <p>Retrieve the current system prompt.</p>
 <pre><code>PUT /api/dashboard/system
@@ -583,7 +583,7 @@ Content-Type: application/json
 <pre><code>GET /api/dashboard/channel-status</code></pre>
       <p>Returns the configuration and connection status for each channel (webchat, Telegram, Discord, Slack, WhatsApp, Signal). Each channel reports whether it is configured and whether it is currently enabled.</p>
 
-      <h3>Secrets Management</h3>
+      <h3>API Keys Management</h3>
 <pre><code>GET /api/dashboard/secrets</code></pre>
       <p>List all stored secrets. Values are masked in the response for security.</p>
 <pre><code>GET /api/dashboard/secrets/:name</code></pre>

package/site/docs/index.html

@@ -61,6 +61,7 @@
           <a href="/docs/agents">Agents &amp; Workflows</a>
           <a href="/docs/memory">Memory System</a>
           <a href="/docs/skills">Skills</a>
+          <a href="/docs/skills#personal-features">Personal Features</a>
         </div>
       </div>
       <div class="docs-sidebar-section">
@@ -69,7 +70,7 @@
           <a href="/docs/conversations">Conversation History</a>
           <a href="/docs/webhooks">Webhooks</a>
           <a href="/docs/workflows">Visual Workflows</a>
-          <a href="/docs/marketplace">MCP Marketplace</a>
+          <a href="/docs/marketplace">Extensions Marketplace</a>
         </div>
       </div>
       <div class="docs-sidebar-section">
@@ -154,6 +155,15 @@
         <li><strong>Skill sandboxing</strong> &mdash; user-installed skills run in isolated subprocesses with configurable timeouts, preventing runaway code from affecting the main process.</li>
       </ul>
 
+      <h3>Personal Features</h3>
+      <ul>
+        <li><strong>Todos</strong> &mdash; add, list, complete, update, and remove tasks with priorities (<code>low</code> / <code>medium</code> / <code>high</code>), due dates, and tags. A full task manager inside your agent.</li>
+        <li><strong>Notes</strong> &mdash; save, search (FTS5), list, update, delete, and pin notes with tags. Fast full-text search across all your notes.</li>
+        <li><strong>Preferences</strong> &mdash; store user preferences as category/key/value pairs. Preferences are automatically injected into the system prompt so the agent always respects your settings.</li>
+        <li><strong>Topics</strong> &mdash; create, switch, list, and archive conversation topics. Each topic scopes a separate session, keeping context focused when you juggle multiple projects.</li>
+        <li><strong>Follow-ups</strong> &mdash; schedule proactive follow-up messages at a specific time or delay. Uses one-shot cron jobs that fire once and auto-delete.</li>
+      </ul>
+
       <h3>Agents</h3>
       <ul>
         <li><strong>Custom sub-agents</strong> with focused system prompts, restricted tool access, and specialized behavior. Define a &ldquo;code-reviewer&rdquo; agent that only has access to file and git tools, or a &ldquo;researcher&rdquo; agent that only has web search.</li>
@@ -300,10 +310,10 @@ docker compose up -d</code></pre>
 
       <p>The wizard walks you through 4 steps:</p>
       <ul>
-        <li><strong>Step 1: LLM Provider</strong> &mdash; choose from 15 supported providers (Anthropic, OpenAI, Ollama, Groq, Together, OpenRouter, DeepSeek, xAI, MiniMax, Fireworks, Cerebras, LM Studio, Claude Code, Codex, or any OpenAI-compatible endpoint) and enter your API key. Optionally configure a fallback provider for automatic failover.</li>
+        <li><strong>Step 1: AI Provider</strong> &mdash; choose from 15 supported providers (Anthropic, OpenAI, Ollama, Groq, Together, OpenRouter, DeepSeek, xAI, MiniMax, Fireworks, Cerebras, LM Studio, Claude Code, Codex, or any OpenAI-compatible endpoint) and enter your API key. Optionally configure a fallback provider for automatic failover.</li>
         <li><strong>Step 2: Channels</strong> &mdash; enable any combination of Telegram, Discord, Slack, WhatsApp, Signal, and Email. Enter the required tokens and credentials for each. Web Chat is always on and requires no configuration.</li>
         <li><strong>Step 3: Personalization</strong> &mdash; set your agent's name and describe its personality. This shapes how Zubo talks to you across all channels.</li>
-        <li><strong>Step 4: Smart Routing</strong> &mdash; optionally configure a fast model (e.g., Groq) for simple queries. Smart routing automatically detects low-complexity messages and routes them to the cheaper, faster model, saving 50&ndash;80% on costs without sacrificing quality for complex tasks.</li>
+        <li><strong>Step 4: Smart Cost Savings</strong> &mdash; optionally configure a fast model (e.g., Groq) for simple queries. Smart routing automatically detects low-complexity messages and routes them to the cheaper, faster model, saving 50&ndash;80% on costs without sacrificing quality for complex tasks.</li>
       </ul>
       <p>The wizard also creates the <code>~/.zubo</code> directory and all required subdirectories, generates your <code>~/.zubo/config.json</code> file, and downloads the all-MiniLM-L6-v2 embedding model (~80 MB) for local semantic memory.</p>
 
@@ -624,7 +634,7 @@ zubo start --daemon</code></pre>
         <li><strong>Use <code>zubo start --daemon</code></strong> for always-on operation. Zubo writes a PID file and rotates logs automatically.</li>
         <li><strong>Check <code>zubo status</code> and <code>zubo logs</code></strong> for troubleshooting. The status command shows uptime, memory usage, connected channels, and pending scheduled jobs.</li>
         <li><strong>Back up your data</strong> with <code>zubo export</code> for a full JSON export, or rely on the automatic daily SQLite backups in <code>~/.zubo/workspace/backups/</code>.</li>
-        <li><strong>Enable smart routing</strong> to automatically send simple queries to fast, cheap models. Set <code>smartRouting.enabled</code> to <code>true</code> and configure a <code>fastProvider</code> (e.g., Groq) alongside your primary. This can cut costs significantly.</li>
+        <li><strong>Enable smart cost savings</strong> to automatically send simple queries to fast, cheap models. Set <code>smartRouting.enabled</code> to <code>true</code> and configure a <code>fastProvider</code> (e.g., Groq) alongside your primary. This can cut costs significantly.</li>
         <li><strong>Set a budget</strong> to avoid surprise bills: <code>zubo config set budget.dailyLimit 5</code>. Cost tracking is always active in the dashboard under Analytics &rarr; Costs.</li>
         <li><strong>Configure failover providers</strong> so your agent stays available even if your primary LLM provider has an outage. For example, set Anthropic as primary and Ollama as failover for fully offline operation when the cloud is down.</li>
         <li><strong>Keep skills small and focused</strong> &mdash; one skill per task. This makes them easier to test, share, and debug.</li>
@@ -640,11 +650,12 @@ zubo start --daemon</code></pre>
         <li><a href="/docs/agents"><strong>Agents &amp; Workflows</strong></a> &mdash; learn how to create custom sub-agents with focused system prompts and restricted tools, and build multi-agent pipelines with dependency resolution and parallel execution.</li>
         <li><a href="/docs/memory"><strong>Memory System</strong></a> &mdash; understand how semantic memory works, how to ingest documents, search your knowledge base, and tune the hybrid search weights.</li>
         <li><a href="/docs/skills"><strong>Skills</strong></a> &mdash; write, install, and share single-file TypeScript skills. Learn the skill manifest format, the sandbox environment, and the community registry.</li>
+        <li><a href="/docs/skills#personal-features"><strong>Personal Features</strong></a> &mdash; built-in tools for todos, notes, preferences, conversation topics, and scheduled follow-ups. Your personal productivity layer, stored locally.</li>
         <li><a href="/docs/channels"><strong>Channel Setup</strong></a> &mdash; step-by-step guides for configuring each channel: creating bots, obtaining tokens, setting up webhooks, and configuring allow-lists.</li>
         <li><a href="/docs/conversations"><strong>Conversation History</strong></a> &mdash; unified cross-channel history with FTS5 search, dashboard browsing, and API access for searching and analyzing past conversations across all channels.</li>
         <li><a href="/docs/webhooks"><strong>Webhooks</strong></a> &mdash; create webhook endpoints for GitHub, Stripe, CI/CD, and any external service. HMAC signature verification, prompt templates with <code>{{payload}}</code> substitution, and dashboard management.</li>
         <li><a href="/docs/workflows"><strong>Visual Workflows</strong></a> &mdash; build multi-step automations with the drag-and-drop workflow builder. Step types (tool, agent, condition, message, delay), triggers (manual, cron, webhook), and template variables.</li>
-        <li><a href="/docs/marketplace"><strong>MCP Marketplace</strong></a> &mdash; browse, install, and manage MCP servers from the official registry. One-click installation with automatic tool registration.</li>
+        <li><a href="/docs/marketplace"><strong>Extensions Marketplace</strong></a> &mdash; browse, install, and manage MCP servers from the official registry. One-click installation with automatic tool registration.</li>
         <li><a href="/docs/integrations"><strong>Integrations</strong></a> &mdash; connect Zubo to GitHub, Google Workspace, Notion, Linear, Jira, and more. <a href="/docs/integrations#oauth">OAuth 2.0 authentication</a> with automatic token refresh, API key setup, and usage examples.</li>
         <li><a href="/docs/security"><strong>Security &amp; Auth</strong></a> &mdash; harden your Zubo instance: API key management, tool permission levels, confirmation tokens, rate limiting, file access restrictions, and network security.</li>
         <li><a href="/docs/api"><strong>API Reference</strong></a> &mdash; complete HTTP API documentation for programmatic access: endpoints, request/response formats, authentication, and WebSocket streaming.</li>

package/site/docs/integrations.html

@@ -101,7 +101,7 @@
       <p>There are three ways to connect a service:</p>
       <ol>
         <li><strong>Chat:</strong> Tell Zubo directly &mdash; for example, <code>"Connect GitHub with token ghp_abc123"</code>. Zubo will store the secret and install the skill pack automatically.</li>
-        <li><strong>Dashboard:</strong> Navigate to Settings &rarr; Secrets &rarr; Add Secret. Enter the secret name and value, then Zubo detects the associated integration and installs the skills.</li>
+        <li><strong>Dashboard:</strong> Navigate to Settings &rarr; API Keys. Enter the secret name and value, then Zubo detects the associated integration and installs the skills.</li>
         <li><strong>CLI:</strong> Run <code>zubo start</code>, then use the <code>connect_service</code> tool programmatically to provide the credentials.</li>
       </ol>
       <p>When you connect a service, Zubo performs the following steps:</p>
@@ -384,11 +384,11 @@ zubo mcp-serve</code></pre>
         </tbody>
       </table>
 
-      <h2 id="managing-secrets">Managing Secrets</h2>
+      <h2 id="managing-secrets">Managing API Keys</h2>
       <p>All integration secrets are managed through the same unified secret system.</p>
       <h3>Dashboard</h3>
       <ul>
-        <li>Navigate to Settings &rarr; Secrets &amp; API Keys</li>
+        <li>Navigate to Settings &rarr; API Keys</li>
         <li>Values are displayed as <code>&bull;&bull;&bull;&bull;&bull;&bull;&bull;&bull;</code> by default</li>
         <li>Click <strong>&ldquo;Reveal&rdquo;</strong> to show the actual secret value</li>
         <li>Click <strong>&ldquo;Edit&rdquo;</strong> to update a secret with a new value</li>

package/site/docs/marketplace.html

@@ -3,18 +3,18 @@
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title>MCP Marketplace — Zubo Docs</title>
+  <title>Extensions Marketplace — Zubo Docs</title>
   <meta name="description" content="Browse, install, and manage MCP servers from the built-in marketplace. Extend Zubo with community-built tools, one-click installs, and automatic configuration.">
   <meta name="theme-color" content="#060608">
   <link rel="canonical" href="https://zubo.bot/docs/marketplace">
-  <meta property="og:title" content="MCP Marketplace — Zubo Docs">
+  <meta property="og:title" content="Extensions Marketplace — Zubo Docs">
   <meta property="og:description" content="Browse, install, and manage MCP servers from the built-in marketplace. Extend Zubo with community-built tools, one-click installs, and automatic configuration.">
   <meta property="og:type" content="website">
   <meta property="og:url" content="https://zubo.bot/docs/marketplace">
   <meta property="og:image" content="https://zubo.bot/og-image.png">
   <meta property="og:site_name" content="Zubo">
   <meta name="twitter:card" content="summary_large_image">
-  <meta name="twitter:title" content="MCP Marketplace — Zubo Docs">
+  <meta name="twitter:title" content="Extensions Marketplace — Zubo Docs">
   <meta name="twitter:description" content="Browse, install, and manage MCP servers from the built-in marketplace. Extend Zubo with community-built tools, one-click installs, and automatic configuration.">
   <meta name="twitter:image" content="https://zubo.bot/og-image.png">
   <meta name="twitter:creator" content="@thomaskanze">
@@ -67,7 +67,7 @@
           <a href="/docs/conversations">Conversation History</a>
           <a href="/docs/webhooks">Webhooks</a>
           <a href="/docs/workflows">Visual Workflows</a>
-          <a href="/docs/marketplace" class="active">MCP Marketplace</a>
+          <a href="/docs/marketplace" class="active">Extensions Marketplace</a>
         </div>
       </div>
       <div class="docs-sidebar-section">
@@ -89,12 +89,12 @@
     </aside>
 
     <main class="docs-content">
-      <div class="docs-breadcrumb"><a href="/">Home</a><span>/</span><a href="/docs/">Docs</a><span>/</span>MCP Marketplace</div>
+      <div class="docs-breadcrumb"><a href="/">Home</a><span>/</span><a href="/docs/">Docs</a><span>/</span>Extensions Marketplace</div>
 
-      <h1>MCP Marketplace</h1>
+      <h1>Extensions Marketplace</h1>
 
       <p>
-        The MCP Marketplace lets you browse, install, and manage MCP (Model Context Protocol) servers from the official registry directly through the Zubo dashboard or API. Instead of manually configuring MCP server commands and arguments, you can discover servers from the community, install them with one click, and have their tools automatically registered in Zubo.
+        The Extensions Marketplace lets you browse, install, and manage MCP (Model Context Protocol) servers from the official registry directly through the Zubo dashboard or API. Instead of manually configuring MCP server commands and arguments, you can discover servers from the community, install them with one click, and have their tools automatically registered in Zubo.
       </p>
 
       <!-- ================================================================ -->
@@ -107,7 +107,7 @@
       <h3>Via the Dashboard</h3>
 
       <ol>
-        <li>Open the web dashboard and navigate to the <strong>MCP</strong> panel in the sidebar.</li>
+        <li>Open the web dashboard and navigate to the <strong>Extensions</strong> panel in the sidebar.</li>
         <li>Click the <strong>Marketplace</strong> tab to view the available servers from the registry.</li>
         <li>Use the search bar to filter servers by name or keyword (e.g., "filesystem", "database", "github").</li>
         <li>Each server card shows the name, description, author, tool count, and install status.</li>
@@ -291,7 +291,7 @@ Content-Type: application/json
     "itemListElement": [
       { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://zubo.bot/" },
       { "@type": "ListItem", "position": 2, "name": "Docs", "item": "https://zubo.bot/docs/" },
-      { "@type": "ListItem", "position": 3, "name": "MCP Marketplace", "item": "https://zubo.bot/docs/marketplace" }
+      { "@type": "ListItem", "position": 3, "name": "Extensions Marketplace", "item": "https://zubo.bot/docs/marketplace" }
     ]
   }
   </script>

package/site/docs/security.html

@@ -169,18 +169,18 @@
 
       <h2 id="secret-management">Secret Management</h2>
       <p>Secrets (API keys, tokens, passwords) are stored securely in the local SQLite <code>secrets</code> table. The agent can use secrets by name but <strong>never sees their actual values</strong> in conversation context.</p>
-      <h3>Storing Secrets</h3>
+      <h3>Storing API Keys</h3>
       <p>There are three ways to store a secret:</p>
       <ul>
         <li><strong>Chat:</strong> Tell Zubo directly &mdash; <code>"Store my GitHub token: ghp_abc123xyz"</code></li>
         <li><strong>Tool:</strong> The <code>secret_set</code> tool can be called programmatically</li>
-        <li><strong>Dashboard:</strong> Navigate to Settings &rarr; Secrets and use the form</li>
+        <li><strong>Dashboard:</strong> Navigate to Settings &rarr; API Keys and use the form</li>
       </ul>
-      <h3>Accessing Secrets in Skills</h3>
+      <h3>Accessing API Keys in Skills</h3>
       <p>User-installed skills can access secrets via environment variables:</p>
 <pre><code>const token = process.env.ZUBO_SECRET_GITHUB_TOKEN;</code></pre>
       <p>Only secrets explicitly declared in the skill manifest are passed to the skill process.</p>
-      <h3>Managing Secrets</h3>
+      <h3>Managing API Keys</h3>
       <ul>
         <li><strong>Dashboard:</strong> View masked values (<code>&bull;&bull;&bull;&bull;&bull;&bull;&bull;&bull;</code>), click &ldquo;Reveal&rdquo; to show the actual value, click &ldquo;Edit&rdquo; to update, or &ldquo;Delete&rdquo; to remove</li>
         <li><strong>Naming:</strong> Secret names must match the pattern <code>[a-z0-9_]+</code> (lowercase alphanumeric and underscores only)</li>

package/site/docs/skills.html

@@ -65,6 +65,7 @@
           <a href="/docs/agents">Agents &amp; Workflows</a>
           <a href="/docs/memory">Memory System</a>
           <a href="/docs/skills" class="active">Skills</a>
+          <a href="/docs/skills#personal-features">Personal Features</a>
         </div>
       </div>
       <div class="docs-sidebar-section">
@@ -162,7 +163,7 @@ export default async function (input: Record&lt;string, unknown&gt;): Promise&lt
         <li><strong>Cannot import from Zubo internals</strong> &mdash; skills run in a sandboxed subprocess and have no access to Zubo's core modules, database, or session state</li>
       </ul>
 
-      <h2>Accessing Secrets</h2>
+      <h2>Accessing API Keys</h2>
       <p>Skills often need API keys or credentials to call external services. Zubo provides a secure way to pass secrets to skill handlers via environment variables:</p>
 <pre><code>export default async function (input: Record&lt;string, unknown&gt;): Promise&lt;string&gt; {
   const apiKey = process.env.ZUBO_SECRET_WEATHER_API_KEY;
@@ -295,10 +296,116 @@ zubo publish my_skill     # Publish your skill to the registry</code></pre>
           <tr><td><code>image_generate</code></td><td>Generate images using AI (DALL-E, etc.)</td><td>auto</td></tr>
           <tr><td><code>webhook_manage</code></td><td>Create, list, or remove incoming webhooks</td><td>auto</td></tr>
           <tr><td><code>oauth_manage</code></td><td>Manage OAuth provider connections</td><td>auto</td></tr>
+          <tr><td><code>todos</code></td><td>Add, list, complete, update, and remove tasks with priorities, due dates, and tags</td><td>auto</td></tr>
+          <tr><td><code>notes</code></td><td>Save, search (FTS5), list, update, delete, and pin notes with tags</td><td>auto</td></tr>
+          <tr><td><code>preferences</code></td><td>Set, get, list, and remove user preferences (injected into system prompt)</td><td>auto</td></tr>
+          <tr><td><code>topics</code></td><td>Create, switch, list, and archive conversation topics</td><td>auto</td></tr>
+          <tr><td><code>follow_ups</code></td><td>Schedule, list, and cancel proactive follow-up messages</td><td>auto</td></tr>
         </tbody>
       </table>
       <p>Tools marked <strong>confirm</strong> require user confirmation before execution. Tools marked <strong>auto</strong> run immediately without prompting.</p>
 
+      <h2 id="personal-features">Personal Features</h2>
+      <p>Built-in tools for personal productivity &mdash; todos, notes, preferences, conversation topics, and scheduled follow-ups. These run in the main process (not sandboxed) and store data in your local SQLite database.</p>
+
+      <h3><code>todos</code></h3>
+      <p>A full task manager built into your agent. Add tasks, set priorities and due dates, tag them for organization, and check them off when done.</p>
+      <table>
+        <thead>
+          <tr><th>Action</th><th>Description</th></tr>
+        </thead>
+        <tbody>
+          <tr><td><code>add</code></td><td>Create a new task with an optional priority (<code>low</code>, <code>medium</code>, <code>high</code>), due date, and tags.</td></tr>
+          <tr><td><code>list</code></td><td>List tasks, optionally filtered by status, priority, tag, or due date.</td></tr>
+          <tr><td><code>complete</code></td><td>Mark a task as done by ID.</td></tr>
+          <tr><td><code>update</code></td><td>Update a task's text, priority, due date, or tags.</td></tr>
+          <tr><td><code>remove</code></td><td>Delete a task by ID.</td></tr>
+        </tbody>
+      </table>
+      <p><strong>Key parameters:</strong> <code>text</code> (string), <code>priority</code> (<code>"low"</code> | <code>"medium"</code> | <code>"high"</code>), <code>due</code> (date string), <code>tags</code> (comma-separated), <code>id</code> (task ID for update/complete/remove).</p>
+      <p><strong>Example:</strong></p>
+<pre><code>"Add a todo: finish the API docs, high priority, due Friday, tag: work"
+"Show my todos tagged work"
+"Complete todo #3"</code></pre>
+
+      <h3><code>notes</code></h3>
+      <p>Save, search, and organize notes with full-text search (FTS5). Pin important notes so they surface first.</p>
+      <table>
+        <thead>
+          <tr><th>Action</th><th>Description</th></tr>
+        </thead>
+        <tbody>
+          <tr><td><code>save</code></td><td>Create a new note with optional title, tags, and pinned status.</td></tr>
+          <tr><td><code>search</code></td><td>Full-text search across all notes using FTS5.</td></tr>
+          <tr><td><code>list</code></td><td>List all notes, optionally filtered by tag or pinned status.</td></tr>
+          <tr><td><code>update</code></td><td>Update a note's content, title, tags, or pinned status.</td></tr>
+          <tr><td><code>delete</code></td><td>Delete a note by ID.</td></tr>
+          <tr><td><code>pin</code></td><td>Toggle the pinned status of a note.</td></tr>
+        </tbody>
+      </table>
+      <p><strong>Key parameters:</strong> <code>title</code> (string), <code>content</code> (string), <code>tags</code> (comma-separated), <code>pinned</code> (boolean), <code>query</code> (search string), <code>id</code> (note ID).</p>
+      <p><strong>Example:</strong></p>
+<pre><code>"Save a note: meeting with design team moved to Thursday 2pm, tag: meetings"
+"Search my notes for API design"
+"Pin note #5"</code></pre>
+
+      <h3><code>preferences</code></h3>
+      <p>Store user preferences as category/key/value pairs. Preferences are automatically injected into the system prompt so the agent always knows your settings.</p>
+      <table>
+        <thead>
+          <tr><th>Action</th><th>Description</th></tr>
+        </thead>
+        <tbody>
+          <tr><td><code>set</code></td><td>Set a preference value for a given category and key.</td></tr>
+          <tr><td><code>get</code></td><td>Retrieve a specific preference by category and key.</td></tr>
+          <tr><td><code>list</code></td><td>List all preferences, optionally filtered by category.</td></tr>
+          <tr><td><code>remove</code></td><td>Delete a preference by category and key.</td></tr>
+        </tbody>
+      </table>
+      <p><strong>Key parameters:</strong> <code>category</code> (string, e.g. <code>"display"</code>, <code>"communication"</code>, <code>"coding"</code>), <code>key</code> (string), <code>value</code> (string).</p>
+      <p><strong>Example:</strong></p>
+<pre><code>"Set my preference: coding/language = TypeScript"
+"What are my communication preferences?"
+"Remove preference coding/editor"</code></pre>
+
+      <h3><code>topics</code></h3>
+      <p>Organize conversations into named topics. Each topic scopes a separate session, so context stays focused and you can switch between projects easily.</p>
+      <table>
+        <thead>
+          <tr><th>Action</th><th>Description</th></tr>
+        </thead>
+        <tbody>
+          <tr><td><code>create</code></td><td>Create a new topic with a name and optional description.</td></tr>
+          <tr><td><code>switch</code></td><td>Switch the active conversation to a different topic.</td></tr>
+          <tr><td><code>list</code></td><td>List all topics, including archived ones.</td></tr>
+          <tr><td><code>archive</code></td><td>Archive a topic to keep things tidy without deleting history.</td></tr>
+        </tbody>
+      </table>
+      <p><strong>Key parameters:</strong> <code>name</code> (string), <code>description</code> (string), <code>id</code> (topic ID for switch/archive).</p>
+      <p><strong>Example:</strong></p>
+<pre><code>"Create a topic called 'Website Redesign'"
+"Switch to the API project topic"
+"List my topics"
+"Archive the old marketing topic"</code></pre>
+
+      <h3><code>follow_ups</code></h3>
+      <p>Schedule proactive follow-up messages that Zubo sends to you at a specified time. Uses one-shot cron jobs under the hood &mdash; the job fires once and auto-deletes.</p>
+      <table>
+        <thead>
+          <tr><th>Action</th><th>Description</th></tr>
+        </thead>
+        <tbody>
+          <tr><td><code>schedule</code></td><td>Schedule a follow-up message for a specific time or delay.</td></tr>
+          <tr><td><code>list</code></td><td>List all pending follow-ups.</td></tr>
+          <tr><td><code>cancel</code></td><td>Cancel a scheduled follow-up by ID.</td></tr>
+        </tbody>
+      </table>
+      <p><strong>Key parameters:</strong> <code>message</code> (string &mdash; what Zubo should say), <code>time</code> (date/time string or natural language like <code>"in 2 hours"</code>, <code>"tomorrow at 9am"</code>), <code>id</code> (follow-up ID for cancel).</p>
+      <p><strong>Example:</strong></p>
+<pre><code>"Follow up with me tomorrow at 10am about the deployment"
+"List my pending follow-ups"
+"Cancel follow-up #2"</code></pre>
+
       <h2>Legacy Format (SKILL.md)</h2>
       <p>Earlier versions of Zubo used a Markdown-based skill definition file called <code>SKILL.md</code>. This format is still fully supported for backward compatibility:</p>
 <pre><code># weather

package/site/index.html

@@ -4,18 +4,18 @@
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   <title>Zubo — Your AI Agent. Your Machine. Your Rules.</title>
-  <meta name="description" content="Open-source AI agent that runs on your machine. One command to install, one file to configure. Persistent memory, 25+ tools, 7 messaging channels, 12+ LLM providers. MCP compatible. Zero complexity.">
+  <meta name="description" content="Open-source AI agent that runs on your machine. One command to install, one file to configure. Persistent memory, 25+ tools, 7 messaging channels, 12+ AI providers. Extension compatible. Zero complexity.">
   <meta name="theme-color" content="#060608">
   <link rel="canonical" href="https://zubo.bot/">
   <meta property="og:title" content="Zubo — Your AI Agent. Your Machine. Your Rules.">
-  <meta property="og:description" content="Open-source AI agent that runs on your machine. Persistent memory, 25+ tools, works across Telegram, Discord, Slack, WhatsApp, Email, and more. MCP compatible. One install, zero cloud.">
+  <meta property="og:description" content="Open-source AI agent that runs on your machine. Persistent memory, 25+ tools, works across Telegram, Discord, Slack, WhatsApp, Email, and more. Extension compatible. One install, zero cloud.">
   <meta property="og:type" content="website">
   <meta property="og:url" content="https://zubo.bot/">
   <meta property="og:image" content="https://zubo.bot/og-image.png">
   <meta property="og:site_name" content="Zubo">
   <meta name="twitter:card" content="summary_large_image">
   <meta name="twitter:title" content="Zubo — Your AI Agent. Your Machine. Your Rules.">
-  <meta name="twitter:description" content="Open-source AI agent that runs on your machine. Persistent memory, 25+ tools, works across Telegram, Discord, Slack, WhatsApp, Email, and more. MCP compatible. One install, zero cloud.">
+  <meta name="twitter:description" content="Open-source AI agent that runs on your machine. Persistent memory, 25+ tools, works across Telegram, Discord, Slack, WhatsApp, Email, and more. Extension compatible. One install, zero cloud.">
   <meta name="twitter:image" content="https://zubo.bot/og-image.png">
   <meta name="twitter:creator" content="@thomaskanze">
   <link rel="preconnect" href="https://fonts.googleapis.com">
@@ -264,7 +264,7 @@
             <svg width="28" height="28" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"><path d="M14.7 6.3a1 1 0 0 0 0 1.4l1.6 1.6a1 1 0 0 0 1.4 0l3.77-3.77a6 6 0 0 1-7.94 7.94l-6.91 6.91a2.12 2.12 0 0 1-3-3l6.91-6.91a6 6 0 0 1 7.94-7.94l-3.76 3.76z"/></svg>
           </div>
           <h3>25+ Smart Tools</h3>
-          <p>Web search, file operations, code interpreter, image generation, APIs, webhooks, and more. Knowledge graph memory, MCP support, and sub-agent delegation for complex tasks.</p>
+          <p>Web search, file operations, code interpreter, image generation, APIs, webhooks, and more. Knowledge graph memory, extension support, and sub-agent delegation for complex tasks.</p>
         </div>
 
         <div class="bento-card tilt-card" data-feature="privacy">
@@ -300,7 +300,15 @@
           <p>Build your own tools in TypeScript and share them with the community. A sandboxed skill system with scoped secrets, hot-reload, and a public registry.</p>
         </div>
 
-        <div class="bento-card bento-lg tilt-card" data-feature="llm">
+        <div class="bento-card tilt-card" data-feature="personal">
+          <div class="bento-icon">
+            <svg width="28" height="28" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"><path d="M9 11l3 3L22 4"/><path d="M21 12v7a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V5a2 2 0 0 1 2-2h11"/></svg>
+          </div>
+          <h3>Personal Features</h3>
+          <p>Built-in todos, notes, preferences, conversation topics, and scheduled follow-ups. Your personal productivity layer, stored locally and always in context.</p>
+        </div>
+
+        <div class="bento-card tilt-card" data-feature="llm">
           <div class="bento-icon">
             <svg width="28" height="28" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"><path d="M21 16V8a2 2 0 0 0-1-1.73l-7-4a2 2 0 0 0-2 0l-7 4A2 2 0 0 0 3 8v8a2 2 0 0 0 1 1.73l7 4a2 2 0 0 0 2 0l7-4A2 2 0 0 0 21 16z"/><polyline points="7.5 4.21 12 6.81 16.5 4.21"/><polyline points="7.5 19.79 7.5 14.6 3 12"/><polyline points="21 12 16.5 14.6 16.5 19.79"/><polyline points="3.27 6.96 12 12.01 20.73 6.96"/><line x1="12" y1="22.08" x2="12" y2="12"/></svg>
           </div>

package/site/install.sh

@@ -29,7 +29,9 @@ ARCH="$(uname -m)"
 case "$OS" in
   Linux*)  PLATFORM="linux" ;;
   Darwin*) PLATFORM="darwin" ;;
-  *)       fail "Unsupported OS: $OS. Zubo supports macOS and Linux." ;;
+  MINGW*|MSYS*|CYGWIN*)
+           fail "Windows detected. Use WSL (Windows Subsystem for Linux) to run Zubo:\n\n  ${DIM}wsl --install${RESET}\n  Then run this installer inside WSL." ;;
+  *)       fail "Unsupported OS: $OS. Zubo supports macOS, Linux, and Windows (via WSL)." ;;
 esac
 
 case "$ARCH" in
@@ -45,7 +47,7 @@ if command -v bun &>/dev/null; then
   BUN_VERSION=$(bun --version 2>/dev/null || echo "unknown")
   ok "Bun already installed (v${BUN_VERSION})"
 else
-  info "Installing Bun runtime..."
+  info "Installing Bun (a fast JavaScript runtime Zubo needs)..."
   curl -fsSL https://bun.sh/install | bash
 
   # Source the updated profile so bun is on PATH
@@ -55,7 +57,7 @@ else
   if command -v bun &>/dev/null; then
     ok "Bun installed (v$(bun --version))"
   else
-    fail "Bun installation failed. Install manually: https://bun.sh"
+    fail "Bun installation failed. Visit https://bun.sh for manual install instructions."
   fi
 fi
 
@@ -78,9 +80,13 @@ else
   # Bun global bin might not be on PATH yet
   ZUBO_BIN="${HOME}/.bun/bin/zubo"
   if [ -f "$ZUBO_BIN" ]; then
-    warn "Zubo installed but not on PATH. Add this to your shell profile:"
+    warn "Zubo installed but your terminal can't find it yet."
     echo ""
-    echo -e "  ${DIM}export PATH=\"\$HOME/.bun/bin:\$PATH\"${RESET}"
+    echo -e "  Run this command, then restart your terminal:"
+    echo ""
+    echo -e "  ${BOLD}echo 'export PATH=\"\$HOME/.bun/bin:\$PATH\"' >> ~/.bashrc && source ~/.bashrc${RESET}"
+    echo ""
+    echo -e "  ${DIM}(On macOS with zsh, use ~/.zshrc instead of ~/.bashrc)${RESET}"
     echo ""
   else
     fail "Zubo binary not found after install"

package/src/agent/context.ts

@@ -7,12 +7,12 @@ export interface AgentContext {
   messages: LlmMessage[];
 }
 
-export function assembleContext(
+export async function assembleContext(
   sessionId: string,
   maxTurns: number = 50,
   memories: string = ""
-): AgentContext {
+): Promise<AgentContext> {
   const messages = loadSession(sessionId, maxTurns);
-  const system = buildSystemPrompt(memories);
+  const system = await buildSystemPrompt(memories);
   return { system, messages };
 }

package/src/agent/loop.ts

@@ -79,7 +79,7 @@ async function prepareLoop(
   // Assemble context (uses static import — no dynamic import overhead)
   const ctx = options.systemPromptOverride
     ? { system: options.systemPromptOverride, messages: loadSession(sessionId, 50) }
-    : assembleContext(sessionId, 50, fullMemories);
+    : await assembleContext(sessionId, 50, fullMemories);
 
   const messages = compactMessages(ctx.messages, llm.contextWindow);