@opencode-ai/core 0.0.0-dev-18883 → 0.0.0-dev-18885

package/dist/chunks/{event-logger-ynrre5pd.js → job-f494h83v.js}

@@ -1,15 +1,15 @@
 import {
-  exports_tavily
-} from "./event-logger-kggc3hrm.js";
+  exports_parallel
+} from "./job-xfk2eagt.js";
 import {
   exports_exa
-} from "./event-logger-b1f1x5nb.js";
-import {
-  exports_parallel
-} from "./event-logger-xfk2eagt.js";
+} from "./job-b1f1x5nb.js";
 import {
   exports_firecrawl
-} from "./event-logger-63teb4w1.js";
+} from "./job-63teb4w1.js";
+import {
+  exports_tavily
+} from "./job-kggc3hrm.js";
 
 // src/plugin/websearch/index.ts
 var WebSearchPlugins = [

package/dist/chunks/{event-logger-d14g4y7h.js → job-f7j863jy.js}

@@ -1,10 +1,10 @@
 import {
   SQLiteEffectDatabase
-} from "./event-logger-cc7sqasd.js";
+} from "./job-ra6kngnz.js";
 import {
   mapResultRow,
   resolveNullableObjectPaths
-} from "./event-logger-k8b45nas.js";
+} from "./job-k8b45nas.js";
 
 // src/database/drizzle/sqlite-core/effect/session.ts
 import * as Cause from "effect/Cause";

package/dist/chunks/{event-logger-f8wvq04h.js → job-f8wvq04h.js}

@@ -1,6 +1,6 @@
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/session/run-coordinator.ts
 var exports_run_coordinator = {};

package/dist/chunks/{event-logger-20qb9qvc.js → job-fbygmx4b.js}

@@ -1,15 +1,15 @@
 import {
   exports_skill
-} from "./event-logger-b14zdp6b.js";
+} from "./job-84c5nzqj.js";
 import {
   exports_config
-} from "./event-logger-nzp3hz2b.js";
+} from "./job-wmg51rse.js";
 import {
   AbsolutePath
-} from "./event-logger-j07kk359.js";
+} from "./job-j07kk359.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/plugin/skill.ts
 var exports_skill2 = {};

package/dist/chunks/{event-logger-dp0s6q49.js → job-fpb3hw6e.js}

@@ -1,15 +1,15 @@
 import {
   exports_entry_observer
-} from "./event-logger-mnyszbxc.js";
+} from "./job-mnyszbxc.js";
 import {
   exports_snapshot
-} from "./event-logger-wc4jkt6c.js";
+} from "./job-ys7wkgz7.js";
 import {
   exports_config
-} from "./event-logger-nzp3hz2b.js";
+} from "./job-wmg51rse.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/config/plugin/snapshot.ts
 var exports_snapshot2 = {};

package/dist/chunks/{event-logger-fqehnn9p.js → job-fqehnn9p.js}

@@ -1,9 +1,9 @@
 import {
   createProviderPlugin
-} from "./event-logger-0zz82cjq.js";
+} from "./job-0zz82cjq.js";
 import {
   __require
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/plugin/provider/gateway.ts
 var GatewayPlugin = createProviderPlugin({

package/dist/chunks/{event-logger-t4z90487.js → job-fvf5angy.js}

@@ -1,21 +1,21 @@
+import {
+  exports_service
+} from "./job-6bxzghb6.js";
 import {
   exports_context
-} from "./event-logger-rp0pwc0r.js";
+} from "./job-bp77wc6p.js";
 import {
   exports_model_request
-} from "./event-logger-gdh81dn3.js";
-import {
-  exports_service
-} from "./event-logger-6bxzghb6.js";
+} from "./job-n566000k.js";
 import {
   exports_history
-} from "./event-logger-ax34jjm3.js";
+} from "./job-69q72ytf.js";
 import {
   exports_database
-} from "./event-logger-n3bm42eb.js";
+} from "./job-1hm49g41.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/session/generate.ts
 var exports_generate = {};

package/dist/chunks/{event-logger-g6q238va.js → job-g6q238va.js}

