zenox 1.4.1 → 1.4.2

package/dist/index.js

@@ -823,6 +823,41 @@ The system automatically reminds you if you go idle with incomplete tasks.
 - The session goes idle
 - There's been sufficient time since the last reminder
 `;
+function getOrchestrationPrompt(agent) {
+  switch (agent) {
+    case "build":
+      return ORCHESTRATION_PROMPT;
+    case "plan":
+      return ORCHESTRATION_PROMPT;
+    default:
+      return;
+  }
+}
+
+// src/orchestration/session-agent-tracker.ts
+var sessionAgentMap = new Map;
+function setSessionAgent(sessionID, agent) {
+  if (agent) {
+    sessionAgentMap.set(sessionID, agent);
+  }
+}
+function getSessionAgent(sessionID) {
+  return sessionAgentMap.get(sessionID);
+}
+function clearSessionAgent(sessionID) {
+  if (sessionID) {
+    sessionAgentMap.delete(sessionID);
+  }
+}
+function getOrchestrationAgentType(agent) {
+  if (agent === "build")
+    return "build";
+  if (agent === "plan")
+    return "plan";
+  if (agent === undefined)
+    return;
+  return agent;
+}
 
 // node_modules/.pnpm/zod@3.25.76/node_modules/zod/v3/external.js
 var exports_external = {};
@@ -18314,6 +18349,7 @@ var ZenoxPlugin = async (ctx) => {
       ...codeIntelligenceTools
     },
     "chat.message": async (input, output) => {
+      setSessionAgent(input.sessionID, input.agent);
       const message = output.message;
       if (firstMessageVariantGate.shouldOverride(input.sessionID)) {
         const variant = resolveAgentVariant(pluginConfig, input.agent);
@@ -18326,6 +18362,17 @@ var ZenoxPlugin = async (ctx) => {
       }
       await keywordDetectorHook["chat.message"]?.(input, output);
     },
+    "experimental.chat.system.transform": async (input, output) => {
+      const { sessionID } = input;
+      if (!sessionID)
+        return;
+      const agent = getSessionAgent(sessionID);
+      const agentType = getOrchestrationAgentType(agent);
+      const prompt = getOrchestrationPrompt(agentType);
+      if (prompt) {
+        output.system.push(prompt);
+      }
+    },
     event: async (input) => {
       const { event } = input;
       await autoUpdateHook.event(input);
@@ -18341,6 +18388,7 @@ var ZenoxPlugin = async (ctx) => {
         const props = event.properties;
         const sessionID = props?.info?.id;
         firstMessageVariantGate.clear(sessionID);
+        clearSessionAgent(sessionID);
         if (sessionID && sessionID === backgroundManager.getMainSession()) {
           backgroundManager.setMainSession(undefined);
         }
@@ -18392,14 +18440,6 @@ var ZenoxPlugin = async (ctx) => {
       if (!disabledAgents.has("ui-planner")) {
         config2.agent["ui-planner"] = applyModelOverride("ui-planner", uiPlannerAgent);
       }
-      if (config2.agent.build) {
-        const existingPrompt = config2.agent.build.prompt ?? "";
-        config2.agent.build.prompt = existingPrompt + ORCHESTRATION_PROMPT;
-      }
-      if (config2.agent.plan) {
-        const existingPrompt = config2.agent.plan.prompt ?? "";
-        config2.agent.plan.prompt = existingPrompt + ORCHESTRATION_PROMPT;
-      }
       const builtinMcps = createBuiltinMcps(disabledMcps);
       config2.mcp = {
         ...config2.mcp,

package/dist/orchestration/prompt.d.ts

@@ -3,3 +3,4 @@
  * This teaches the primary agents how to delegate to specialized subagents using the Task tool.
  */
 export declare const ORCHESTRATION_PROMPT = "\n\n---\n\n## Sub-Agent Delegation\n\nYou have specialized subagents. Use the **Task tool** to delegate work proactively.\n\n### Available Agents\n\n| Agent | Use For | subagent_type |\n|-------|---------|---------------|\n| **Explorer** | Codebase grep - fast pattern matching, \"Where is X?\" | `explorer` |\n| **Librarian** | External grep - docs, GitHub, OSS examples | `librarian` |\n| **Oracle** | Strategic advisor - architecture, debugging, decisions | `oracle` |\n| **UI Planner** | Designer-developer - visual design, CSS, animations | `ui-planner` |\n\n### Quick Rule: Background vs Synchronous\n\n| Agent | Default Execution | Why |\n|-------|-------------------|-----|\n| Explorer | `background_task` | It's codebase grep - fire and continue |\n| Librarian | `background_task` | It's external grep - fire and continue |\n| Oracle | `Task` (sync) | Need strategic answer before proceeding |\n| UI Planner | `Task` (sync) | Implements changes, needs write access |\n\n**Mental Model**: Explorer & Librarian = **grep commands**. You don't wait for grep, you fire it and continue thinking.\n\n### When to Delegate (Fire Immediately)\n\n| Trigger | subagent_type | Why |\n|---------|---------------|-----|\n| \"Where is X?\", \"Find Y\", locate code | `explorer` | Fast codebase search |\n| External library, \"how does X library work?\" | `librarian` | Searches docs, GitHub, OSS |\n| 2+ modules involved, cross-cutting concerns | `explorer` | Multi-file pattern discovery |\n| Architecture decision, \"should I use X or Y?\" | `oracle` | Deep reasoning advisor |\n| Visual/styling, CSS, animations, UI/UX | `ui-planner` | Designer-developer hybrid |\n| After 2+ failed fix attempts | `oracle` | Debugging escalation |\n\n### How to Delegate\n\nUse the Task tool with these parameters:\n\n```\nTask(\n  subagent_type: \"explorer\" | \"librarian\" | \"oracle\" | \"ui-planner\",\n  description: \"Short 3-5 word task description\",\n  prompt: \"Detailed instructions for the agent\"\n)\n```\n\n**Example delegations:**\n\n```\n// Find code in codebase\nTask(\n  subagent_type: \"explorer\",\n  description: \"Find auth middleware\",\n  prompt: \"Find all authentication middleware implementations in this codebase. Return file paths and explain the auth flow.\"\n)\n\n// Research external library\nTask(\n  subagent_type: \"librarian\",\n  description: \"React Query caching docs\",\n  prompt: \"How does React Query handle caching? Find official documentation and real-world examples with GitHub permalinks.\"\n)\n\n// Architecture decision\nTask(\n  subagent_type: \"oracle\",\n  description: \"Redux vs Zustand analysis\",\n  prompt: \"Analyze trade-offs between Redux and Zustand for this project. Consider bundle size, learning curve, and our existing patterns.\"\n)\n\n// UI/Visual work\nTask(\n  subagent_type: \"ui-planner\",\n  description: \"Redesign dashboard cards\",\n  prompt: \"Redesign the dashboard stat cards to be more visually appealing. Use modern aesthetics, subtle animations, and ensure responsive design.\"\n)\n```\n\n### Parallel Execution\n\nTo run multiple agents in parallel, call multiple Task tools in the **same response message**:\n\n```\n// CORRECT: Multiple Task calls in ONE message = parallel execution\nTask(subagent_type: \"explorer\", description: \"Find auth code\", prompt: \"...\")\nTask(subagent_type: \"librarian\", description: \"JWT best practices\", prompt: \"...\")\n// Both run simultaneously\n\n// WRONG: One Task per message = sequential (slow)\nMessage 1: Task(...) \u2192 wait for result\nMessage 2: Task(...) \u2192 wait for result\n```\n\n### Delegation Priority\n\n1. **Explorer FIRST** \u2014 Always locate code before modifying unfamiliar areas\n2. **Librarian** \u2014 When dealing with external libraries/APIs you don't fully understand\n3. **Oracle** \u2014 For complex decisions or after 2+ failed fix attempts\n4. **UI Planner** \u2014 For ANY visual/styling work (never edit CSS/UI yourself)\n\n### Critical Rules\n\n1. **Never touch frontend visual/styling code yourself** \u2014 Always delegate to `ui-planner`\n2. **Fire librarian proactively** when unfamiliar libraries are involved\n3. **Consult oracle BEFORE major architectural decisions**, not after\n4. **Verify delegated work** before marking task complete\n\n### When to Handle Directly (Don't Delegate)\n\n- Single file edits with known location\n- Questions answerable from code already in context\n- Trivial changes requiring no specialist knowledge\n- Tasks you can complete faster than explaining to an agent\n\n---\n\n## Background Tasks (Parallel Research)\n\nFor **independent research tasks** that benefit from parallelism, use background tasks instead of sequential Task calls.\n\n### When to Use Background Tasks\n\n| Scenario | Use Background Tasks |\n|----------|---------------------|\n| User wants \"comprehensive\" / \"thorough\" / \"deep\" exploration | YES - fire 3-4 agents in parallel |\n| Need BOTH codebase search AND external docs | YES - explore + librarian in parallel |\n| Exploring multiple modules/features simultaneously | YES - separate explore for each |\n| Result of Task A needed before Task B | NO - use sequential Task |\n| Single focused lookup | NO - just use Task directly |\n\n### How Background Tasks Work\n\n1. **Fire**: Launch multiple agents with `background_task` - they run in parallel\n2. **Continue**: Keep working while background agents search\n3. **Notify**: You'll be notified when ALL background tasks complete\n4. **Retrieve**: Use `background_output` to get each result\n\n### Usage\n\n```\n// Launch parallel research (all run simultaneously)\nbackground_task(agent=\"explorer\", description=\"Find auth code\", prompt=\"Search for authentication...\")\nbackground_task(agent=\"explorer\", description=\"Find db layer\", prompt=\"Search for database/ORM...\")\nbackground_task(agent=\"librarian\", description=\"Best practices\", prompt=\"Find framework best practices...\")\n\n// Continue working on other things while they run...\n\n// [NOTIFICATION: All background tasks complete!]\n\n// Retrieve results\nbackground_output(task_id=\"bg_abc123\")\nbackground_output(task_id=\"bg_def456\")\nbackground_output(task_id=\"bg_ghi789\")\n```\n\n### Background Tasks vs Task Tool\n\n| Aspect | Task Tool | Background Tasks |\n|--------|-----------|------------------|\n| Execution | Sequential (waits for result) | Parallel (fire-and-forget) |\n| Best for | Dependent tasks, immediate needs | Independent research, breadth |\n| Result | Inline, immediate | Retrieved later via background_output |\n\n### Key Insight\n\n- **Task** = Use when you need the result immediately before proceeding\n- **Background** = Use when researching multiple angles independently\n\n**Both tools coexist - choose based on whether tasks are dependent or independent.**\n\n### The Parallel Research Pattern\n\nFor complex tasks, fire research first, then continue working:\n\n```\n// 1. FIRE parallel research (don't wait!)\nbackground_task(agent=\"explorer\", description=\"Find existing patterns\", prompt=\"...\")\nbackground_task(agent=\"librarian\", description=\"Find best practices\", prompt=\"...\")\n\n// 2. CONTINUE productive work while they run:\n//    - Plan your implementation approach\n//    - Read files you already know about\n//    - Identify edge cases and questions\n\n// 3. When notified \u2192 RETRIEVE and synthesize\nbackground_output(task_id=\"bg_xxx\")\nbackground_output(task_id=\"bg_yyy\")\n```\n\n**Anti-pattern**: Firing background tasks then doing nothing. Always continue productive work!\n\n---\n\n## Keyword Triggers (Power User)\n\nInclude these keywords in your prompt to unlock special modes:\n\n| Keyword | Effect |\n|---------|--------|\n| `ultrawork` or `ulw` | Maximum multi-agent coordination - aggressive parallel research |\n| `deep research` | Comprehensive exploration - fires 3-4 background agents |\n| `explore codebase` | Codebase mapping - multiple explorers in parallel |\n\n---\n\n## Session History Tools\n\nYou have tools to learn from past work sessions:\n\n| Tool | Use For |\n|------|---------|\n| `session_list` | List recent sessions to find relevant past work |\n| `session_search` | Search messages across sessions for how something was done |\n\n### When to Use Session Tools\n\n- **Before implementing unfamiliar features** \u2014 search if done before\n- **When user says \"like before\" or \"last time\"** \u2014 find that session\n- **When debugging** \u2014 check if similar issues were solved previously\n- **For context on ongoing projects** \u2014 understand recent work history\n\n### Example Usage\n\n```\n// Find how authentication was implemented before\nsession_search({ query: \"JWT authentication\" })\n\n// List recent sessions to understand project context\nsession_list({ limit: 5 })\n\n// Find past implementations of a feature\nsession_search({ query: \"rate limiting\" })\n```\n\n---\n\n## Code Intelligence Tools\n\nYou have tools to understand code structure via LSP:\n\n| Tool | Use For |\n|------|---------|\n| `find_symbols` | Search for functions, classes, variables by name |\n| `lsp_status` | Check which language servers are running |\n\n### When to Use Code Intelligence\n\n- **Before editing code** \u2014 find the symbol's definition location\n- **When refactoring** \u2014 search for related symbols\n- **To understand project structure** \u2014 search for key symbols like \"auth\", \"user\", \"api\"\n- **To verify LSP availability** \u2014 check if code intelligence is working\n\n### Example Usage\n\n```\n// Find all auth-related functions/classes\nfind_symbols({ query: \"auth\" })\n\n// Find a specific function\nfind_symbols({ query: \"handleLogin\" })\n\n// Check LSP server status\nlsp_status()\n```\n\n---\n\n## Todo Continuation\n\nThe system automatically reminds you if you go idle with incomplete tasks.\n\n**Best Practices:**\n- Keep your todo list updated with `TodoWrite`\n- Mark tasks complete immediately when finished\n- Use clear, actionable task descriptions\n- The system will prompt you to continue if tasks remain incomplete\n\n**Note:** You don't need to invoke the todo enforcer \u2014 it runs automatically when:\n- You have pending or in-progress todos\n- The session goes idle\n- There's been sufficient time since the last reminder\n";
+export declare function getOrchestrationPrompt(agent: "build" | "plan" | string | undefined): string | undefined;

package/dist/orchestration/session-agent-tracker.d.ts

@@ -0,0 +1,36 @@
+/**
+ * Session-Agent Tracker
+ *
+ * Tracks which agent is active for each session, allowing the system transform
+ * hook to inject agent-specific prompts.
+ *
+ * Flow:
+ * 1. chat.message hook fires with { sessionID, agent }
+ * 2. We store the mapping: sessionID -> agentName
+ * 3. experimental.chat.system.transform fires with { sessionID }
+ * 4. We look up the agent and inject the appropriate prompt
+ */
+/**
+ * Record which agent is active for a session.
+ * Called from chat.message hook.
+ */
+export declare function setSessionAgent(sessionID: string, agent: string | undefined): void;
+/**
+ * Get the active agent for a session.
+ * Called from experimental.chat.system.transform hook.
+ */
+export declare function getSessionAgent(sessionID: string): string | undefined;
+/**
+ * Clear tracking for a session (on deletion).
+ */
+export declare function clearSessionAgent(sessionID: string | undefined): void;
+/**
+ * Check if an agent should receive orchestration injection.
+ * Only build and plan agents get the orchestration prompt.
+ */
+export declare function shouldInjectOrchestration(agent: string | undefined): boolean;
+/**
+ * Get the agent type for prompt selection.
+ * Returns "build", "plan", or string for other agents.
+ */
+export declare function getOrchestrationAgentType(agent: string | undefined): "build" | "plan" | string | undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zenox",
-  "version": "1.4.1",
+  "version": "1.4.2",
   "description": "OpenCode plugin with specialized agents (explorer, librarian, oracle, ui-planner), background tasks for parallel execution, and smart orchestration",
   "author": "Ayush",
   "license": "MIT",