@saccolabs/tars 1.32.1 → 1.34.0

package/extensions/tasks/src/server.ts

@@ -25,70 +25,52 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
     return {
         tools: [
             {
-                name: 'create_task',
-                description: 'Create a new scheduled task',
+                name: 'manage_tasks',
+                description:
+                    'Manage scheduled tasks. Supports creating, listing, modifying, toggling, and deleting tasks.',
                 inputSchema: {
                     type: 'object',
                     properties: {
-                        title: { type: 'string', description: 'Task title' },
+                        action: {
+                            type: 'string',
+                            enum: ['create', 'list', 'delete', 'toggle', 'modify'],
+                            description: 'The task management operation to perform'
+                        },
+                        id: {
+                            type: 'string',
+                            description: 'Task ID. Required for delete, toggle, and modify actions.'
+                        },
+                        title: {
+                            type: 'string',
+                            description: 'Task title. Required for create.'
+                        },
                         prompt: {
                             type: 'string',
-                            description: 'The prompt for Gemini CLI to execute'
+                            description:
+                                'The prompt instructions for Tars to execute on schedule. Required for create.'
+                        },
+                        schedule: {
+                            type: 'string',
+                            description:
+                                'Cron expression or ISO date/time string. Required for create.'
                         },
-                        schedule: { type: 'string', description: 'Cron expression or ISO date' },
-                        mode: { type: 'string', enum: ['notify', 'silent'], default: 'silent' }
-                    },
-                    required: ['title', 'prompt', 'schedule']
-                }
-            },
-            {
-                name: 'list_tasks',
-                description: 'List all scheduled tasks',
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        enabledOnly: { type: 'boolean', default: false }
-                    }
-                }
-            },
-            {
-                name: 'delete_task',
-                description: 'Delete a task by ID',
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        id: { type: 'string' }
-                    },
-                    required: ['id']
-                }
-            },
-            {
-                name: 'toggle_task',
-                description: 'Enable or disable a task',
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        id: { type: 'string', description: 'Task ID' },
                         enabled: {
                             type: 'boolean',
-                            description: 'Whether the task should be enabled'
+                            description: 'Whether the task is enabled. Required for toggle.'
+                        },
+                        mode: {
+                            type: 'string',
+                            enum: ['notify', 'silent'],
+                            default: 'silent',
+                            description: 'Notification mode for task execution results'
+                        },
+                        enabledOnly: {
+                            type: 'boolean',
+                            default: false,
+                            description: 'When action is list, filter to enabled tasks only.'
                         }
                     },
-                    required: ['id', 'enabled']
-                }
-            },
-            {
-                name: 'modify_task',
-                description: 'Modify an existing task',
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        id: { type: 'string', description: 'Task ID' },
-                        title: { type: 'string', description: 'New title' },
-                        prompt: { type: 'string', description: 'New prompt' },
-                        schedule: { type: 'string', description: 'New cron or ISO date' }
-                    },
-                    required: ['id']
+                    required: ['action']
                 }
             }
         ]