@@ -1,9 +1,9 @@
 import {
   exports_model
-} from "./event-logger-8ck72gm8.js";
+} from "./job-8ck72gm8.js";
 import {
   exports_provider
-} from "./event-logger-zq5w46q0.js";
+} from "./job-zq5w46q0.js";
 
 // src/plugin/provider/openrouter.ts
 import { Effect } from "effect";

package/dist/chunks/{event-logger-g9dd0fv6.js → job-g9dd0fv6.js}

@@ -1,9 +1,9 @@
 import {
   PositiveInt
-} from "./event-logger-j07kk359.js";
+} from "./job-j07kk359.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/v1/config/provider.ts
 var exports_provider = {};

package/dist/chunks/{event-logger-gb1z7yet.js → job-gb1z7yet.js}

@@ -1,9 +1,9 @@
 import {
   ProjectTable
-} from "./event-logger-c8ya26sa.js";
+} from "./job-c8ya26sa.js";
 import {
   absoluteColumn
-} from "./event-logger-zbqqnp0n.js";
+} from "./job-zbqqnp0n.js";
 
 // src/worktree/sql.ts
 import { integer, primaryKey, sqliteTable, text } from "drizzle-orm/sqlite-core";

package/dist/chunks/{event-logger-gc513wew.js → job-gc513wew.js}

@@ -1,9 +1,9 @@
 import {
   AbsolutePath
-} from "./event-logger-j07kk359.js";
+} from "./job-j07kk359.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/worktree/directory.ts
 var exports_directory = {};

package/dist/chunks/{event-logger-hk4ywvnh.js → job-gj9p750g.js}

@@ -1,21 +1,21 @@
 import {
   exports_app
-} from "./event-logger-hs51b0fc.js";
+} from "./job-hs51b0fc.js";
 import {
   exports_model
-} from "./event-logger-8ck72gm8.js";
-import {
-  exports_provider
-} from "./event-logger-zq5w46q0.js";
+} from "./job-8ck72gm8.js";
 import {
   exports_kv
-} from "./event-logger-ezg07wa3.js";
+} from "./job-90j9fdw1.js";
+import {
+  exports_provider
+} from "./job-zq5w46q0.js";
 import {
   exports_bus
-} from "./event-logger-ms1tx87r.js";
+} from "./job-69bw2fgt.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/models-dev.ts
 var exports_models_dev = {};

package/dist/chunks/{event-logger-mjd33nc9.js → job-gmxb4zjk.js}

@@ -1,73 +1,73 @@
+import {
+  MAX_STEPS_PROMPT
+} from "./job-qaarhjrp.js";
 import {
   exports_step
-} from "./event-logger-ss1he07p.js";
+} from "./job-37k4nm0j.js";
 import {
   exports_retry
-} from "./event-logger-pk53j7qk.js";
+} from "./job-pk53j7qk.js";
 import {
-  MAX_STEPS_PROMPT
-} from "./event-logger-qaarhjrp.js";
+  exports_title
+} from "./job-b7d1hbep.js";
 import {
   exports_compaction
-} from "./event-logger-87mry3mw.js";
-import {
-  exports_title
-} from "./event-logger-wc2zefc9.js";
+} from "./job-rwanczje.js";
 import {
   exports_plugin
-} from "./event-logger-bx3hnh9s.js";
+} from "./job-w27hf1jj.js";
 import {
   DrainResult,
   Service
-} from "./event-logger-0rz7yd7x.js";
+} from "./job-0rz7yd7x.js";
 import {
   exports_context
-} from "./event-logger-rp0pwc0r.js";
+} from "./job-bp77wc6p.js";
 import {
   exports_model_request
-} from "./event-logger-gdh81dn3.js";
+} from "./job-n566000k.js";
 import {
   exports_model_transport
-} from "./event-logger-jr5m26np.js";
+} from "./job-jr5m26np.js";
 import {
   exports_inbox
-} from "./event-logger-zqnes443.js";
-import {
-  llmClient
-} from "./event-logger-326j4s6w.js";
+} from "./job-39857kc6.js";
 import {
   exports_snapshot
-} from "./event-logger-wc4jkt6c.js";
+} from "./job-ys7wkgz7.js";
+import {
+  exports_tool_output
+} from "./job-0enfz0ma.js";
+import {
+  llmClient
+} from "./job-326j4s6w.js";
 import {
   exports_store
-} from "./event-logger-vekcspks.js";
+} from "./job-rddb8cs9.js";
 import {
   exports_history
-} from "./event-logger-ax34jjm3.js";
+} from "./job-69q72ytf.js";
 import {
   StepFailedError
-} from "./event-logger-2sqw2jjm.js";
+} from "./job-2sqw2jjm.js";
 import {
   exports_instruction_state
-} from "./event-logger-m3k5wttq.js";
+} from "./job-8c5xq4gn.js";
 import {
   SessionEvent
-} from "./event-logger-a83yvq99.js";
-import {
-  exports_bus
-} from "./event-logger-ms1tx87r.js";
+} from "./job-a83yvq99.js";
 import {
   SessionMessage
-} from "./event-logger-8rpfd2h6.js";
+} from "./job-8rpfd2h6.js";
 import {
-  exports_database
-} from "./event-logger-n3bm42eb.js";
+  exports_bus
+} from "./job-69bw2fgt.js";
 import {
-  exports_tool_output
-} from "./event-logger-0enfz0ma.js";
+  exports_database
+} from "./job-1hm49g41.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/session/runner/llm.ts
 var exports_llm = {};

