orchestrix-yuri 4.7.0 → 4.7.1

package/lib/gateway/history.js

@@ -70,6 +70,19 @@ class ChatHistory {
     this._trimIfNeeded(filePath);
   }
 
+  /**
+   * Get the last assistant message for a chat.
+   * @param {string} chatId
+   * @returns {string|null}
+   */
+  getLastAssistantMessage(chatId) {
+    const messages = this.getRecent(chatId);
+    for (let i = messages.length - 1; i >= 0; i--) {
+      if (messages[i].role === 'assistant') return messages[i].text;
+    }
+    return null;
+  }
+
   _trimIfNeeded(filePath) {
     const lines = fs.readFileSync(filePath, 'utf8').trim().split('\n').filter(Boolean);
     const limit = this.maxMessages * 2;

package/lib/gateway/router.js

@@ -282,18 +282,37 @@ class Router {
     }
 
     // ═══ DISPATCHER CLASSIFY — NL intent detection via persistent Claude agent ═══
-    if (this.dispatcher && this.dispatcher.isReady()) {
-      try {
-        const classified = await this.dispatcher.classify(msg.text);
-        log.router(`Dispatcher: ${classified.action} ← "${msg.text.slice(0, 50)}..." (${classified.reasoning})`);
+    {
+      // Inject last assistant response as context for the dispatcher
+      const lastReply = this.history.getLastAssistantMessage(msg.chatId);
+      const contextText = lastReply
+        ? `[CONTEXT] Previous assistant response: ${lastReply.slice(0, 300)}\n\nUser message: ${msg.text}`
+        : msg.text;
+
+      let classified = null;
+      if (this.dispatcher) {
+        try {
+          classified = await this.dispatcher.classify(contextText);
+          log.router(`Dispatcher: ${classified.action} ← "${msg.text.slice(0, 50)}..." (${classified.reasoning})`);
+        } catch (err) {
+          log.warn(`Dispatcher classify failed: ${err.message}`);
+        }
+      }
 
-        if (classified.action !== 'conversation') {
+      // If dispatcher unavailable or failed, default to 'change' for work-like messages
+      if (!classified) {
+        classified = { action: 'change', description: msg.text, reasoning: 'dispatcher unavailable, defaulting to change' };
+        log.router(`Dispatcher unavailable, defaulting to change for: "${msg.text.slice(0, 50)}..."`);
+      }
+
+      if (classified.action !== 'conversation') {
+        try {
           const intentResult = await this._executeClassifiedIntent(classified, msg);
           if (intentResult) return intentResult;
+        } catch (err) {
+          log.warn(`Intent execution failed: ${err.message}`);
+          // Fall through to conversation
         }
-      } catch (err) {
-        log.warn(`Dispatcher classify failed: ${err.message}`);
-        // Fall through to normal processing
       }
     }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orchestrix-yuri",
-  "version": "4.7.0",
+  "version": "4.7.1",
   "description": "Yuri — Meta-Orchestrator for Orchestrix. Drive your entire project lifecycle with natural language.",
   "main": "lib/installer.js",
   "bin": {

package/skill/resources/dispatcher-prompt.txt

@@ -1,19 +1,20 @@
 You are a message classifier for Yuri, a project orchestrator.
 
 Your ONLY job is to classify incoming user messages into structured actions.
+Messages may include "[CONTEXT]" with the previous assistant response for reference.
 
 ## Available Actions
 
 | Action | When to use | Examples |
 |--------|-------------|---------|
-| change | User wants something fixed, modified, added, redesigned, or wants a specific agent to do work | "这个 bug 修一下", "让 UX 重新设计界面", "Add dark mode", "让 architect 评估可行性" |
-| plan | User wants to start or restart the planning phase | "开始规划", "重新做 PRD", "重新规划架构" |
-| develop | User wants to start or continue development | "开始开发", "继续写代码" |
+| change | User wants ANY work done: fix, modify, add, redesign, create a plan, write something, have an agent do work | "这个 bug 修一下", "让 UX 重新设计界面", "Add dark mode", "先做个完整的设计 plan", "写一份方案", "从 PO 开始改" |
+| plan | User explicitly wants to START the planning phase from scratch | "开始规划", "*plan" |
+| develop | User explicitly wants to START development phase | "开始开发", "*develop" |
 | test | User wants to run tests | "跑一下测试", "冒烟测试" |
 | deploy | User wants to deploy or release | "部署到线上", "发布", "上线" |
 | status | User asks about progress, previous results, or what happened | "之前的方案呢？", "进展如何？", "怎么样了", "结果出来了吗" |
 | iterate | User wants a new iteration cycle | "新迭代", "下一轮" |
-| conversation | Pure question, opinion, or chat — no actionable request | "你觉得怎么样？", "这个架构好不好？", "解释一下这段代码" |
+| conversation | ONLY for pure questions or opinions with NO actionable request | "你觉得怎么样？", "这个架构好不好？", "解释一下这段代码" |
 
 ## Response Format
 
@@ -21,12 +22,13 @@ Reply with EXACTLY this JSON format on a single line, nothing else:
 
 {"action":"<action>","description":"<brief description for the agent>","reasoning":"<one sentence why>"}
 
-## Rules
+## Critical Rules
 
-- If the user references a specific agent role (UX, UI, architect, PM, QA, dev, SM), and wants them to DO something, classify as "change"
-- If the user asks about previous results, output, or progress, classify as "status"
-- If the user expresses dissatisfaction and wants improvement, classify as "change" (they want something fixed/redesigned)
-- If the user expresses an opinion or asks a question WITHOUT requesting any action, classify as "conversation"
-- When in doubt, prefer "conversation" — it is safer to chat than to trigger an unintended action
-- The "description" field should be a concise summary of what the user wants done, suitable for passing to an agent
+- **Bias toward "change"**: If the user wants ANYTHING done (create, write, fix, modify, redesign, evaluate, plan something), classify as "change". The "change" action is the safe default for any work request.
+- If the user is replying to a question with a choice/decision (e.g., "先做 plan" answering "要 A 还是 B？"), that reply IS an instruction — classify as "change", NOT "conversation".
+- If the user references a specific agent role (UX, UI, architect, PM, QA, dev, SM) and wants them to do something, classify as "change".
+- If the user asks about previous results, output, or progress, classify as "status".
+- "conversation" is ONLY for messages that require NO action at all — pure questions, opinions, greetings.
+- When in doubt between "change" and "conversation", ALWAYS choose "change".
+- The "description" field should be a concise summary of what the user wants done.
 - ALWAYS respond with the JSON format above. Never add explanation, markdown, or anything else.