tuna-agent 0.1.169 → 0.1.171

package/dist/agents/claude-code-adapter.js

@@ -476,7 +476,7 @@ export class ClaudeCodeAdapter {
         ws.sendProgress(task.id, 'planning', { startedAt: new Date().toISOString() });
         ws.sendPMMessage(task.id, {
             sender: 'pm',
-            content: "I'm analyzing your project to create an execution plan...",
+            content: 'Đang xem xét yêu cầu…',
         });
         let planFirstChunkIso = '';
         let planChunkCount = 0;

package/dist/pm/planner.js

@@ -30,24 +30,30 @@ function isSimpleTask(description) {
     // Default: treat as complex (safer)
     return false;
 }
-const SIMPLE_PROMPT = `You are a PM creating a quick plan for a simple task.
+const SIMPLE_PROMPT = `You are planning a task for yourself — the agent described in this project's context (CLAUDE.md), working in your OWN area of expertise (which may be non-software: ASO, content, marketing, research, ops, etc.).
 
 Output ONLY valid JSON (no markdown, no explanation):
 {
   "summary": "One-line summary of what will be done",
   "subtasks": [{
     "id": "sub-1",
-    "role": "fullstack",
+    "role": "self",
     "description": "Complete task description with specific steps",
     "cwd": ".",
     "dependencies": []
   }]
 }`;
-const PLAN_SYSTEM_PROMPT = `You are a senior technical PM orchestrating developer sessions. Your job is to:
-1. Read the project structure to understand the codebase, tech stack, and existing patterns
-2. Analyze the given task thoroughly
-3. Define API contracts if the task involves both backend and frontend
-4. Break the task into subtasks for different developer roles
+const PLAN_SYSTEM_PROMPT = `You are the agent described in this project's context (CLAUDE.md). Plan how to accomplish the task within YOUR area of expertise — which may be NON-software (ASO, content, marketing, research, ops...). Do NOT assume every task is software development.
+
+DEFAULT: produce ONE subtask with role "self" — you do the task yourself in a single focused execution. This is correct for the vast majority of tasks (analysis, data/config edits, content, research, ops).
+
+ONLY split into multiple subtasks with developer roles (backend/frontend/tester) when the task is GENUINELY a complex software build needing parallel developer sessions with shared API contracts.
+
+Your job:
+1. Read the project/context to understand what you're working with
+2. Analyze the given task
+3. (Software builds only) Define API contracts if the task spans backend and frontend
+4. Break into subtasks ONLY if truly needed — otherwise a single "self" subtask
 
 CRITICAL RULES:
 
@@ -71,7 +77,7 @@ Execution layers (dependencies):
 - Testers should depend on the code they're testing
 - Minimize layers to maximize parallelism
 
-Roles: "backend", "frontend", "tester", "fullstack"
+Roles: "self" (default — your own-domain work), or "backend"/"frontend"/"tester" ONLY for actual software subtasks. "role" is a display label; it does not change execution.
 
 If you need information that ONLY the user can decide (e.g., business rules, design preferences, auth method choice), include it in the "questions" array. The user will answer before execution starts. Do NOT guess — ask.
 
@@ -130,8 +136,8 @@ export async function planTask(task, onProgress, signal, onTextChunk, inputFiles
     const systemPrompt = isSimple ? SIMPLE_PROMPT : PLAN_SYSTEM_PROMPT;
     const maxTurns = isSimple ? 3 : 15;
     const userPrompt = isSimple
-        ? `Create a simple plan for this task:\n\n${task.description}`
-        : `Analyze this project and create an execution plan.\n\nTask: ${task.description}\n\nFirst, explore the project structure to understand the codebase, existing patterns, and tech stack. Then output your plan as JSON.`;
+        ? `Plan this task:\n\n${task.description}`
+        : `Plan how to accomplish this task within your area of expertise.\n\nTask: ${task.description}\n\nRead the project/context as needed to understand what you're working with, then output your plan as JSON. Default to a single "self" subtask unless this is genuinely a complex software build.`;
     if (isSimple) {
         console.log('[PM] Simple task detected → using quick planning');
     }

package/dist/utils/message-schemas.d.ts

@@ -16,13 +16,7 @@ export declare const TaskAssignmentSchema: z.ZodObject<{
             file_type: z.ZodString;
             file_name: z.ZodString;
         }, z.core.$strip>>>;
-        source: z.ZodDefault<z.ZodOptional<z.ZodEnum<{
-            manual: "manual";
-            skill: "skill";
-            scheduled: "scheduled";
-            workflow: "workflow";
-            api: "api";
-        }>>>;
+        source: z.ZodDefault<z.ZodOptional<z.ZodString>>;
         agentId: z.ZodOptional<z.ZodString>;
         enableReflection: z.ZodOptional<z.ZodBoolean>;
     }, z.core.$strip>;

package/dist/utils/message-schemas.js

@@ -14,7 +14,10 @@ export const TaskAssignmentSchema = z.object({
         mode: z.enum(['tuna', 'agent_team']),
         confirmBeforeEdit: z.boolean().optional().default(false),
         attachments: z.array(ChatAttachmentSchema).optional(),
-        source: z.enum(['manual', 'skill', 'scheduled', 'workflow', 'api']).optional().default('manual'),
+        // Accept any source string — it is metadata only. A strict enum here rejected
+        // the WHOLE task_assigned message for any new source (e.g. 'discord'), silently
+        // stranding tasks in 'queued'.
+        source: z.string().optional().default('manual'),
         agentId: z.string().optional(),
         enableReflection: z.boolean().optional(),
     }),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tuna-agent",
-  "version": "0.1.169",
+  "version": "0.1.171",
   "description": "Tuna Agent - Run AI coding tasks on your machine",
   "bin": {
     "tuna-agent": "dist/cli/index.js"