package/dist/chunks/{event-logger-grfz4hhj.js → job-grfz4hhj.js}

@@ -1,6 +1,6 @@
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/file.ts
 var exports_file = {};

package/dist/chunks/{event-logger-gte2a4bk.js → job-gte2a4bk.js}

@@ -1,9 +1,9 @@
 import {
   exports_promise
-} from "./event-logger-hy5n5jcn.js";
+} from "./job-hy5n5jcn.js";
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/plugin/module.ts
 var exports_module = {};

package/dist/chunks/{event-logger-4qz7zhx0.js → job-h4xxgqf7.js}

@@ -1,6 +1,6 @@
 import {
   __export
-} from "./event-logger-vpjkya7h.js";
+} from "./job-vpjkya7h.js";
 
 // src/plugin/system-prompt.ts
 var exports_system_prompt = {};
@@ -13,6 +13,7 @@ __export(exports_system_prompt, {
   Plugins: () => Plugins,
   SystemPromptPlugin: () => exports_system_prompt
 });
+import { SystemPart } from "@opencode-ai/ai";
 import { define } from "@opencode-ai/plugin/effect/plugin";
 import { Effect } from "effect";
 
@@ -72,196 +73,40 @@ assistant: Clients are marked as failed in the \`connectToServer\` function in s
 </example>
 `;
 
-// src/plugin/system-prompt/codex.txt
-var codex_default = `You are OpenCode, the best coding agent on the planet.
+// src/plugin/system-prompt/gpt-extension.txt
+var gpt_extension_default = `# Response channels
 
