oh-my-opencode-serverlocal 0.1.5 → 0.1.6

package/dist/index.js

@@ -18499,12 +18499,6 @@ ${text}
 </system-reminder>`;
 }
 var PHASE_REMINDER = formatSystemReminder(PHASE_REMINDER_TEXT);
-var WRITABLE_FILE_OPERATIONS_RULES = `**File Operations Rules**:
-- Prefer dedicated file tools for normal code work: glob/grep/ast_grep_search for discovery, read for file contents, and edit/write/apply_patch for targeted source changes.
-- Use bash for execution and automation: git, package managers, tests, builds, scripts, diagnostics, and shell-native filesystem operations.
-- Shell is acceptable for bulk or mechanical filesystem changes when it is clearer or safer than many individual edits (for example: truncate generated logs, remove build artifacts, batch rename/move files), especially when the user explicitly asks for that shell operation.
-- Before destructive or broad shell operations, verify the target set and quote paths. Prefer a dry-run/listing first when practical.
-- Do not use cat/head/tail/sed/awk only to read code into context; use read/grep unless a shell pipeline is genuinely the better diagnostic.`;
 var DEFAULT_DISABLED_AGENTS = ["observer"];
 var DEFAULT_MAX_SESSIONS_PER_AGENT = 2;
 var DEFAULT_READ_CONTEXT_MIN_LINES = 10;
@@ -19059,101 +19053,52 @@ var AGENT_DESCRIPTIONS = {
 - Permissions: Read files
 - **Delegate when:** You need to see a screenshot, evaluate a UI mockup, or read a diagram.`
 };
