opencodekit 0.19.4 → 0.19.5

package/dist/index.js

@@ -20,7 +20,7 @@ var __require = /* @__PURE__ */ createRequire(import.meta.url);
 
 //#endregion
 //#region package.json
-var version = "0.19.4";
+var version = "0.19.5";
 
 //#endregion
 //#region src/utils/license.ts

package/dist/template/.opencode/agent/vision.md

@@ -71,7 +71,7 @@ Route by need:
 | Mockup-to-implementation mapping              | `mockup-to-code`      |
 | Distinctive UI direction / anti-slop guidance | `frontend-design`     |
 | Figma design data (read/write via MCP)        | `figma-go`            |
-| Pencil design-as-code workflow                | `pencil`              |
+| OpenPencil design-as-code workflow            | `pencil`              |
 | Brand identity extraction from URLs           | `webclaw`             |
 
 ### Taste-Skill Variants (installed)
@@ -108,12 +108,12 @@ If Figma is available, request MCP access via `figma-go` and ground feedback in
 2. Use `figma-go` to pull `get_design_context` or `get_node`
 3. Reference node IDs in findings for traceability
 
-## Pencil-First Workflow (when no Figma)
+## OpenPencil Workflow (when no Figma)
 
-If design must be created or iterated quickly, use Pencil:
+If design must be created or iterated quickly, use OpenPencil via the legacy `pencil` skill:
 
-1. Create/modify `.pen` via Pencil CLI
-2. Export PNGs for review
+1. Create/modify `.op` via `op` CLI
+2. Export PNGs or code for review
 3. Provide audit with node-level critique where possible
 
 ## Brand Extraction Workflow (when auditing existing sites)

package/dist/template/.opencode/dcp-prompts/defaults/compress-message.md

@@ -8,6 +8,7 @@ When a selected message contains user intent, preserve that intent with extra ca
 Directly quote short user instructions when that best preserves exact meaning.
 
 Yet be LEAN. Strip away the noise: failed attempts that led nowhere, verbose tool output, and repetition. What remains should be pure signal - golden nuggets of detail that preserve full understanding with zero ambiguity.
+If a message contains no significant technical decisions, code changes, or user requirements, produce a minimal one-line summary rather than a detailed one.
 
 MESSAGE IDS
 You specify individual raw messages by ID using the injected IDs visible in the conversation:
@@ -15,9 +16,10 @@ You specify individual raw messages by ID using the injected IDs visible in the
 - `mNNNN` IDs identify raw messages
 
 Each message has an ID inside XML metadata tags like `<dcp-message-id priority="high">m0007</dcp-message-id>`.
-The ID tag appears at the end of the message it belongs to — each ID covers all the content above it back to the previous ID.
+The same ID tag appears in every tool output of the message it belongs to — each unique ID identifies one complete message.
 Treat these tags as message metadata only, not as content to summarize. Use only the inner `mNNNN` value as the `messageId`.
-The `priority` attribute indicates relative context cost. Prefer higher-priority closed messages before lower-priority ones.
+The `priority` attribute indicates relative context cost. You MUST compress high-priority messages when their full text is no longer necessary for the active task.
+If prior compress-tool results are present, always compress and summarize them minimally only as part of a broader compression pass. Do not invoke the compress tool solely to re-compress an earlier compression result.
 Messages marked as `<dcp-message-id>BLOCKED</dcp-message-id>` cannot be compressed.
 
 Rules:
@@ -25,18 +27,15 @@ Rules:
 - Pick each `messageId` directly from injected IDs visible in context.
 - Only use raw message IDs of the form `mNNNN`.
 - Ignore XML attributes such as `priority` when copying the ID; use only the inner `mNNNN` value.
-- Do NOT use compressed block IDs like `bN`.
 - Do not invent IDs. Use only IDs that are present in context.
-- Do not target prior compressed blocks or block summaries.
 
 BATCHING
-Select MANY messages in a single tool call when they are independently safe to compress.
+Select MANY messages in a single tool call when they are safe to compress.
 Each entry should summarize exactly one message, and the tool can receive as many entries as needed in one batch.
-When several messages are equally safe to compress, prefer higher-priority messages first.
 
-Because each message is compressed independently:
-
-- Do not describe ranges
-- Do not use start/end boundaries
-- Do not use compressed block placeholders
-- Do not reference prior compressed blocks with `(bN)`
+GENERAL CLEANUP
+Use the topic "general cleanup" for broad cleanup passes.
+During general cleanup, compress all medium and high-priority messages that are not relevant to the active task.
+Optimize for reducing context footprint, not for grouping messages by topic.
+Do not compress away still-active instructions, unresolved questions, or constraints that are likely to matter soon.
+Prioritize the earliest messages in the context as they will be the least relevant to the active task.

package/dist/template/.opencode/dcp-prompts/defaults/compress-range.md