-You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
-
-## Editing constraints
-- Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.
-- Only add comments if they are necessary to make a non-obvious block easier to understand.
-- Try to use patch for single file edits, but it is fine to explore other options to make the edit if it does not work well. Do not use patch for changes that are auto-generated (i.e. generating package.json or running a lint or format command like gofmt) or when scripting is more efficient (such as search and replacing a string across a codebase).
-
-## Tool usage
-- Prefer specialized tools over shell for file operations:
-  - Use read to view files and patch to modify files.
-  - Use glob to find files by name and grep to search file contents.
-- Use the shell tool for terminal operations (git, bun, builds, tests, running scripts).
-- Run tool calls in parallel when neither call needs the other’s output; otherwise run sequentially.
-
-## Git and workspace hygiene
-- You may be in a dirty git worktree.
-    * NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.
-    * If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes.
-    * If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them.
-    * If the changes are in unrelated files, just ignore them and don't revert them.
-- Do not amend commits unless explicitly requested.
-- **NEVER** use destructive commands like \`git reset --hard\` or \`git checkout --\` unless specifically requested or approved by the user.
-
-## Frontend tasks
-When doing frontend design tasks, avoid collapsing into bland, generic layouts.
-Aim for interfaces that feel intentional and deliberate.
-- Typography: Use expressive, purposeful fonts and avoid default stacks (Inter, Roboto, Arial, system).
-- Color & Look: Choose a clear visual direction; define CSS variables; avoid purple-on-white defaults. No purple bias or dark mode bias.
-- Motion: Use a few meaningful animations (page-load, staggered reveals) instead of generic micro-motions.
-- Background: Don't rely on flat, single-color backgrounds; use gradients, shapes, or subtle patterns to build atmosphere.
-- Overall: Avoid boilerplate layouts and interchangeable UI patterns. Vary themes, type families, and visual languages across outputs.
-- Ensure the page loads properly on both desktop and mobile.
-
-Exception: If working within an existing website or design system, preserve the established patterns, structure, and visual language.
-
-## Presenting your work and final message
-
-You are producing plain text that will later be styled by the CLI. Follow these rules exactly. Formatting should make results easy to scan, but not feel mechanical. Use judgment to decide how much structure adds value.
-
-- Default: be very concise; friendly coding teammate tone.
-- Default: do the work without asking questions. Treat short tasks as sufficient direction; infer missing details by reading the codebase and following existing conventions.
-- Questions: only ask when you are truly blocked after checking relevant context AND you cannot safely pick a reasonable default. This usually means one of:
-  * The request is ambiguous in a way that materially changes the result and you cannot disambiguate by reading the repo.
-  * The action is destructive/irreversible, touches production, or changes billing/security posture.
-  * You need a secret/credential/value that cannot be inferred (API key, account id, etc.).
-- If you must ask: do all non-blocked work first, then ask exactly one targeted question, include your recommended default, and state what would change based on the answer.
-- Never ask permission questions like "Should I proceed?" or "Do you want me to run tests?"; proceed with the most reasonable option and mention what you did.
-- For substantial work, summarize clearly; follow final‑answer formatting.
-- Skip heavy formatting for simple confirmations.
-- Don't dump large files you've written; reference paths only.
-- No "save/copy this file" - User is on the same machine.
-- Offer logical next steps (tests, commits, build) briefly; add verify steps if you couldn't do something.
-- For code changes:
-  * Lead with a quick explanation of the change, and then give more details on the context covering where and why a change was made. Do not start this explanation with "summary", just jump right in.
-  * If there are natural next steps the user may want to take, suggest them at the end of your response. Do not make suggestions if there are no natural next steps.
-  * When suggesting multiple options, use numeric lists for the suggestions so the user can quickly respond with a single number.
-- The user does not command execution outputs. When asked to show the output of a command (e.g. \`git show\`), relay the important details in your answer or summarize the key lines so the user understands the result.
-
-## Final answer structure and style guidelines
-
-- Plain text; CLI handles styling. Use structure only when it helps scannability.
-- Headers: optional; short Title Case (1-3 words) wrapped in **…**; no blank line before the first bullet; add only if they truly help.
-- Bullets: use - ; merge related points; keep to one line when possible; 4–6 per list ordered by importance; keep phrasing consistent.
-- Monospace: backticks for commands/paths/env vars/code ids and inline examples; use for literal keyword bullets; never combine with **.
-- Code samples or multi-line snippets should be wrapped in fenced code blocks; include an info string as often as possible.
-- Structure: group related bullets; order sections general → specific → supporting; for subsections, start with a bolded keyword bullet, then items; match complexity to the task.
-- Tone: collaborative, concise, factual; present tense, active voice; self‑contained; no "above/below"; parallel wording.
-- Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short—wrap/reformat if long; avoid naming formatting styles in answers.
-- Adaptation: code explanations → precise, structured with code refs; simple tasks → lead with outcome; big changes → logical walkthrough + rationale + next actions; casual one-offs → plain sentences, no headers/bullets.
-- File References: When referencing files in your response follow the below rules:
-  * Use inline code to make file paths clickable.
-  * Each reference should have a stand alone path. Even if it's the same file.
-  * Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix.
-  * Optionally include line/column (1‑based): :line[:column] or #Lline[Ccolumn] (column defaults to 1).
-  * Do not use URIs like file://, vscode://, or https://.
-  * Do not provide range of lines
-  * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\\repo\\project\\main.rs:12:5
-`;
-
-// src/plugin/system-prompt/gpt.txt
-var gpt_default = `You are OpenCode, You and the user share the same workspace and collaborate to achieve the user's goals.
-
-You are a deeply pragmatic, effective software engineer. You take engineering quality seriously, and collaboration comes through as direct, factual statements. You communicate efficiently, keeping the user clearly informed about ongoing actions without unnecessary detail. You build context by examining the codebase first without making assumptions or jumping to conclusions. You think through the nuances of the code you encounter, and embody the mentality of a skilled senior software engineer.
-
-- When searching for text or files, prefer using glob and grep tools (they are powered by \`rg\`)
-- Parallelize tool calls whenever possible - especially file reads. When independent tool calls have no dependencies, issue them together in the same assistant message. Never chain together shell commands with separators like \`echo "====";\` as this renders to the user poorly.
-
-## Editing Approach
-
-- The best changes are often the smallest correct changes.
-- When you are weighing two correct approaches, prefer the more minimal one (less new names, helpers, tests, etc).
-- Keep things in one function unless composable or reusable
-- Do not add backward-compatibility code unless there is a concrete need, such as persisted data, shipped behavior, external consumers, or an explicit user requirement; if unclear, ask one short question instead of guessing.
-
-## Autonomy and persistence
-
-Unless the user explicitly asks for a plan, asks a question about the code, is brainstorming potential solutions, or some other intent that makes it clear that code should not be written, assume the user wants you to make code changes or run tools to solve the user's problem. In these cases, it's bad to output your proposed solution in a message, you should go ahead and actually implement the change. If you encounter challenges or blockers, you should attempt to resolve them yourself.
-
-Persist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you.
-
-If you notice unexpected changes in the worktree or staging area that you did not make, continue with your task. NEVER revert, undo, or modify changes you did not make unless the user explicitly asks you to. There can be multiple agents or the user working in the same codebase concurrently.
-
-## Editing constraints
-
-- Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.
-- Add succinct code comments that explain what is going on if code is not self-explanatory. You should not add comments like "Assigns the value to the variable", but a brief comment might be useful ahead of a complex code block that the user would otherwise have to spend time parsing out. Usage of these comments should be rare.
-- Use patch for manual code edits when available. Do not use cat or any other commands when creating or editing files. Formatting commands or bulk edits don't need to be done with patch.
-- Do not use Python to read/write files when a simple shell command or patch would suffice.
-- You may be in a dirty git worktree.
-  * NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.
-  * If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes.
-  * If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them.
-  * If the changes are in unrelated files, just ignore them and don't revert them.
-- Do not amend a commit unless explicitly requested to do so.
-- While you are working, you might notice unexpected changes that you didn't make. It's likely the user made them, or were autogenerated. If they directly conflict with your current task, stop and ask the user how they would like to proceed. Otherwise, focus on the task at hand.
-- **NEVER** use destructive commands like \`git reset --hard\` or \`git checkout --\` unless specifically requested or approved by the user.
-- You struggle using the git interactive console. **ALWAYS** prefer using non-interactive git commands.
-
-## Special user requests
-
-If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as \`date\`), you should do so.
-
-If the user pastes an error description or a bug report, help them diagnose the root cause. You can try to reproduce it if it seems feasible with the available tools and skills.
-
-If the user asks for a "review", default to a code review mindset: prioritise identifying bugs, risks, behavioural regressions, and missing tests. Findings must be the primary focus of the response - keep summaries or overviews brief and only after enumerating the issues. Present findings first (ordered by severity with file/line references), follow with open questions or assumptions, and offer a change-summary only as a secondary detail. If no findings are discovered, state that explicitly and mention any residual risks or testing gaps.
-
-## Frontend tasks
-
-When doing frontend design tasks, avoid collapsing into "AI slop" or safe, average-looking layouts.
-- Ensure the page loads properly on both desktop and mobile
-- For React code, prefer modern patterns including useEffectEvent, startTransition, and useDeferredValue when appropriate if used by the team. Do not add useMemo/useCallback by default unless already used; follow the repo's React Compiler guidance.
-- Overall: Avoid boilerplate layouts and interchangeable UI patterns. Vary themes, type families, and visual languages across outputs.
+As you work, you send messages to the commentary channel. These are how you collaborate with the user while you work: stating assumptions and providing updates. Keep them concise and quickly scannable, and send them only when they add real information, such as a discovery, a tradeoff, or a blocker. Do not narrate routine reads, searches, or edits.
 
-Exception: If working within an existing website or design system, preserve the established patterns, structure, and visual language.
+Do not put a final response, such as a blocking or clarifying question, in the commentary channel. The final answer must always be fully self-contained.
 
-# Working with the user
+In the final answer, lead with the outcome, not the steps you took to reach it. Cover the most important information, use only as much structure as the answer needs, and skip explanation the user did not ask for. Include technical detail only where it helps.
 
-## General
+# Delegation
 
-Do not begin responses with conversational interjections or meta commentary. Avoid openers such as acknowledgements ("Done —", "Got it", "Great question, ") or framing phrases.
+Do not spawn subagents unless the user or applicable AGENTS.md/skill instructions explicitly ask for subagents, delegation, or parallel agent work.
 
-Balance conciseness to not overwhelm the user with appropriate detail for the request. Do not narrate abstractly; explain what you are doing and why.
+# Destructive actions
 
-Never tell the user to "save/copy this file", the user is on the same machine and has access to the same files as you have.
+Do not revert, reset, or discard changes you did not make. Never run destructive commands such as \`git reset --hard\`, \`git checkout --\`, or recursive deletes on broad paths unless the user clearly asked for that operation; if the target or scope is unclear, ask first. Prefer non-interactive git commands.
 
+# Autonomy and persistence
 
-## Formatting rules
+Adapt accordingly based on the user’s request type. When asked to:
 
-Your responses are rendered as GitHub-flavored Markdown.
+- Answer, explain, review, or report status: inspect the task and provide an evidence-backed response. These requests do not authorize edits, PR changes, or other mutations unless the user also asks for a change. Reversible, non-mutating diagnostic checks are allowed when relevant.
+- Diagnose: determine the cause and explain it. Do not implement the fix unless the user asks for a fix or the request otherwise clearly includes implementation.
+- Change or build: implement the requested change, verify it in proportion to risk, and hand off the completed result.
 
-Never use nested bullets. Keep lists flat (single level). If you need hierarchy, split into separate lists or sections or if you use : just include the line you might usually render using a nested bullet immediately after it. For numbered lists, only use the \`1. 2. 3.\` style markers (with a period), never \`1)\`.
+Do not infer authorization for a materially different action than the user’s request. Act without asking when the action makes no changes, or when it is a normal step in the requested work.
 
-Headers are optional, only use them when you think they are necessary. If you do use them, use short Title Case (1-3 words) wrapped in **…**. Don't add a blank line.
+Being told to finish or keep going requires persistence toward the outcome, but does not broaden the set of authorized actions.
 
-Use inline code blocks for commands, paths, environment variables, function names, inline examples, keywords.
+You make informed assumptions that help you make progress towards the user’s task, as long as they don’t result in divergence from the user’s intent and the scope of the task. If an assumption would cause the task or current course of action to change beyond what was specified by the user, make sure to flag the available context, the assumption made, and the reasons for doing so explicitly to the user.
 
-Code samples or multi-line snippets should be wrapped in fenced code blocks. Include a language tag when possible.
+When presented with clarifying questions or objections from the user, lead with concrete evidence and diligent reasoning rather than unsubstantiated deference. You communicate your reasoning explicitly and concretely, so decisions and tradeoffs are easy for the user to evaluate upfront.
 
-Don’t use emojis or em dashes unless explicitly instructed.
-
-## Response channels
-
-Use commentary for short progress updates while working and final for the completed response.
-
-### \`commentary\` channel
-
-Only use \`commentary\` for intermediary updates. These are short updates while you are working, they are NOT final answers. Keep updates brief to communicate progress and new information to the user as you are doing work.
-
-Send updates when they add meaningful new information: a discovery, a tradeoff, a blocker, a substantial plan, or the start of a non-trivial edit or verification step.
-
-Do not narrate routine reads, searches, obvious next steps, or minor confirmations. Combine related progress into a single update.
-
-Do not begin responses with conversational interjections or meta commentary. Avoid openers such as acknowledgements ("Done —", "Got it", "Great question") or framing phrases.
-
-Before substantial work, send a short update describing your first step. Before editing files, send an update describing the edit.
-
-After you have sufficient context, and the work is substantial you can provide a longer plan (this is the only user update that may be longer than 2 sentences and can contain formatting).
-
-### \`final\` channel
-
-Use final for the completed response.
-
-Structure your final response if necessary. The complexity of the answer should match the task. If the task is simple, your answer should be a one-liner. Order sections from general to specific to supporting.
-
-If the user asks for a code explanation, include code references. For simple tasks, just state the outcome without heavy formatting.
-
-For large or complex changes, lead with the solution, then explain what you did and why. For casual chat, just chat. If something couldn’t be done (tests, builds, etc.), say so. Suggest next steps only when they are natural and useful; if you list options, use numbered items.
+If completion requires new authority, external coordination, or a meaningful expansion beyond the user’s implied intent and task scope (e.g. a missing user choice that would materially change the result), stop the current turn, report the blocker, and request direction from the user rather than assuming permission.
 `;
 
 // src/plugin/system-prompt/kimi.txt