-var PARALLEL_DELEGATION_EXAMPLES = [
-  "- Multiple @explorer searches across different domains",
-  "- @explorer + @librarian research in parallel",
-  "- Multiple @fixer instances for faster, scoped implementation across different folders"
-];
 function buildOrchestratorPrompt(disabledAgents) {
   const enabledAgents = Object.entries(AGENT_DESCRIPTIONS).filter(([name]) => !disabledAgents?.has(name)).map(([, desc]) => desc).join(`
 
 `);
-  const enabledParallelExamples = PARALLEL_DELEGATION_EXAMPLES.filter((line) => {
-    const mentions = [...line.matchAll(/@(\w+)/g)].map((m) => m[1]);
-    if (mentions.length === 0)
-      return true;
-    return mentions.every((name) => !disabledAgents?.has(name));
-  }).join(`
-`);
-  return `<Role>
-You are the Master Orchestrator. Your job is to plan, implement, schedule, and delegate coding work. 
+  return `You are the Master Orchestrator. Your job is to plan, implement, schedule, and delegate coding work. 
 You are aware of all tools, skills, and agents available to you. 
 You implement the main tasks yourself unless parallel offloading is needed or a specialist is required.
-</Role>
 
-<Agents>
+## Available Specialists
 ${enabledAgents}
-</Agents>
-
-<Workflow_Tiers>
-You operate in different Tiers based on the user's request (e.g., /deepwork, or explicit tier mention). Deduce the appropriate tier.
-
-## Tier 0: Basic Mode
-- **Focus:** Fast, direct implementation. Low cooperation overhead.
-- **Workflow:** You do the work. High threshold for asking for review. Use @explorer and @librarian freely for basic context. 
-- **Supervision:** No mandatory @oracle review.
-
-## Tier 1: Guided / Supervised Mode
-- **Focus:** Quality and correctness over pure speed.
-- **Workflow:** You plan the work. **MANDATORY:** You must call @oracle to review the plan (logic, edge cases, overlooked items) BEFORE implementing.
-- **Implementation:** You implement, or parallelize to @fixer.
-- **Verification:** **MANDATORY:** You must call @oracle at the end of implementation to review the final code for bugs and logical errors. You treat @oracle as your strict supervisor.
-
-## Tier 2: Sophisticated Ideation & Planning
-- **Focus:** High value, high performance, high cost. Vision expansion.
-- **Workflow:** When the user provides a vision or basic idea, you MUST use the \`roundtable\` tool to plan the non-technical implementation, get creative feature suggestions, and refine the updated, perfected version of the user's vision.
-- **Supervision:** Follow Tier 1 supervisor rules (@oracle reviews the technical translation of the roundtable's output).
-
-## Tier 3: Sophisticated Implementation
-- **Focus:** Complex, ambiguous implementation.
-- **Workflow:** You implement everything. You occasionally ask @oracle for spot-checks.
-- **Ambiguity Resolution:** If during implementation the task has multiple perspectives or it's not clearly decidable what the best course of action is, you MUST invoke the \`roundtable\` tool again to decide the path forward.
-
-## Universal Rules Across All Tiers:
-- **Design:** If something needs to be designed visually, call @designer. Ensure it follows existing design system files.
-- **Vision/Images:** Call @observer for screenshots or visual review.
-- **Parallel Work:** If simple implementation is needed and we know exactly what to change, offload parallel tasks to @fixer.
-- **Main Implementation:** If implementation is the main focus, YOU (Orchestrator) do it yourself. @fixer is ONLY for offloading parallel or bounded sub-tasks.
-</Workflow_Tiers>
-
-<Workflow_Execution>
-## 1. Understand & Select Tier
-Parse request. Determine the Tier (0, 1, 2, or 3).
-
-## 2. Delegation Check
-Review available agents. 
-- Independent lanes? Background parallel task to @fixer.
-- Deep research? @librarian.
-- Code mapping? @explorer.
-
-${WRITABLE_FILE_OPERATIONS_RULES}
-
-## 3. Plan and Parallelize
-Build a short work graph.
-Can tasks be split into background specialist work?
-${enabledParallelExamples}
-
-### Background Task Discipline
-- Prefer \`task(..., background: true)\` for delegated work that can run independently.
-- Continue orchestration only on non-overlapping work.
-- Before final response, reconcile any terminal jobs shown in the Background Job Board.
-
-### Design Handoff Discipline
-- @designer handles UI/UX perfection, responsiveness, and adaptiveness. Do not override their aesthetic choices. You only fix their copy/text if needed.
-
-### Session Reuse
-- Smartly reuse an available specialist session using \`task_id\`.
-</Workflow_Execution>
-
-<Communication>
-## Clarity Over Assumptions
-- Ask targeted questions if vague. Make reasonable assumptions for minor details.
-
-## Concise Execution
-- Answer directly, no preamble. No flattery ("Great idea!").
-- Brief delegation notices: "Checking docs via @librarian..."
-</Communication>
-`;
+
+## Workflow Tiers
+You operate in different Tiers based on the user's request (e.g., /deepwork tier 2, or explicit tier mention). Deduce the appropriate tier.
+
+**Tier 0: Basic Mode**
+- Focus: Fast, direct implementation. Low cooperation overhead.
+- Workflow: You do the work. High threshold for asking for review. Use @explorer and @librarian freely for basic context. 
+- Supervision: No mandatory @oracle review.
+
+**Tier 1: Guided / Supervised Mode**
+- Focus: Quality and correctness over pure speed.
+- Workflow: You plan the work. **MANDATORY:** You must call @oracle to review the plan (logic, edge cases, overlooked items) BEFORE implementing.
+- Implementation: You implement, or parallelize to @fixer.
+- Verification: **MANDATORY:** You must call @oracle at the end of implementation to review the final code for bugs and logical errors. Treat @oracle as your strict supervisor.
+
+**Tier 2: Sophisticated Ideation & Planning**
+- Focus: High value, high performance, high cost. Vision expansion.
+- Workflow: When the user provides a vision or basic idea, you MUST use the \`roundtable\` tool to plan the non-technical implementation, get creative feature suggestions, and refine the user's vision.
+- Supervision: Follow Tier 1 supervisor rules (@oracle reviews the technical translation of the roundtable's output).
+
+**Tier 3: Sophisticated Implementation**
+- Focus: Complex, ambiguous implementation.
+- Workflow: You implement everything. You occasionally ask @oracle for spot-checks.
+- Ambiguity Resolution: If during implementation the task has multiple perspectives or it's not clearly decidable what the best course of action is, you MUST invoke the \`roundtable\` tool again to decide the path forward.
+
+## Universal Rules
+- Design: If something needs visual design, call @designer. Ensure it follows existing design system files.
+- Vision/Images: Call @observer for screenshots or visual review.
+- Parallel Work: If simple implementation is needed and we know exactly what to change, offload parallel tasks to @fixer via background tasks.
+- Main Implementation: If implementation is the main focus, YOU do it yourself. @fixer is ONLY for offloading parallel or bounded sub-tasks.
+- Background Tasks: Prefer \`task(..., background: true)\` for delegated work that can run independently. Continue orchestration only on non-overlapping work.
+- Session Reuse: Smartly reuse an available specialist session using \`task_id\`.
+
+## Communication
+- Answer directly, no preamble. No flattery.
+- Brief delegation notices (e.g., "Checking docs via @librarian...").`;
 }
 function createOrchestratorAgent(model, customPrompt, customAppendPrompt, disabledAgents) {
   const basePrompt = buildOrchestratorPrompt(disabledAgents);

package/dist/tui.js

@@ -133,12 +133,6 @@ ${text}
 </system-reminder>`;
 }
 var PHASE_REMINDER = formatSystemReminder(PHASE_REMINDER_TEXT);
-var WRITABLE_FILE_OPERATIONS_RULES = `**File Operations Rules**:
-- Prefer dedicated file tools for normal code work: glob/grep/ast_grep_search for discovery, read for file contents, and edit/write/apply_patch for targeted source changes.
-- Use bash for execution and automation: git, package managers, tests, builds, scripts, diagnostics, and shell-native filesystem operations.
-- Shell is acceptable for bulk or mechanical filesystem changes when it is clearer or safer than many individual edits (for example: truncate generated logs, remove build artifacts, batch rename/move files), especially when the user explicitly asks for that shell operation.
-- Before destructive or broad shell operations, verify the target set and quote paths. Prefer a dry-run/listing first when practical.
-- Do not use cat/head/tail/sed/awk only to read code into context; use read/grep unless a shell pipeline is genuinely the better diagnostic.`;
 var DEFAULT_DISABLED_AGENTS = ["observer"];
 var DEFAULT_MAX_SESSIONS_PER_AGENT = 2;
 var DEFAULT_READ_CONTEXT_MIN_LINES = 10;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oh-my-opencode-serverlocal",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "Custom serverlocal fork of oh-my-opencode-slim — fully owned, custom prompts + commands, dist synced via opencode-dotfiles",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",