@@ -45,7 +45,7 @@ You specify boundaries by ID using the injected IDs visible in the conversation:
 - `bN` IDs identify previously compressed blocks
 
 Each message has an ID inside XML metadata tags like `<dcp-message-id>...</dcp-message-id>`.
-The ID tag appears at the end of the message it belongs to — each ID covers all the content above it back to the previous ID.
+The same ID tag appears in every tool output of the message it belongs to — each unique ID identifies one complete message.
 Treat these tags as boundary metadata only, not as tool result content.
 
 Rules:

package/dist/template/.opencode/dcp-prompts/defaults/context-limit-nudge.md

@@ -6,16 +6,10 @@ You MUST use the `compress` tool now. Do not continue normal exploration until c
 
 If you are in the middle of a critical atomic operation, finish that atomic step first, then compress immediately.
 
-RANGE STRATEGY (MANDATORY)
-Prioritize one large, closed, high-yield compression range first.
-This overrides the normal preference for many small compressions.
-Only split into multiple compressions if one large range would reduce summary quality or make boundary selection unsafe.
-
-RANGE SELECTION
+SELECTION PROCESS
 Start from older, resolved history and capture as much stale context as safely possible in one pass.
-Avoid the newest active working slice unless it is clearly closed.
-Use visible injected boundary IDs for compression (`mNNNN` for messages, `bN` for compressed blocks), and ensure `startId` appears before `endId`.
+Avoid the newest active working messages unless it is clearly closed.
 
 SUMMARY REQUIREMENTS
-Your summary must cover all essential details from the selected range so work can continue without reopening raw messages.
+Your summary MUST cover all essential details from the selected messages so work can continue.
 If the compressed range includes user messages, preserve user intent exactly. Prefer direct quotes for short user messages to avoid semantic drift.

package/dist/template/.opencode/dcp-prompts/defaults/iteration-nudge.md

@@ -1,5 +1,3 @@
 You've been iterating for a while after the last user message.
 
 If there is a closed portion that is unlikely to be referenced immediately (for example, finished research before implementation), use the compress tool on it now.
-
-Prefer multiple short, closed ranges over one large range when several independent slices are ready.

package/dist/template/.opencode/dcp-prompts/defaults/system.md

@@ -9,19 +9,6 @@ THE PHILOSOPHY OF COMPRESS
 
 Think of compression as phase transitions: raw exploration becomes refined understanding. The original context served its purpose; your summary now carries that understanding forward.
 
-OPERATING STANCE
-Prefer short, closed, summary-safe compressions.
-When multiple independent stale sections exist, prefer several focused compressions (in parallel when possible) over one broad compression.
-
-Use `compress` as steady housekeeping while you work.
-
-CADENCE, SIGNALS, AND LATENCY
-
-- No fixed threshold mandates compression
-- Prioritize closedness and independence over raw size
-- Prefer smaller, regular compressions over infrequent massive compressions for better latency and summary quality
-- When multiple independent stale sections are ready, batch compressions in parallel
-
 COMPRESS WHEN
 
 A section is genuinely closed and the raw conversation has served its purpose:

package/dist/template/.opencode/dcp-prompts/defaults/turn-nudge.md

@@ -1,8 +1,7 @@
 Evaluate the conversation for compressible ranges.
 
-If any range is cleanly closed and unlikely to be needed again, use the compress tool on it.
+If any messages are cleanly closed and unlikely to be needed again, use the compress tool on them.
 If direction has shifted, compress earlier ranges that are now less relevant.
 
-Prefer small, closed-range compressions over one broad compression.
 The goal is to filter noise and distill key information so context accumulation stays under control.
 Keep active context uncompressed.

package/dist/template/.opencode/dcp.jsonc

@@ -53,7 +53,10 @@
 			"github-copilot/claude-sonnet-4.6": 192000,
 			"github-copilot/claude-sonnet-4.5": 192000,
 			"github-copilot/claude-sonnet-4": 192000,
-			"github-copilot/claude-haiku-4.5": 172000
+			"github-copilot/claude-haiku-4.5": 172000,
+			"github-copilot/gpt-5.4": 192000,
+			"github-copilot/gpt-5.3-codex": 192000,
+			"github-copilot/gemini-3.1-pro-preview": 192000
 		},
 		// Soft lower threshold: below this, turn/iteration reminders are off
 		"minContextLimit": "35%",
@@ -64,7 +67,10 @@
 			"github-copilot/claude-sonnet-4.6": "35%",
 			"github-copilot/claude-sonnet-4.5": "35%",
 			"github-copilot/claude-sonnet-4": "35%",
-			"github-copilot/claude-haiku-4.5": "25%"
+			"github-copilot/claude-haiku-4.5": "25%",
+			"github-copilot/gpt-5.4": "30%",
+			"github-copilot/gpt-5.3-codex": "30%",
+			"github-copilot/gemini-3.1-pro-preview": "30%"
 		},
 		// How often context-limit nudge fires above maxContextLimit (1 = every fetch)
 		"nudgeFrequency": 5,

