agent-world 0.12.0 → 0.12.1

package/dist/server/sse-handler.d.ts

@@ -5,9 +5,10 @@
  *
  * Features:
  * - Sets up SSE response headers and connection
- * - Wires world event listeners (MESSAGE, SSE, SYSTEM, WORLD)
+ * - Wires world event listeners (MESSAGE, SSE, SYSTEM, WORLD, CRUD)
  * - Handles world activity state tracking (response-start, idle)
  * - Forwards tool events (tool-start, tool-result, tool-error, tool-progress) as SSE events
+ * - Forwards CRUD events so frontends can refresh world/agent state in real time
  * - Automatic stream completion when world becomes idle
  * - Timeout fallback (60s) if world never becomes idle
  * - Proper cleanup on client disconnect or stream end

package/dist/server/sse-handler.js

@@ -5,9 +5,10 @@
  *
  * Features:
  * - Sets up SSE response headers and connection
- * - Wires world event listeners (MESSAGE, SSE, SYSTEM, WORLD)
+ * - Wires world event listeners (MESSAGE, SSE, SYSTEM, WORLD, CRUD)
  * - Handles world activity state tracking (response-start, idle)
  * - Forwards tool events (tool-start, tool-result, tool-error, tool-progress) as SSE events
+ * - Forwards CRUD events so frontends can refresh world/agent state in real time
  * - Automatic stream completion when world becomes idle
  * - Timeout fallback (60s) if world never becomes idle
  * - Proper cleanup on client disconnect or stream end
@@ -211,6 +212,14 @@ export function createSSEHandler(req, res, world, context = 'sse', scopedChatId)
     };
     world.eventEmitter.on(EventType.SYSTEM, systemListener);
     listeners.set(EventType.SYSTEM, systemListener);
