limbo-ai 1.20.0 → 1.20.2

package/README.md

@@ -80,17 +80,11 @@ There are two ways to connect: **talk to Limbo** (conversational, with its perso
 
 #### Telegram (recommended)
 
-Set `TELEGRAM_ENABLED=true` and `TELEGRAM_BOT_TOKEN` in `~/.limbo/.env`, then restart:
+During setup (`npx limbo-ai start`), the wizard will walk you through creating a Telegram bot via BotFather and pairing it. Message your bot and Limbo will respond — full agent with personality, memory logic, and vault tools.
 
-```sh
-npx limbo-ai start --reconfigure
-```
-
-Message your bot and Limbo will respond — full agent with personality, memory logic, and vault tools.
-
-#### ZeroClaw client
+#### ZeroClaw gateway
 
-Any ZeroClaw-compatible chat client can connect via WebSocket to:
+Any [ZeroClaw](https://github.com/zeroclaw-labs/zeroclaw)-compatible chat client can connect to:
 
 ```
 ws://localhost:18789
@@ -130,7 +124,6 @@ Managed automatically by `npx limbo-ai start`, stored in `~/.limbo/.env`.
 | `MODEL_NAME` | no | `claude-opus-4-6` | Model name (e.g. `claude-opus-4-6`, `claude-sonnet-4-6`, `gpt-5.4`) |
 | `TELEGRAM_ENABLED` | no | `false` | Enable Telegram bot integration |
 | `TELEGRAM_BOT_TOKEN` | no | — | Telegram bot token (required if `TELEGRAM_ENABLED=true`) |
-| `TELEGRAM_AUTO_PAIR_FIRST_DM` | no | `false` | Auto-approves the first Telegram DM sender and persists access (must opt-in explicitly) |
 
 > \* API keys are required only for `AUTH_MODE=api-key`. Subscription auth uses ZeroClaw auth profiles instead.
 
@@ -159,12 +152,12 @@ Full tool specs in `workspace/TOOLS.md`.
 │                                         │
 │  ┌─────────────┐    ┌────────────────┐  │
 │  │  ZeroClaw   │◄──►│  LLM (Claude   │  │
-│  │  Gateway    │    │  or OpenAI)    │  │
+│  │  daemon     │    │  or OpenAI)    │  │
 │  │  :18789     │    └────────┬───────┘  │
 │  └──────┬──────┘             │          │
 │         │           ┌────────▼───────┐  │
-│  Telegram Bot        │  MCP Server   │  │
-│         │           │  limbo-vault  │  │
+│  Telegram Bot       │  MCP Server    │  │
+│         │           │  limbo-vault   │  │
 │         │           └────────┬───────┘  │
 │         └────────────────────┤          │
 │                              ▼          │
@@ -173,8 +166,8 @@ Full tool specs in `workspace/TOOLS.md`.
 └─────────────────────────────────────────┘
 ```
 
-- **ZeroClaw** — lightweight Rust gateway that handles client connections, routes to the LLM, and integrates MCP tools
-- **MCP server** — Node.js server providing vault read/write tools
+- **ZeroClaw** — lightweight Rust runtime (~5MB RAM) that handles client connections, routes to the LLM, manages Telegram, and integrates MCP tools natively
+- **MCP server** — Node.js server providing vault read/write tools (spawned by ZeroClaw, no mcporter needed)
 - **Vault** — plain markdown files with YAML frontmatter, persisted in a named Docker volume
 - **Migrations** — lightweight Node.js migration runner for vault schema changes
 
@@ -212,7 +205,7 @@ VAULT_PATH=./dev-vault node index.js
 
 ```sh
 docker build -t limbo:dev .
-docker run --rm -e LLM_API_KEY=sk-ant-... -p 18789:18789 limbo:dev
+docker compose up -d
 ```
 
 ### Run migrations standalone

package/cli.js

@@ -159,9 +159,12 @@ function composeContent() {
       - ${VAULT_DIR}:/data/vault
       - limbo-zeroclaw-state:/home/limbo/.zeroclaw
     secrets:
-      - llm_api_key
-      - telegram_bot_token
-      - gateway_token
+      - source: llm_api_key
+        mode: 0444
+      - source: telegram_bot_token
+        mode: 0444
+      - source: gateway_token
+        mode: 0444
     env_file:
       - ${LIMBO_DIR}/.env
     environment:
@@ -179,10 +182,13 @@ function composeContent() {
 secrets:
   llm_api_key:
     file: ${SECRETS_DIR}/llm_api_key
+    mode: 0444
   telegram_bot_token:
     file: ${SECRETS_DIR}/telegram_bot_token
+    mode: 0444
   gateway_token:
     file: ${SECRETS_DIR}/gateway_token
+    mode: 0444
 
 volumes:
   limbo-data:
@@ -215,9 +221,12 @@ function composeContentHardened() {
       - ${VAULT_DIR}:/data/vault
       - limbo-zeroclaw-state:/home/limbo/.zeroclaw
     secrets:
-      - llm_api_key
-      - telegram_bot_token
-      - gateway_token
+      - source: llm_api_key
+        mode: 0444
+      - source: telegram_bot_token
+        mode: 0444
+      - source: gateway_token
+        mode: 0444
     env_file:
       - ${LIMBO_DIR}/.env
     environment:
@@ -266,10 +275,13 @@ networks:
 secrets:
   llm_api_key:
     file: ${SECRETS_DIR}/llm_api_key
+    mode: 0444
   telegram_bot_token:
     file: ${SECRETS_DIR}/telegram_bot_token
+    mode: 0444
   gateway_token:
     file: ${SECRETS_DIR}/gateway_token
+    mode: 0444
 
 volumes:
   limbo-data:
@@ -1599,19 +1611,10 @@ async function cmdStart() {
     tunnel = await createSetupTunnel(PORT);
   }
 
-  if (wizardUrl) {
-    printWizardUrl(wizardUrl, tunnel);
-  } else {
-    const fallbackUrl = `http://127.0.0.1:${PORT}`;
-    console.log(`
-  ${c.green}${c.bold}Limbo is starting.${c.reset}
-
-  Open: ${c.cyan}${c.bold}${fallbackUrl}${c.reset}
-  ${c.dim}(may take a few seconds to be ready)${c.reset}
-
-  Logs: ${c.dim}limbo logs${c.reset}
-`);
-  }
+  // Always show the wizard URL with tunnel/SSH info, even if we couldn't
+  // extract the token-authenticated URL from logs.
+  const displayUrl = wizardUrl || `http://127.0.0.1:${PORT}`;
+  printWizardUrl(displayUrl, tunnel);
 }
 
 // Shared path for headless, CLI-prompt, and existing-config routes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "limbo-ai",
-  "version": "1.20.0",
+  "version": "1.20.2",
   "description": "Your personal AI memory agent — install and manage Limbo via npx",
   "type": "commonjs",
   "bin": {