obol-ai 0.2.1 → 0.2.2

package/README.md

@@ -30,7 +30,7 @@ OBOL is an AI agent that evolves its own personality, rewrites its own code, tes
 
 It starts as a blank slate. Through conversation it learns who you are, develops a personality shaped by your interactions, and builds operational knowledge about how to work with you. Every 100 exchanges it reflects on who it's becoming, refactors its own scripts, writes tests, fixes regressions, and builds you new tools based on patterns it spots in your conversations — scripts, commands, or full web apps deployed to Vercel. Over months it becomes an agent that's uniquely yours. No two OBOL instances are alike.
 
-One bot, multiple users. Each allowed Telegram user gets a fully isolated context — their own personality, memory, evolution cycle, workspace, and first-run experience. User A's personality drift, scripts, and memories never leak into User B's. Everything runs in a single process with shared API credentials.
+One bot, multiple users. Each allowed Telegram user gets a fully isolated context — their own personality, memory, evolution cycle, and workspace. User A's personality drift, scripts, and memories never leak into User B's. Everything runs in a single process with shared API credentials.
 
 Under the hood: Node.js + Telegram + Claude + Supabase pgvector. No framework, no plugins, no config to maintain. It backs up its brain to GitHub and hardens your server automatically.
 
@@ -156,7 +156,7 @@ Refined voice, updated your project list, cleaned up 2 unused scripts.
 
 ```
 Day 1:   obol init → obol start → first conversation
-         → OBOL asks 2-3 questions, writes SOUL.md + USER.md
+         → OBOL responds naturally from message one
          → post-setup hardens your VPS automatically
 
 Day 2:   Every 5 messages → Haiku extracts facts to vector memory
@@ -224,8 +224,7 @@ Router: ctx.from.id → tenant context
 | GitHub token | Evolution cycle + state |
 | Vercel token | Scripts, tests, commands, apps |
 | VPS hardening | Workspace directory (`~/.obol/users/{id}/`) |
-| Process manager (pm2) | First-run onboarding experience |
-| | GitHub backup (per-user repo dir) |
+| Process manager (pm2) | GitHub backup (per-user repo dir) |
 
 ### Tenant routing
 
@@ -244,11 +243,13 @@ When users store secrets via the `pass` encrypted store, each user gets their ow
 | Shared bot credentials | `obol/` | `obol/anthropic-key` |
 | User secrets | `obol/users/{id}/` | `obol/users/206639616/gmail-key` |
 
+Users manage their own secrets via Telegram: `/secret set <key> <value>` (message auto-deleted for safety), `/secret list`, `/secret remove <key>`. The agent can also read/write secrets via tools for scripts that need API keys at runtime.
+
 ### Adding users
 
 1. Add their Telegram user ID to `allowedUsers` in `~/.obol/config.json` (or run `obol config`)
 2. Restart the bot
-3. They message the bot → OBOL creates their workspace, runs first-run onboarding, and writes their own SOUL.md + USER.md
+3. They message the bot → OBOL creates their workspace and starts responding immediately. Personality files are created during their first evolution cycle.
 
 Each new user starts fresh. Their bot evolves independently from every other user's.
 
@@ -339,7 +340,7 @@ For Telegram user IDs, OBOL auto-detects by checking who messaged the bot. Just
 
 ### First Conversation
 
-Send your first message. OBOL introduces itself, asks 2-3 questions, then writes its own SOUL.md and USER.md. After that, it hardens your VPS and reports progress directly in the Telegram chat (Linux only — skipped on macOS/Windows):
+Send your first message. OBOL responds naturally — no onboarding flow, it works from message one. Personality files (SOUL.md, USER.md) are created during the first evolution cycle. After first boot, it hardens your VPS and reports progress directly in the Telegram chat (Linux only — skipped on macOS/Windows):
 
 | Task | What |
 |------|------|
@@ -445,11 +446,18 @@ Or edit `~/.obol/config.json` directly:
 ## Telegram Commands
 
 ```