+    const crudListener = (eventData) => {
+        if (!isChatEventInScope(eventData?.chatId, true)) {
+            return;
+        }
+        sendSSE({ type: EventType.CRUD, data: eventData });
+    };
+    world.eventEmitter.on(EventType.CRUD, crudListener);
+    listeners.set(EventType.CRUD, crudListener);
     // Cleanup function to remove all listeners
     const cleanupListeners = () => {
         for (const [eventType, listener] of listeners.entries()) {

package/migrations/0000_init_base_schema.sql

@@ -0,0 +1,129 @@
+-- Migration: Initial base schema
+-- Version: 0
+-- Date: 2025-11-02
+--
+-- This is the base schema that creates the initial database structure.
+-- All subsequent migrations (0001-0009) build upon this foundation.
+--
+-- Base Tables:
+-- - worlds: Core world configuration (no LLM/chat columns yet)
+-- - agents: Agent configuration with LLM settings
+-- - agent_memory: Active conversation memory (no chat_id, message_id, reply_to_message_id yet)
+-- - memory_archives: Archive session metadata
+-- - archived_messages: Historical conversation content
+-- - archive_statistics: Usage analytics
+--
+-- Note: This is the PRE-MIGRATION state. Tables like world_chats, events, event_sequences
+-- and columns like chat_id, mcp_config, etc. are added by subsequent migrations.
+
+-- Create worlds table (base version without migration columns)
+CREATE TABLE IF NOT EXISTS worlds (
+  id TEXT PRIMARY KEY,
+  name TEXT NOT NULL,
+  description TEXT,
+  turn_limit INTEGER NOT NULL DEFAULT 5,
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
+);
+
+-- Create agents table (complete from start)
+CREATE TABLE IF NOT EXISTS agents (
+  id TEXT NOT NULL,
+  world_id TEXT NOT NULL,
+  name TEXT NOT NULL,
+  type TEXT NOT NULL,
+  status TEXT DEFAULT 'inactive',
+  provider TEXT NOT NULL,
+  model TEXT NOT NULL,
+  system_prompt TEXT,
+  temperature REAL,
+  max_tokens INTEGER,
+  llm_call_count INTEGER DEFAULT 0,
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  last_active TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  last_llm_call TIMESTAMP,
+  PRIMARY KEY (id, world_id),
+  FOREIGN KEY (world_id) REFERENCES worlds(id) ON DELETE CASCADE
+);
+
+-- Create agent_memory table (base version without chat columns)
+CREATE TABLE IF NOT EXISTS agent_memory (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  agent_id TEXT NOT NULL,
+  world_id TEXT NOT NULL,
+  role TEXT NOT NULL CHECK (role IN ('system', 'user', 'assistant')),
+  content TEXT NOT NULL,
+  sender TEXT,
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  FOREIGN KEY (agent_id, world_id) REFERENCES agents(id, world_id) ON DELETE CASCADE
+);
+
+-- Create memory archives system
+CREATE TABLE IF NOT EXISTS memory_archives (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  agent_id TEXT NOT NULL,
+  world_id TEXT NOT NULL,
+  session_name TEXT,
+  archive_reason TEXT,
+  message_count INTEGER NOT NULL DEFAULT 0,
+  start_time TIMESTAMP,
+  end_time TIMESTAMP,
+  participants TEXT,
+  tags TEXT,
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  FOREIGN KEY (agent_id, world_id) REFERENCES agents(id, world_id) ON DELETE CASCADE
+);
+
+CREATE TABLE IF NOT EXISTS archived_messages (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  archive_id INTEGER NOT NULL,
+  agent_id TEXT NOT NULL,
+  world_id TEXT NOT NULL,
+  role TEXT NOT NULL CHECK (role IN ('system', 'user', 'assistant')),
+  content TEXT NOT NULL,
+  sender TEXT,
+  original_timestamp TIMESTAMP,
+  FOREIGN KEY (archive_id) REFERENCES memory_archives(id) ON DELETE CASCADE,
+  FOREIGN KEY (agent_id, world_id) REFERENCES agents(id, world_id) ON DELETE CASCADE
+);
+
+CREATE TABLE IF NOT EXISTS archive_statistics (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  agent_id TEXT NOT NULL,
+  world_id TEXT NOT NULL,
+  total_archives INTEGER DEFAULT 0,
+  total_messages INTEGER DEFAULT 0,
+  average_session_length REAL DEFAULT 0,
+  most_active_agent TEXT,
+  archive_frequency TEXT,
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  FOREIGN KEY (agent_id, world_id) REFERENCES agents(id, world_id) ON DELETE CASCADE
+);
+
+-- Create base indexes
+CREATE INDEX IF NOT EXISTS idx_agents_world_id ON agents(world_id);
+CREATE INDEX IF NOT EXISTS idx_agents_status ON agents(status);
+CREATE INDEX IF NOT EXISTS idx_agent_memory_agent_world ON agent_memory(agent_id, world_id);
+CREATE INDEX IF NOT EXISTS idx_memory_archives_agent_world ON memory_archives(agent_id, world_id);
+CREATE INDEX IF NOT EXISTS idx_archived_messages_archive_id ON archived_messages(archive_id);
+CREATE INDEX IF NOT EXISTS idx_archive_statistics_agent_world ON archive_statistics(agent_id, world_id);
+
+-- Create triggers for automatic timestamp updates
+CREATE TRIGGER IF NOT EXISTS worlds_updated_at
+AFTER UPDATE ON worlds
+BEGIN
+  UPDATE worlds SET updated_at = CURRENT_TIMESTAMP WHERE id = NEW.id;
+END;
+
+CREATE TRIGGER IF NOT EXISTS agents_last_active
+AFTER UPDATE ON agents
+BEGIN
+  UPDATE agents SET last_active = CURRENT_TIMESTAMP WHERE id = NEW.id AND world_id = NEW.world_id;
+END;
+
+CREATE TRIGGER IF NOT EXISTS archive_statistics_updated_at
+AFTER UPDATE ON archive_statistics
+BEGIN
+  UPDATE archive_statistics SET updated_at = CURRENT_TIMESTAMP WHERE id = NEW.id;
+END;

package/migrations/0001_add_chat_id.sql

@@ -0,0 +1,12 @@
+-- Migration: Add chat_id to agent_memory for chat session tracking
+-- Version: 1
+-- Date: 2025-08-01
+--
+-- This migration adds the chat_id column to the agent_memory table to enable
+-- chat session management and message grouping by conversation context.
+
+ALTER TABLE agent_memory ADD COLUMN chat_id TEXT;
+
+CREATE INDEX
+IF NOT EXISTS idx_agent_memory_chat_id ON agent_memory
+(chat_id);

package/migrations/0002_add_llm_config.sql

@@ -0,0 +1,9 @@
+-- Migration: Add LLM provider and model configuration to worlds
+-- Version: 2
+-- Date: 2025-09-15
+--
+-- This migration adds chat_llm_provider and chat_llm_model columns to the worlds
+-- table, enabling per-world LLM configuration for chat interactions.
+
+ALTER TABLE worlds ADD COLUMN chat_llm_provider TEXT;
+ALTER TABLE worlds ADD COLUMN chat_llm_model TEXT;

package/migrations/0003_add_current_chat_id.sql

@@ -0,0 +1,8 @@
+-- Migration: Add current_chat_id to worlds for active chat tracking
+-- Version: 3
+-- Date: 2025-09-20
+--
+-- This migration adds the current_chat_id column to the worlds table to track
+-- which chat session is currently active in each world.
+
+ALTER TABLE worlds ADD COLUMN current_chat_id TEXT;

package/migrations/0004_add_mcp_config.sql

@@ -0,0 +1,8 @@
+-- Migration: Add MCP (Model Context Protocol) configuration to worlds
+-- Version: 4
+-- Date: 2025-10-10
+--
+-- This migration adds the mcp_config column to the worlds table to store
+-- Model Context Protocol server configurations as JSON.
+
+ALTER TABLE worlds ADD COLUMN mcp_config TEXT;

package/migrations/0005_add_message_id.sql

@@ -0,0 +1,12 @@
+-- Migration: Add message_id to agent_memory for message identification
+-- Version: 5
+-- Date: 2025-10-21
+--
+-- This migration adds the message_id column to the agent_memory table to enable
+-- unique identification of messages for features like message editing and threading.
+
+ALTER TABLE agent_memory ADD COLUMN message_id TEXT;
+
+CREATE INDEX
+IF NOT EXISTS idx_agent_memory_message_id ON agent_memory
+(message_id);

package/migrations/0006_add_reply_to_message_id.sql

@@ -0,0 +1,12 @@
+-- Migration: Add reply_to_message_id for message threading support
+-- Version: 6
+-- Date: 2025-10-25
+--
+-- This migration adds the reply_to_message_id column to the agent_memory table
+-- to enable message threading and conversation context tracking.
+
+ALTER TABLE agent_memory ADD COLUMN reply_to_message_id TEXT;
+
+CREATE INDEX
+IF NOT EXISTS idx_agent_memory_reply_to_message_id ON agent_memory
+(reply_to_message_id);

package/migrations/0007_create_world_chats.sql

@@ -0,0 +1,35 @@
+-- Migration: Create world_chats table for chat session management
+-- Version: 7
+-- Date: 2025-10-28
+--
+-- This migration creates the world_chats table to manage chat sessions within worlds,
+-- including metadata like name, description, message count, and tags.
+
+CREATE TABLE
+IF NOT EXISTS world_chats
+(
+  id TEXT PRIMARY KEY,
+  world_id TEXT NOT NULL,
+  name TEXT NOT NULL,
+  description TEXT,
+  message_count INTEGER DEFAULT 0,
+  tags TEXT,
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  FOREIGN KEY
+(world_id) REFERENCES worlds
+(id) ON
+DELETE CASCADE
+);
+
+CREATE INDEX
+IF NOT EXISTS idx_world_chats_world_id ON world_chats
+(world_id);
+
+CREATE TRIGGER
+IF NOT EXISTS world_chats_updated_at
+AFTER
+UPDATE ON world_chats
+BEGIN
+  UPDATE world_chats SET updated_at = CURRENT_TIMESTAMP WHERE id = NEW.id;
+END;

package/migrations/0008_create_events_table.sql

@@ -0,0 +1,78 @@
+-- Migration: Create events table for persistent event storage
+-- Version: 8
+-- Date: 2025-10-30
+--
+-- This migration creates the events table to store world emitter events with proper
+-- foreign key relationships and cascade delete behavior.
+--
+-- Table Design:
+-- - id: Text primary key (UUID format)
+-- - world_id: Foreign key to worlds table with CASCADE delete
+-- - chat_id: Foreign key to world_chats table with CASCADE delete (nullable)
+-- - seq: Sequence number for ordering within a world/chat (nullable, auto-incremented per world/chat)
+-- - type: Event type (message, sse, tool, system, etc.)
+-- - payload: JSON column for event data (uses JSON1 extension)
+-- - meta: JSON column for metadata like timestamp, sender, etc.
+-- - created_at: Timestamp of event creation
+--
+-- Indexes:
+-- - Composite index on (world_id, chat_id, created_at) for efficient time-based queries
+-- - Composite index on (world_id, chat_id, seq) for efficient sequence-based queries
+--
+-- Cascade Delete Behavior:
+-- - When a world is deleted, all events for that world are automatically deleted
+-- - When a chat is deleted, all events for that chat are automatically deleted
+-- - Foreign keys enforce referential integrity
+
+-- Create events table
+CREATE TABLE
+IF NOT EXISTS events
+(
+  id TEXT PRIMARY KEY,
+  world_id TEXT NOT NULL,
+  chat_id TEXT,
+  seq INTEGER,
+  type TEXT NOT NULL,
+  payload TEXT NOT NULL,  -- JSON data stored as text (JSON1 extension)
+  meta TEXT,              -- JSON metadata stored as text
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  
+  -- Foreign key constraints with CASCADE delete
+  -- When a world is deleted, all its events are deleted
+  FOREIGN KEY
+(world_id) REFERENCES worlds
+(id) ON
+DELETE CASCADE,
+  
+  -- When a chat is deleted, all its events are deleted
+  -- Note: This uses a conditional foreign key - events with NULL chat_id won't be constrained
+  FOREIGN KEY (chat_id)
+REFERENCES world_chats
+(id) ON
+DELETE CASCADE
+);
+
+-- Create indexes for efficient queries
+-- Index for time-based queries within a world/chat context
+CREATE INDEX
+IF NOT EXISTS idx_events_world_chat_time 
+  ON events
+(world_id, chat_id, created_at);
+
+-- Index for sequence-based queries within a world/chat context
+CREATE INDEX
+IF NOT EXISTS idx_events_world_chat_seq 
+  ON events
+(world_id, chat_id, seq);
+
+-- Index for event type queries
+CREATE INDEX
+IF NOT EXISTS idx_events_type 
+  ON events
+(type);
+
+-- Index for world_id alone for efficient world-level queries
+CREATE INDEX
+IF NOT EXISTS idx_events_world_id 
+  ON events
+(world_id);

package/migrations/0009_add_event_sequences.sql

@@ -0,0 +1,40 @@
+-- Migration: Add auto-incrementing sequence numbers to events
+-- Version: 9
+-- Date: 2025-11-06 (Updated)
+--
+-- This migration ensures that the seq column in events table auto-increments
+-- within each world_id/chat_id context using MAX(seq) + 1 approach.
+--
+-- Approach:
+-- - The seq column already exists in the events table (created in 0008)
+-- - No separate sequence tracking table is needed
+-- - Applications will use: COALESCE((SELECT MAX(seq) FROM events WHERE ...), 0) + 1
+-- - Transaction isolation ensures no race conditions
+--
+-- Backfill Strategy:
+-- - Assign sequence numbers to existing events based on creation time
+-- - Uses ROW_NUMBER() partitioned by world_id and chat_id
+-- - Orders by created_at to maintain chronological sequence
+
+-- Backfill existing events with sequence numbers if they have NULL seq
+-- This handles migration of existing data
+-- Note: SQLite requires a CTE for window functions in UPDATE
+WITH
+  numbered_events
+  AS
+  (
+    SELECT
+      rowid,
+      ROW_NUMBER() OVER (
+      PARTITION BY world_id, 
+                   CASE WHEN chat_id IS NULL THEN '' ELSE chat_id END
+      ORDER BY created_at ASC
+    ) as new_seq
+    FROM events
+    WHERE seq IS NULL
+  )
+UPDATE events 
+SET seq = (SELECT new_seq
+FROM numbered_events
+WHERE numbered_events.rowid = events.rowid)
+WHERE seq IS NULL;

package/migrations/0010_add_tool_call_fields.sql

@@ -0,0 +1,27 @@
+-- Migration: Add tool call fields for approval message persistence
+-- Version: 10
+-- Date: 2025-11-05
+--
+-- This migration adds support for storing tool call information in agent memory,
+-- which is essential for persisting approval request/response messages.
+--
+-- Changes:
+-- - Add tool_calls column (TEXT) to store JSON array of tool call objects
+-- - Add tool_call_id column (TEXT) to store tool call identifier for tool responses
+--
+-- Usage:
+-- - tool_calls: JSON serialized array for assistant messages with function calls
+--   Example: [{"id":"call_123","type":"function","function":{"name":"approve","arguments":"{}"}}]
+-- - tool_call_id: String identifier for tool role messages responding to a tool call
+--   Example: "approval_abc123"
+--
+-- These fields enable:
+-- - Persistence of approval request messages (role='assistant' with tool_calls)
+-- - Persistence of approval response messages (role='tool' with tool_call_id)
+-- - Full reconstruction of approval conversation flows after page refresh
+
+-- Add tool_calls column for storing JSON array of tool call objects
+ALTER TABLE agent_memory ADD COLUMN tool_calls TEXT;
+
+-- Add tool_call_id column for tool response messages
+ALTER TABLE agent_memory ADD COLUMN tool_call_id TEXT;

package/migrations/0011_add_event_metadata_indexes.sql

@@ -0,0 +1,79 @@
+-- Migration: Add indexes on JSON metadata fields for fast filtering
+-- Version: 11
+-- Date: 2025-11-07
+--
+-- This migration adds indexes on commonly queried JSON metadata fields to improve
+-- performance of event filtering operations. SQLite's JSON1 extension allows indexing
+-- on json_extract() expressions.
+--
+-- Indexed Fields:
+-- - ownerAgentIds: Array of agent IDs that have this event in memory
+-- - recipientAgentId: Intended recipient agent ID
+-- - messageDirection: Message flow direction (outgoing/incoming/broadcast)
+-- - isMemoryOnly: Flag for messages saved but not triggering response
+-- - isCrossAgentMessage: Flag for agent-to-agent communication
+-- - threadRootId: Root message ID for threading queries
+-- - hasToolCalls: Flag for messages containing tool calls
+--
+-- Performance Impact:
+-- - Significantly improves filtering queries on metadata fields
+-- - Composite index optimizes common query patterns (world + chat + owner)
+-- - Uses SQLite JSON1 extension (built-in since SQLite 3.38.0)
+
+-- Index on ownerAgentIds array (for agent filtering)
+-- Note: Array search requires LIKE operator with pattern %"agentId"%
+CREATE INDEX
+IF NOT EXISTS idx_events_owner_agents 
+  ON events
+(json_extract
+(meta, '$.ownerAgentIds'));
+
+-- Index on recipientAgentId (for recipient filtering)
+CREATE INDEX
+IF NOT EXISTS idx_events_recipient_agent 
+  ON events
+(json_extract
+(meta, '$.recipientAgentId'));
+
+-- Index on messageDirection (for direction filtering)
+CREATE INDEX
+IF NOT EXISTS idx_events_message_direction 
+  ON events
+(json_extract
+(meta, '$.messageDirection'));
+
+-- Index on isMemoryOnly flag (for memory-only message filtering)
+CREATE INDEX
+IF NOT EXISTS idx_events_memory_only 
+  ON events
+(json_extract
+(meta, '$.isMemoryOnly'));
+
+-- Index on isCrossAgentMessage flag (for cross-agent message filtering)
+CREATE INDEX
+IF NOT EXISTS idx_events_cross_agent 
+  ON events
+(json_extract
+(meta, '$.isCrossAgentMessage'));
+
+-- Index on threadRootId (for thread queries)
+CREATE INDEX
+IF NOT EXISTS idx_events_thread_root 
+  ON events
+(json_extract
+(meta, '$.threadRootId'));
+
+-- Index on hasToolCalls flag (for tool call filtering)
+CREATE INDEX
+IF NOT EXISTS idx_events_has_tool_calls 
+  ON events
+(json_extract
+(meta, '$.hasToolCalls'));
+
+-- Composite index for common query pattern: filter by world, chat, and owner agent
+-- This is the most common query pattern in the web UI (agent-specific message views)
+CREATE INDEX
+IF NOT EXISTS idx_events_world_chat_owner 
+  ON events
+(world_id, chat_id, json_extract
+(meta, '$.ownerAgentIds'));

package/migrations/0012_add_tool_role.sql

@@ -0,0 +1,78 @@
+-- Migration: Add 'tool' role support to agent_memory and archived_messages
+-- Version: 0012
+-- Date: 2025-11-08
+--
+-- Purpose: Allow role='tool' for tool result messages in approval flow
+-- This requires recreating tables since SQLite doesn't support modifying CHECK constraints
+--
+-- Note: Migration runner handles transactions automatically, so no explicit BEGIN/COMMIT needed
+
+PRAGMA foreign_keys=OFF;
+
+-- Clean up any existing backup tables from failed migration attempts
+DROP TABLE IF EXISTS agent_memory_backup;
+DROP TABLE IF EXISTS archived_messages_backup;
+
+-- Backup agent_memory (copy ALL columns as-is)
+CREATE TABLE agent_memory_backup AS SELECT * FROM agent_memory;
+
+-- Drop and recreate agent_memory with updated constraint
+DROP TABLE agent_memory;
+
+CREATE TABLE agent_memory (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  agent_id TEXT NOT NULL,
+  world_id TEXT NOT NULL,
+  role TEXT NOT NULL CHECK (role IN ('system', 'user', 'assistant', 'tool')),
+  content TEXT NOT NULL,
+  sender TEXT,
+  created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
+  chat_id TEXT,
+  message_id TEXT,
+  reply_to_message_id TEXT,
+  tool_calls TEXT,
+  tool_call_id TEXT,
+  FOREIGN KEY (agent_id, world_id) REFERENCES agents(id, world_id) ON DELETE CASCADE
+);
+
+-- Restore data from backup (explicitly list columns to handle any schema differences)
+INSERT INTO agent_memory (id, agent_id, world_id, role, content, sender, created_at, chat_id, message_id, reply_to_message_id, tool_calls, tool_call_id)
+SELECT id, agent_id, world_id, role, content, sender, created_at, chat_id, message_id, reply_to_message_id, tool_calls, tool_call_id
+FROM agent_memory_backup;
+DROP TABLE agent_memory_backup;
+
+-- Recreate indexes for agent_memory
+CREATE INDEX IF NOT EXISTS idx_agent_memory_agent_world ON agent_memory(agent_id, world_id);
+CREATE INDEX IF NOT EXISTS idx_agent_memory_chat_id ON agent_memory(chat_id);
+CREATE INDEX IF NOT EXISTS idx_agent_memory_message_id ON agent_memory(message_id);
+CREATE INDEX IF NOT EXISTS idx_agent_memory_reply_to ON agent_memory(reply_to_message_id);
+
+-- Backup archived_messages (copy ALL columns as-is)
+CREATE TABLE archived_messages_backup AS SELECT * FROM archived_messages;
+
+-- Drop and recreate archived_messages with updated constraint
+DROP TABLE archived_messages;
+
+CREATE TABLE archived_messages (
+  id INTEGER PRIMARY KEY AUTOINCREMENT,
+  archive_id INTEGER NOT NULL,
+  agent_id TEXT NOT NULL,
+  world_id TEXT NOT NULL,
+  role TEXT NOT NULL CHECK (role IN ('system', 'user', 'assistant', 'tool')),
+  content TEXT NOT NULL,
+  sender TEXT,
+  original_timestamp TIMESTAMP,
+  FOREIGN KEY (archive_id) REFERENCES memory_archives(id) ON DELETE CASCADE,
+  FOREIGN KEY (agent_id, world_id) REFERENCES agents(id, world_id) ON DELETE CASCADE
+);
+
+-- Restore data from backup (explicitly list columns for archived_messages)
+INSERT INTO archived_messages (id, archive_id, agent_id, world_id, role, content, sender, original_timestamp)
+SELECT id, archive_id, agent_id, world_id, role, content, sender, original_timestamp
+FROM archived_messages_backup;
+DROP TABLE archived_messages_backup;
+
+-- Recreate index for archived_messages
+CREATE INDEX IF NOT EXISTS idx_archived_messages_archive_id ON archived_messages(archive_id);
+
+PRAGMA foreign_keys=ON;

package/migrations/0013_add_world_variables.sql

@@ -0,0 +1,7 @@
+-- Migration: Add world variables text field
+-- Version: 13
+-- Date: 2026-02-12
+--
+-- Adds optional .env-style variables text storage to worlds.
+
+ALTER TABLE worlds ADD COLUMN variables TEXT;

package/migrations/0014_add_main_agent_and_auto_reply.sql

@@ -0,0 +1,10 @@
+-- Migration: Add world main_agent and agent auto_reply fields
+-- Version: 14
+-- Date: 2026-02-13
+--
+-- Adds:
+-- - worlds.main_agent (TEXT, nullable)
+-- - agents.auto_reply (INTEGER, default 1)
+
+ALTER TABLE worlds ADD COLUMN main_agent TEXT;
+ALTER TABLE agents ADD COLUMN auto_reply INTEGER NOT NULL DEFAULT 1;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-world",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "exports": {
@@ -20,9 +20,9 @@
     "web"
   ],
   "bin": {
-    "agent-world": "dist/server/index.js",
-    "agent-world-cli": "dist/cli/index.js",
-    "agent-world-server": "dist/server/index.js"
+    "agent-world": "bin/agent-world.js",
+    "agent-world-cli": "bin/agent-world-cli.js",
+    "agent-world-server": "bin/agent-world-server.js"
   },
   "scripts": {
     "dev": "npm run web:dev",
@@ -80,6 +80,7 @@
     "nanoid": "^5.1.5",
     "open": "^11.0.0",
     "openai": "^6.15.0",
+    "commander": "^14.0.0",
     "pino": "^10.0.0",
     "pino-pretty": "^13.1.3",
     "sqlite3": "^5.1.7",
@@ -97,7 +98,6 @@
     "@vitest/ui": "^4.0.16",
     "autoprefixer": "^10.4.23",
     "chai": "^6.2.1",
-    "commander": "^14.0.0",
     "npm-run-all": "^4.1.5",
     "postcss": "^8.5.6",
     "tailwindcss": "^4.1.18",