volute 0.28.0 → 0.30.0

package/README.md

@@ -152,22 +152,32 @@ volute channel read discord:123456789 --mind atlas         # recent messages
 volute send discord:123456789 "hello" --mind atlas        # send a message
 ```
 
-## Schedules
+## Clock
 
-Cron-based scheduled messages — daily check-ins, periodic tasks, whatever you need.
+Schedules, timers, and sleep/wake cycles — a mind's daily rhythm.
 
 ```sh
-volute schedule add --mind atlas \
+# Recurring schedule
+volute clock add --mind atlas \
   --cron "0 9 * * *" \
   --message "good morning — write your daily log"
 
-volute schedule list --mind atlas
-volute schedule remove --mind atlas --id <schedule-id>
+# One-time timer
+volute clock add --mind atlas --in 30m --message "check on that task"
+
+# Sleep/wake
+volute clock sleep atlas --wake-at "2025-01-15T07:00:00Z"
+volute clock wake atlas
+
+# Status and management
+volute clock status --mind atlas
+volute clock list --mind atlas
+volute clock remove --mind atlas --id <schedule-id>
 ```
 
 ## Pages
 
-Publish a mind's `home/pages/` directory to the web via [volute.systems](https://volute.systems).
+Pages is a built-in extension that lets minds publish web content. HTML files in `home/public/pages/` are served locally and can be published to [volute.systems](https://volute.systems).
 
 ### Setup
 
@@ -179,20 +189,16 @@ volute systems register --name my-system
 volute systems login --key vp_...
 ```
 
-### Publishing
-
-```sh
-volute pages publish --mind atlas
-# Published 3 file(s) to https://my-system.volute.systems/~atlas/
-```
+### How it works
 
-The command uploads everything in the mind's `home/pages/` directory. Minds can publish their own pages since `VOLUTE_MIND` is set automatically.
-
-### Status & Logout
+- Place HTML files in a mind's `home/public/pages/` directory
+- Pages are served locally at `/ext/pages/public/<mindname>/`
+- The pages extension provides publish/status API endpoints at `/api/ext/pages/`
+- Minds learn how to publish via the bundled pages skill (auto-installed)
+- File changes are tracked by a watcher and shown in the web dashboard
 
 ```sh
-volute pages status --mind atlas   # show published URL, file count, last publish time
-volute systems logout                 # remove stored credentials
+volute systems logout   # remove stored credentials
 ```
 
 ## Environment variables
@@ -210,13 +216,102 @@ volute env remove API_KEY
 
 The daemon serves a web UI at `http://localhost:1618` (or whatever port you chose).
 
-- Real-time chat with full tool call visibility
+- Real-time chat with full tool call visibility and turn summaries
 - File browser and editor
 - Log streaming
 - Connector and schedule management
 - Variant listing and status
+- System settings: AI service config, system prompts, shared files, skills, user management
 - First user to register becomes admin
 
+## Extensions
+
+Extensions add UI sections, API routes, feed sources, and lifecycle hooks to Volute. Notes and Pages are built-in extensions; you can add your own.
+
+### Managing extensions
+
+```sh
+volute extension list                      # list loaded extensions
+volute extension install <npm-package>     # install from npm
+volute extension uninstall <npm-package>   # remove
+```
+
+After installing or uninstalling, restart the daemon (`volute restart`) to load changes.
+
+### Local extensions
+
+For extensions that don't need an npm package, place the code in `~/.volute/extensions/<name>/`:
+
+```
+~/.volute/extensions/my-extension/
+├── src/
+│   └── index.ts    # exports an ExtensionManifest (default export)
+└── package.json    # optional, for dependencies
+```
+
+Local extensions are auto-discovered on daemon start. The entry point can be `src/index.ts`, `src/index.js`, `index.ts`, or `index.js`.
+
+### Writing an extension
+
+Install the SDK:
+
+```sh
+npm install @volute/extensions hono
+```
+
+Create the manifest:
+
+```typescript
+import { createExtension } from "@volute/extensions";
+import { Hono } from "hono";
+
+export default createExtension({
+  id: "my-ext",
+  name: "My Extension",
+  version: "0.1.0",
+  description: "Does something useful",
+
+  // Required: authenticated API routes at /api/ext/my-ext/
+  routes: (ctx) =>
+    new Hono()
+      .get("/", (c) => c.json({ hello: "world" }))
+      .get("/feed", (c) =>
+        c.json([
+          {
+            id: "item-1",
+            title: "Example",
+            url: "/ext/my-ext/#/item-1",
+            date: new Date().toISOString(),
+            bodyHtml: "<p>An item</p>",
+          },
+        ]),
+      ),
+
+  // Optional: initialize a SQLite database for this extension
+  initDb: (db) => {
+    db.exec(`CREATE TABLE IF NOT EXISTS items (
+      id INTEGER PRIMARY KEY AUTOINCREMENT,
+      name TEXT NOT NULL
+    )`);
+  },
+
+  // Optional: UI configuration
+  ui: {
+    systemSections: [{ id: "items", label: "Items" }],
+    mindSections: [{ id: "items", label: "Items" }],
+    feedSource: { endpoint: "/api/ext/my-ext/feed" },
+  },
+});
+```
+
+The extension context (`ctx`) provides:
+- `ctx.db` — SQLite database (if `initDb` is declared)
+- `ctx.resolveUser(c)` — get the authenticated user from a Hono context
+- `ctx.getUser(id)` / `ctx.getUserByUsername(name)` — look up users
+- `ctx.publishActivity(event)` — emit activity events
+- `ctx.getMindDir(name)` — resolve a mind's directory path
+- `ctx.dataDir` — extension-specific data directory
+
 ## Upgrading minds
 
 When the Volute template updates, you can upgrade minds without touching their identity:
@@ -244,6 +339,20 @@ Two built-in templates:
 volute mind create atlas --template pi
 ```
 
+## AI Service
+
+Volute has an optional system-level AI service for features like automatic turn summaries. It uses [`@mariozechner/pi-ai`](https://github.com/nicepkg/pi) for multi-provider support — configure any combination of Anthropic, OpenAI, Google, GitHub Copilot, and others.
+
+Configure via the web dashboard (Settings → AI Service) or during `volute setup`. Each provider authenticates independently via API key, OAuth, or environment variables. After adding providers, select which models to enable — the system picks from your enabled list.
+
+When configured, each mind turn automatically gets a 1-2 sentence AI-generated summary (visible in history and the web UI). Without AI configured, summaries fall back to a deterministic format.
+
+## System Prompts
+
+Volute ships with default prompts for mind creation, system messages, and mind-owned templates. These can be customized via the web dashboard (Settings → Prompts) without modifying code.
+
+Customized prompts are stored in the database and override the built-in defaults. Each prompt shows its template variables and can be reset to the default at any time.
+
 ## Model configuration
 
 Set the model via `home/.config/volute.json` in the mind directory, or the `VOLUTE_MODEL` env var.

package/dist/{accept-666DIZX2.js → accept-E3PAH3QJ.js}

@@ -4,11 +4,11 @@ import {
 } from "./chunk-NAOW2CLO.js";
 import {
   daemonFetch
-} from "./chunk-JGFVMROS.js";
+} from "./chunk-EFVHR7KH.js";
 import {
   parseArgs
 } from "./chunk-D424ZQGI.js";
-import "./chunk-H7OZRFJB.js";
+import "./chunk-HHTXM4JT.js";
 import "./chunk-K3NQKI34.js";
 
 // src/commands/chat/accept.ts

package/dist/{activity-events-BBIEA2F4.js → activity-events-BKBPPUBP.js}

@@ -3,9 +3,9 @@ import {
   broadcast,
   publish,
   subscribe
-} from "./chunk-VIVMW2H2.js";
+} from "./chunk-P27RV5WM.js";
 import "./chunk-YUIHSKR6.js";
-import "./chunk-H7OZRFJB.js";
+import "./chunk-HHTXM4JT.js";
 import "./chunk-K3NQKI34.js";
 export {
   broadcast,

package/dist/ai-service-VAJT5UBS.js

@@ -0,0 +1,29 @@
+#!/usr/bin/env node
+import {
+  aiComplete,
+  getAiConfig,
+  getAvailableModels,
+  getConfiguredProviders,
+  getEnabledModels,
+  isAiConfigured,
+  removeAiConfig,
+  removeProviderConfig,
+  saveProviderConfig,
+  setEnabledModels
+} from "./chunk-NSBFETWP.js";
+import "./chunk-YUIHSKR6.js";
+import "./chunk-7D47T4RB.js";
+import "./chunk-HHTXM4JT.js";
+import "./chunk-K3NQKI34.js";
+export {
+  aiComplete,
+  getAiConfig,
+  getAvailableModels,
+  getConfiguredProviders,
+  getEnabledModels,
+  isAiConfigured,
+  removeAiConfig,
+  removeProviderConfig,
+  saveProviderConfig,
+  setEnabledModels
+};