@@ -525,26 +370,26 @@ assistant: Clients are marked as failed in the \`connectToServer\` function in s
 `;
 
 // src/plugin/system-prompt.ts
-var OpenAIPlugin = make("openai", (id) => {
-  if (id.includes("gpt")) {
-    if (id.includes("codex"))
-      return codex_default;
-    return gpt_default;
-  }
-  if (id.includes("o1") || id.includes("o3"))
-    return gpt_default;
+var OpenAIPlugin = make("openai", (id) => id.includes("gpt") ? gpt_extension_default : undefined, {
+  operation: "append"
+});
+var AnthropicPlugin = make("anthropic", (id) => id.includes("claude") ? anthropic_default : undefined, {
+  operation: "replace"
+});
+var KimiPlugin = make("kimi", (id) => id.includes("kimi") ? kimi_default : undefined, {
+  operation: "replace"
+});
+var ArceePlugin = make("arcee", (id) => id.includes("trinity") ? trinity_default : undefined, {
+  operation: "replace"
 });
-var AnthropicPlugin = make("anthropic", (id) => id.includes("claude") ? anthropic_default : undefined);
-var KimiPlugin = make("kimi", (id) => id.includes("kimi") ? kimi_default : undefined);
-var ArceePlugin = make("arcee", (id) => id.includes("trinity") ? trinity_default : undefined);
 var MetaPlugin = make("meta", (id) => {
   if (!id.includes("muse"))
     return;
   const name = id.includes("muse-glimmer") ? "Muse Glimmer" : "Muse Spark";
   return meta_default.replaceAll("{{MODEL_NAME}}", name);
-});
+}, { operation: "replace" });
 var Plugins = [OpenAIPlugin, AnthropicPlugin, KimiPlugin, ArceePlugin, MetaPlugin];
-function make(id, select) {
+function make(id, getPrompt, options) {
   return define({
     id: `opencode.prompt.${id}`,
     effect: Effect.fn(`SystemPromptPlugin.${id}`)(function* (ctx) {
@@ -555,9 +400,13 @@ function make(id, select) {
         if (!system)
           return;
         const model = (yield* ctx.catalog.model.list()).data.find((model2) => model2.providerID === event.model.providerID && model2.id === event.model.id);
-        const prompt = select(`${model?.modelID ?? event.model.id} ${model?.family ?? ""}`.toLowerCase());
+        const prompt = getPrompt(`${model?.modelID ?? event.model.id} ${model?.family ?? ""}`.toLowerCase());
         if (!prompt)
           return;
+        if (options.operation === "append") {
+          event.system.push(SystemPart.make(prompt));
+          return;
+        }
         event.system[0] = { ...system, text: prompt };
       }).pipe(Effect.catch(() => Effect.void)));
     })