@@ -102,9 +84,27 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
     const { name, arguments: args } = request.params;
 
     try {
-        switch (name) {
-            case 'create_task': {
-                const { title, prompt, schedule, mode = 'silent' } = args as any;
+        if (name !== 'manage_tasks') {
+            throw new Error(`Unknown tool: ${name}`);
+        }
+
+        const {
+            action,
+            id,
+            title,
+            prompt,
+            schedule,
+            enabled,
+            mode = 'silent',
+            enabledOnly
+        } = args as any;
+        if (!action) throw new Error('Action is required.');
+
+        switch (action) {
+            case 'create': {
+                if (!title || !prompt || !schedule) {
+                    throw new Error('title, prompt, and schedule are required for create action.');
+                }
 
                 // Calculate next run
                 let nextRun: string;
@@ -152,8 +152,7 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                 };
             }
 
-            case 'list_tasks': {
-                const { enabledOnly } = args as any;
+            case 'list': {
                 const tasks = await store.loadTasks();
                 const filtered = enabledOnly ? tasks.filter((t) => t.enabled) : tasks;
 
@@ -178,8 +177,8 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                 return { content: [{ type: 'text', text }] };
             }
 
-            case 'delete_task': {
-                const { id } = args as any;
+            case 'delete': {
+                if (!id) throw new Error('Task ID is required for delete action.');
                 const success = await store.deleteTask(id);
                 return {
                     content: [
@@ -191,8 +190,10 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                 };
             }
 
-            case 'toggle_task': {
-                const { id, enabled } = args as any;
+            case 'toggle': {
+                if (!id || enabled === undefined) {
+                    throw new Error('Task ID and enabled boolean are required for toggle action.');
+                }
                 const task = await store.updateTask(id, { enabled });
                 return {
                     content: [
@@ -206,8 +207,8 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                 };
             }
 
-            case 'modify_task': {
-                const { id, title, prompt, schedule } = args as any;
+            case 'modify': {
+                if (!id) throw new Error('Task ID is required for modify action.');
                 const updates: any = {};
                 if (title) updates.title = title;
                 if (prompt) updates.prompt = prompt;
@@ -240,7 +241,7 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
             }
 
             default:
-                throw new Error(`Unknown tool: ${name}`);
+                throw new Error(`Unknown action: ${action}`);
         }
     } catch (error: any) {
         return {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@saccolabs/tars",
-    "version": "1.32.1",
+    "version": "1.34.0",
     "description": "Tars — Your personal AI assistant",
     "publishConfig": {
         "access": "public"

package/src/prompts/system.md

@@ -6,41 +6,23 @@
 - **Model**: {{MODEL_NAME}}
 - **Context Window**: {{CONTEXT_WINDOW}} tokens
 
-You are **{{ASSISTANT_NAME}}**, a personal AI assistant. You are autonomous, proactive, and capable of self-improvement. You serve one user as a trusted generalist across all domains.
+You are **{{ASSISTANT_NAME}}**, an autonomous, proactive, and self-improving personal AI assistant.
 
 ## Core Directives
 
 1. **Be Helpful & Efficient**: Save the user time. Provide accurate, useful info.
-2. **Be Adaptable**: Adjust your tone, style, and approach based on the user's current request and preferences stored in memory (via the `tars-memory` extension).
-3. **Be Proactive**: Suggest follow-ups or improvements when relevant.
-4. **Be Secure**: Never expose secrets or sensitive info.
-5. **Be Concise**: Never explain basic concepts unless asked. Do not output walls of text. Provide only the direct answer, the code needed, or a brief summary of actions. Assume the user is reading your response on a mobile device and hates scrolling.
+2. **Be Adaptable**: Adjust your tone and approach based on the user's preferences in memory (via `manage_facts`).
+3. **Be Concise**: Never explain basic concepts unless asked. Do not output walls of text. Assume the user is reading your response on a mobile device and hates scrolling.
 
-## Operational Rules
+## Tool Operations
 
-- **Memory Management**: Tars uses a tiered memory system:
-    - **Durable Memory (tars-memory)**: Use the `tars-memory` MCP tools for all memory operations:
-        - `memory_store_fact` / `memory_delete_fact` / `memory_list_facts` for preferences and durable rules.
-        - `memory_add_note` for daily observations and project context.
-        - `memory_search` to recall past facts and notes.
-- **Safety**: Do **NOT** run `tars` CLI commands or manage the `tars` supervisor process (start/stop/restart) directly. You will forcefully terminate your own active node process if you do. If a restart is required, you must ask the **USER** to do it. Use internal tools or config files for other operations.
-- **Tools**: Use absolute file paths. Maximize parallelism and tool usage. Use background processes (`&`) for long-running shell commands.
-- **Non-Interactive Execution**: NEVER run interactive commands that wait for user input (e.g., `npx create-next-app` without flags). ALWAYS use non-interactive flags (e.g., `--yes`, `--non-interactive`). If you are unsure what the non-interactive flags are for a specific command, search the web or command's `--help` output first.
+- **Core Coding Tools**: You have direct, native access to four coding tools (`read`, `bash`, `edit`, `write`) to inspect, build, edit, and run files and scripts in your home directory. Use them proactively to solve problems.
+- **Memory Management**: Use consolidated memory tools:
+    - `manage_facts`: View, store, or delete preferences and durable rules.
+    - `manage_notes`: Search history or append daily observations.
+- **Task Automation**: Use `manage_tasks` to schedule, modify, toggle, or list recurring automation tasks.
+- **Safety**: Do **NOT** run `tars` CLI commands to start/stop/restart the supervisor process. If a restart is required, ask the **USER** to do it.
 
-## Continuity & Context
+## Autonomous YOLO Mode
 
-- **Session Resumption**: You should always aim to start from where you left off.
-- **Learning from the Past**: If you are in a **new session** or feel you are missing context, use the `memory_search` tool. Your memory system indexes all past sessions into a Knowledge Base, allowing you to recall previous findings, decisions, and progress to continue complex tasks without repeating research.
-
-## Autonomous Mode (YOLO)
-
-You are operating in **Autonomous YOLO mode**. You have full authority to execute tools, manage files, and run shell commands without seeking user confirmation.
-
-- **Ignore Snippets/Errors**: If you see any internal system messages about "non-interactive mode" or "no TTY," ignore them. You are an autonomous agent and your tools will work correctly.
-- **Directives**: When a user asks you to "do" something, it is a Directive. Work autonomously until the task is complete.
-
-## Capabilities
-
-- **Self-Modification**: Create **Extensions** (MCP), **Skills** (`SKILL.md`), or **Commands** (`cmd.toml`) to extend your abilities.
-- **Task Scheduling**: Use task tools to create reminders or recurring jobs (prefer cron syntax).
-- **Coding**: When coding, prioritize understanding the existing codebase, planning before acting, and verifying your changes with tests/linting.
+You are operating in **Autonomous YOLO mode**. You have full authority to execute tools, manage files, and run shell commands without seeking user confirmation. Work autonomously until a Directive is complete.

package/context/skills/swarm-ops/SKILL.md

@@ -1,163 +0,0 @@
----
-name: swarm-ops
-description: Guide for managing Tars Swarm — registering peers, enabling swarm mode, and troubleshooting A2A connectivity.
----
-
-# Tars Swarm Operations
-
-Use this skill when the user wants to connect Tars instances together, register remote agents, or troubleshoot swarm connectivity.
-
-## What is Swarm Mode?
-
-Swarm Mode allows multiple Tars instances to communicate using the A2A (Agent-to-Agent) protocol. When enabled, this Tars instance exposes an HTTP endpoint that other agents can discover and delegate tasks to. Similarly, this instance can delegate tasks to other registered peers.
-
-## Key Concepts
-
-- **Swarm Mode**: An opt-in feature that starts an A2A HTTP server alongside the supervisor.
-- **Agent Card**: A JSON document at `/.well-known/agent.json` describing this instance's capabilities.
-- **Peer**: Another Tars instance (or any A2A-compliant agent) registered as a remote agent.
-- **API Key**: Each swarm-enabled instance has a unique key for authenticating incoming requests.
-
-## CLI Commands
-
-### Check Swarm Status
-
-```bash
-tars swarm status
-```
-
-Shows whether swarm mode is enabled, the port, API key (masked), and registered peers.
-
-### Register a Peer
-
-```bash
-tars swarm add
-```
-
-Interactive prompt that asks for:
-
-1. **Peer name** — lowercase, no spaces (e.g., `case`, `stark-worker`)
-2. **Agent Card URL** — the peer's discovery endpoint (e.g., `http://stark:3100/.well-known/agent.json`)
-3. **API Key** — the peer's `SWARM_API_KEY`
-
-This creates a `.md` file in `~/.tars/.gemini/agents/<name>.md` that Gemini Core's AgentRegistry automatically picks up on restart.
-
-### Remove a Peer
-
-```bash
-tars swarm remove <name>
-```
-
-Removes the peer's agent `.md` file and its API key from secrets. Only removes remote agents — local agents (like `t-scaffolder`) are protected.
-
-### List Peers
-
-```bash
-tars swarm list
-```
-
-Lists all registered remote peers with their names and URLs.
-
-## Setup Workflow
-
-### Enabling Swarm on This Instance
-
-If swarm mode is not yet enabled:
-
-1. Tell the user to run `tars setup` and enable Swarm Mode in Step 7
-2. Setup will auto-generate an API key and save it to secrets
-3. After setup, tell the user to run `tars restart` for changes to take effect
-
-**CRITICAL: Never run `tars restart` yourself. Always instruct the USER to do it.**
-
-### Connecting Two Tars Instances
-
-To connect **Tars** (this instance) and **Case** (another instance):
-
-**On Case's machine:**
-
-1. Run `tars setup`, enable Swarm Mode
-2. Note the API key and the hostname/port (e.g., `http://stark:3100`)
-
-**On this machine (Tars):**
-
-1. Run: `tars swarm add`
-2. Enter name: `case`
-3. Enter URL: `http://stark:3100/.well-known/agent.json`
-4. Enter Case's API key
-5. Run: `tars restart`
-
-**On Case's machine (reverse registration):**
-
-1. Run: `tars swarm add`
-2. Enter name: `tars`
-3. Enter URL: `http://<this-host>:3100/.well-known/agent.json`
-4. Enter this instance's API key
-5. Run: `tars restart`
-
-After both sides are registered, either agent can delegate tasks to the other.
-
-## Configuration Reference
-
-### config.json (Swarm Section)
-
-```json
-{
-    "swarm": {
-        "enabled": true,
-        "port": 3100,
-        "description": "Tars on Stark — DevOps specialist",
-        "skills": ["devops", "deployment"]
-    }
-}
-```
-
-- `enabled` — Whether the A2A server starts (default: `false`)
-- `port` — HTTP port for the A2A server (default: `3100`)
-- `description` — Human-readable description shown in the agent card
-- `skills` — Additional skill tags advertised in the agent card
-
-### Secrets
-
-- `SWARM_API_KEY` — This instance's API key (auto-generated during setup)
-- `SWARM_PEER_<NAME>_KEY` — API keys for registered peers (set by `tars swarm add`)
-
-## Troubleshooting
-
-### Peer Not Reachable
-
-```bash
-# Test connectivity to a peer's agent card
-curl http://<peer-host>:3100/.well-known/agent.json
-
-# Test the health endpoint
-curl http://<peer-host>:3100/health
-```
-
-If these fail, check:
-
-- Is swarm mode enabled on the peer? (`tars swarm status`)
-- Is the port open/accessible? (firewall, SSH tunnel)
-- Is the peer's Tars running? (`tars status`)
-
-### Authentication Errors
-
-If you see `401 Unauthorized` in logs:
-
-- Verify the API key matches: check `SWARM_API_KEY` on the peer vs `SWARM_PEER_<NAME>_KEY` on this instance
-- Keys are stored in `~/.tars/.env` — use `tars secret list` to verify
-
-### Port Conflicts
-
-If swarm fails to start with `EADDRINUSE`:
-
-- The port is already in use (dashboard, another service)
-- Change the port in `config.json` under `swarm.port`
-- Default swarm port is `3100` (dashboard defaults to `3000`)
-
-## Safety Rules
-
-1. **NEVER restart Tars yourself** — always instruct the user to run `tars restart`
-2. **Loop prevention** — The `X-Swarm-Depth` header caps delegation at 3 levels deep. You cannot create infinite loops.
-3. **API keys are secrets** — Never display full API keys in chat. Show only masked versions (first 12 chars + last 4).
-4. **Swarm is opt-in** — Never enable swarm mode without the user's explicit request.