-/new     — Fresh conversation
-/tasks   — Running background tasks
-/status  — Uptime and memory stats
-/backup  — Trigger GitHub backup
-/clean   — Audit workspace, remove rogue files, fix misplaced items
+/new        — Fresh conversation
+/memory     — Search or view memory stats
+/recent     — Last 10 memories
+/today      — Today's memories
+/tasks      — Running background tasks
+/status     — Bot status, uptime, evolution progress, traits
+/backup     — Trigger GitHub backup
+/clean      — Audit workspace, remove rogue files, fix misplaced items
+/traits     — View or adjust personality traits (0-100)
+/secret     — Manage per-user encrypted secrets
+/evolution  — Evolution progress
+/help       — Show available commands
 ```
 
 Everything else is natural conversation.
@@ -468,6 +476,7 @@ obol logs              # Tail logs (pm2 or log file fallback)
 obol status            # Status
 obol backup            # Manual backup
 obol upgrade           # Update to latest version
+obol delete            # Full VPS cleanup (removes all OBOL data)
 ```
 
 ## Directory Structure

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obol-ai",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Self-evolving AI assistant that learns, remembers, and acts on its own. Persistent vector memory, self-rewriting personality, proactive heartbeats.",
   "main": "src/index.js",
   "bin": {
@@ -29,7 +29,8 @@
     "grammy": "^1.35.0",
     "inquirer": "^8.2.6",
     "node-cron": "^3.0.3",
-    "open": "^8.4.2"
+    "open": "^8.4.2",
+    "pdfkit": "^0.17.2"
   },
   "engines": {
     "node": ">=18"

package/src/claude.js

@@ -215,8 +215,17 @@ Model: Use "sonnet" for most things (chat, simple questions, quick tasks, single
       history.shift();
       history.shift();
     }
-    if (history.length > 0 && history[0].role !== 'user') {
-      history.shift();
+    while (history.length > 0) {
+      const first = history[0];
+      if (first.role !== 'user') {
+        history.shift();
+        continue;
+      }
+      if (Array.isArray(first.content) && first.content.some(b => b.type === 'tool_result')) {
+        history.shift();
+        continue;
+      }
+      break;
     }
 
     // Add user message with memory context
@@ -310,7 +319,13 @@ Model: Use "sonnet" for most things (chat, simple questions, quick tasks, single
     }
   }
 
-  return { chat, client, reloadPersonality, clearHistory };
+  function injectHistory(chatId, role, content) {
+    if (!histories.has(chatId)) histories.set(chatId, []);
+    const history = histories.get(chatId);
+    history.push({ role, content });
+  }
+
+  return { chat, client, reloadPersonality, clearHistory, injectHistory };
 }
 
 function buildSystemPrompt(personality, userDir, opts = {}) {
@@ -392,6 +407,7 @@ Use the \`store_secret\`, \`read_secret\`, and \`list_secrets\` tools for all us
 These store secrets under the prefix \`${passPrefix}/\` in pass (or JSON fallback).
 
 Users can also manage secrets via Telegram: \`/secret set <key> <value>\` (message auto-deleted), \`/secret list\`, \`/secret remove <key>\`.
+Since users can store secrets via /secret outside your conversation, ALWAYS call \`list_secrets\` to check what's available before telling the user their credentials aren't stored.
 
 Shared bot credentials live under \`obol/\` — do NOT touch or re-create these:
 \`obol/anthropic-key\`, \`obol/telegram-token\`, \`obol/supabase-url\`, \`obol/supabase-key\`, \`obol/github-token\`, \`obol/vercel-token\`
@@ -589,6 +605,19 @@ function buildTools(memory, opts = {}) {
     },
   });
 
+  tools.push({
+    name: 'send_file',
+    description: 'Send a file to the user via Telegram (PDF, image, document, etc). Use after generating files the user requested.',
+    input_schema: {
+      type: 'object',
+      properties: {
+        path: { type: 'string', description: 'Path to the file to send' },
+        caption: { type: 'string', description: 'Optional caption for the file' },
+      },
+      required: ['path'],
+    },
+  });
+
   if (opts.bridgeEnabled) {
     const { buildBridgeTool, buildBridgeTellTool } = require('./bridge');
     tools.push(buildBridgeTool());
@@ -791,6 +820,18 @@ async function executeToolCall(toolUse, memory, context = {}) {
         return keys.join('\n');
       }
 
+      case 'send_file': {
+        const filePath = userDir ? resolveUserPath(input.path, userDir) : input.path;
+        if (!fs.existsSync(filePath)) return `File not found: ${filePath}`;
+        const telegramCtx = context.ctx;
+        if (!telegramCtx) return 'Cannot send files in this context.';
+        const { InputFile } = require('grammy');
+        await telegramCtx.replyWithDocument(new InputFile(filePath), {
+          caption: input.caption || undefined,
+        });
+        return `Sent: ${path.basename(filePath)}`;
+      }
+
       case 'bridge_ask': {
         const { bridgeAsk } = require('./bridge');
         return await bridgeAsk(input.question, context.userId, context.config, context._notifyFn, input.partner_id);

package/src/defaults/AGENTS.md

@@ -41,6 +41,9 @@ Use these tools instead of `exec` for storing/reading secrets — they bypass th
 
 Users can also manage secrets via Telegram: `/secret set <key> <value>` (message auto-deleted), `/secret list`, `/secret remove <key>`.
 
+### Send File (`send_file`)
+Send a file back to the user via Telegram. Use after generating PDFs, images, documents, or any file the user requested.
+
 ### Bridge (`bridge_ask`, `bridge_tell`)
 Only available if bridge is enabled. Communicate with partner's AI agent.
 
@@ -98,6 +101,19 @@ Rules:
 - Temporary files go in /tmp
 - If unsure where something belongs, ask
 
+## Self-Extending
+
+You can give yourself new capabilities by writing scripts and running them. If the user asks for something you don't have a dedicated tool for (PDF generation, image manipulation, data processing, etc.):
+
+1. **Write a script** to `scripts/` using `write_file`
+2. **Install dependencies** if needed via `exec`: `pip3 install fpdf2` or `npm install --prefix . pdfkit`
+3. **Run the script** via `exec`: `python3 scripts/generate-pdf.py` or `node scripts/generate-pdf.js`
+4. **Send the result** to the user with `send_file`
+
+Don't tell the user you can't do something — create the capability, then use it.
+
+Pre-installed npm packages you can `require()` in Node scripts: `pdfkit`
+
 ## Scripts & Service Integrations
 
 When building scripts (Gmail, Notion, APIs, etc.), prefer **Python**:

package/src/telegram.js

@@ -254,6 +254,11 @@ function createBot(telegramConfig, config) {
         ctx.api.deleteMessage(ctx.chat.id, ctx.message.message_id).catch(() => {});
         credentials.storeSecret(userId, key, value);
         await ctx.reply(`🔑 Secret "${key}" stored securely.`);
+        const tenant = await getTenant(userId, config);
+        if (tenant.claude?.injectHistory) {
+          tenant.claude.injectHistory(ctx.chat.id, 'user', `[System: user stored secret "${key}" via /secret set]`);
+          tenant.claude.injectHistory(ctx.chat.id, 'assistant', `Noted — secret "${key}" is now stored.`);
+        }
       } catch (e) {
         await ctx.reply(`⚠️ ${e.message}`);
       }
@@ -264,6 +269,11 @@ function createBot(telegramConfig, config) {
       try {
         credentials.removeSecret(userId, args[1]);
         await ctx.reply(`🗑️ Secret "${args[1]}" removed.`);
+        const tenant = await getTenant(userId, config);
+        if (tenant.claude?.injectHistory) {
+          tenant.claude.injectHistory(ctx.chat.id, 'user', `[System: user removed secret "${args[1]}" via /secret remove]`);
+          tenant.claude.injectHistory(ctx.chat.id, 'assistant', `Noted — secret "${args[1]}" has been removed.`);
+        }
       } catch (e) {
         await ctx.reply(`⚠️ ${e.message}`);
       }