package/dist/template/.opencode/opencode.json

@@ -106,22 +106,16 @@
       "timeout": 120000,
       "type": "local"
     },
-    "pencil": {
-      "command": [
-        "/Applications/Pencil.app/Contents/Resources/app.asar.unpacked/out/mcp-server-darwin-arm64",
-        "--app",
-        "desktop"
-      ],
-      "enabled": true,
-      "environment": {},
-      "timeout": 120000,
-      "type": "local"
-    },
     "webclaw": {
       "command": ["webclaw-mcp"],
       "enabled": true,
       "timeout": 120000,
       "type": "local"
+    },
+    "pencil": {
+      "command": ["openpencil-mcp"],
+      "enabled": false,
+      "type": "local"
     }
   },
   "model": "opencode/minimax-m2.5-free",

package/dist/template/.opencode/skill/pencil/SKILL.md

@@ -1,68 +1,72 @@
 ---
 name: pencil
-description: Pencil design-as-code workflow (CLI + MCP). Create/edit .pen files and export visuals.
+description: OpenPencil design-as-code workflow (legacy skill name: pencil). Create/edit .op files, export code, and use desktop-bundled MCP.
 version: 1.0.0
-tags: [design, pencil, mcp, cli]
+tags: [design, openpencil, mcp, cli]
 mcp:
   pencil:
-    command: /Applications/Pencil.app/Contents/Resources/app.asar.unpacked/out/mcp-server-darwin-arm64
-    args: ["--app", "desktop"]
+    command: openpencil-mcp
 ---
 
-# Pencil Skill
+# OpenPencil Skill
+
+Legacy skill name: `pencil`.
 
 ## When to Use
 
-- Create or modify UI designs as code using `.pen` files.
-- Export PNG/JPEG/WEBP/PDF for review or handoff.
-- Run headless, scriptable design changes via CLI/MCP tools.
+- Create or modify UI designs as code using `.op` files.
+- Export production code or visuals from the terminal.
+- Use OpenPencil's desktop-bundled MCP server after installing the app.
 
 ## Prerequisites
 
 ### Install CLI
 
 ```bash
-npm install -g @pencil.dev/cli
-pencil version
+npm install -g @zseven-w/openpencil
+op status
 ```
 
-### Authenticate
+### Install Desktop App for MCP
 
-```bash
-pencil login
-```
+- Install the OpenPencil desktop app from the ZSeven-W/openpencil releases page.
+- Open **Agent Settings** inside OpenPencil and use the one-click MCP install for OpenCode/Claude Code/Codex/etc.
+- The npm CLI install does **not** provide `openpencil-mcp`; that binary is bundled with the desktop app.
 
 ### MCP Server
 
-- Starts automatically when Pencil runs (extension or desktop).
-- Verify in Cursor: Settings → Tools & MCP.
-- In Codex CLI: run Pencil first, then `/mcp`.
+- OpenPencil ships a built-in MCP server for agent tooling.
+- The server command is `openpencil-mcp` once the desktop app has installed/exposed it.
+- Keep MCP disabled in template config until OpenPencil desktop is installed locally.
 
 ## Quick Start
 
 ```bash
 # Create new design
-pencil --out design.pen --prompt "Create a login page with email, password, CTA"
+op design @landing.txt
 
-# Modify existing design
-pencil --in design.pen --out design-v2.pen --prompt "Add a sidebar nav"
+# Start the desktop app
+op start
 
-# Export to image
-pencil --in design.pen --export design.png --export-scale 2
+# Export code
+op export react --out .
 
-# Interactive MCP shell
-pencil interactive -o design.pen
+# Import a Figma file
+op import:figma design.fig
 ```
 
-## Core MCP Tools (examples)
+## Core CLI Commands
 
-- `get_editor_state({ include_schema: true })`
-- `get_guidelines()`
-- `batch_design({ operations: "..." })`
-- `get_screenshot({ nodeId: "..." })`
-- `export_nodes({ nodeIds: ["..."], format: "png" })`
+- `op design @brief.txt`
+- `op design:skeleton`
+- `op design:content`
+- `op design:refine --root-id <id>`
+- `op export react --out .`
+- `op import:figma design.fig`
 
 ## Notes
 
-- Pencil uses `.pen` files as the source of truth.
-- Use taste-skill for design quality, Pencil for execution.
+- OpenPencil uses `.op` files as the source of truth.
+- CLI install is published on npm as `@zseven-w/openpencil` and exposes the `op` binary.
+- MCP is a desktop-app-bundled feature, not a standalone npm package.
+- Use taste-skill for design quality, OpenPencil for execution.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "opencodekit",
-	"version": "0.19.4",
+	"version": "0.19.5",
 	"description": "CLI tool for bootstrapping and managing OpenCodeKit projects",
 	"keywords": [
 		"agents",