opencode-hashline 1.0.0

package/dist/utils.d.cts

@@ -0,0 +1,74 @@
+import { H as HashlineConfig, e as HashlineCache } from './hashline-Civwirvf.cjs';
+export { D as DEFAULT_CONFIG, f as DEFAULT_EXCLUDE_PATTERNS, g as DEFAULT_PREFIX, a as HashEditInput, b as HashEditOperation, c as HashEditResult, d as HashlineInstance, R as ResolvedRange, V as VerifyHashResult, h as applyHashEdit, i as buildHashMap, j as computeLineHash, k as createHashline, l as formatFileWithHashes, m as getAdaptiveHashLength, n as getByteLength, o as matchesGlob, p as normalizeHashRef, q as parseHashRef, r as replaceRange, s as resolveConfig, t as resolveRange, u as shouldExclude, v as stripHashes, w as verifyHash } from './hashline-Civwirvf.cjs';
+import { Hooks } from '@opencode-ai/plugin';
+
+/**
+ * OpenCode plugin hooks for Hashline.
+ *
+ * - `onFileReadAfter`: Injects hashline annotations into file-read tool output
+ *   so the AI model sees content-addressable line references.
+ * - `onFileEditBefore`: Strips hashline prefixes from the AI's edit arguments
+ *   before they are applied to the actual file.
+ */
+
+/**
+ * Check if a tool input looks like a file-reading tool.
+ * Matches by tool name OR by presence of path-like args.
+ *
+ * NOTE: This is a fallback heuristic. The OpenCode plugin API (as of v1.2.2)
+ * does not expose a semantic tool category (e.g. "read" vs "write") in the
+ * hook input. If a future API version provides an explicit tool type or
+ * category field, prefer that over this name-based detection.
+ *
+ * ### How tool name matching works:
+ *
+ * 1. **Exact match** — tool name (lowercased) is compared against the allow-list:
+ *    `read`, `file_read`, `read_file`, `cat`, `view`.
+ *
+ * 2. **Dotted suffix match** — for namespaced tools like `mcp.read` or
+ *    `custom_provider.file_read`, the part after the last `.` is matched.
+ *
+ * 3. **Fallback heuristic** — if the tool has `path`, `filePath`, or `file`
+ *    arguments AND the tool name does NOT contain write/edit/execute indicators
+ *    (`write`, `edit`, `patch`, `execute`, `run`, `command`, `shell`, `bash`),
+ *    it is treated as a file-read tool.
+ *
+ * ### How to customize:
+ *
+ * If your custom tool is not detected, you can either:
+ * - Name it to match one of the patterns above (e.g. `my_read_file`)
+ * - Include `path`/`filePath`/`file` in its arguments
+ * - Or extend the FILE_READ_TOOLS list in a fork
+ */
+declare function isFileReadTool(toolName: string, args?: Record<string, unknown>): boolean;
+/**
+ * Create the `tool.execute.after` hook.
+ *
+ * When a file-read tool completes, this hook annotates the output
+ * with hashline prefixes so the AI can reference lines precisely.
+ *
+ * @param cache - optional LRU cache for annotated content
+ * @param config - resolved hashline configuration
+ */
+declare function createFileReadAfterHook(cache?: HashlineCache, config?: Required<HashlineConfig>): NonNullable<Hooks["tool.execute.after"]>;
+/**
+ * Create the `tool.execute.before` hook.
+ *
+ * When a file-edit tool is about to execute, this hook strips any
+ * hashline prefixes from the content arguments so the edits apply
+ * cleanly to the original file.
+ *
+ * @param config - resolved hashline configuration
+ */
+declare function createFileEditBeforeHook(config?: Required<HashlineConfig>): NonNullable<Hooks["tool.execute.before"]>;
+/**
+ * Create the system prompt injection hook.
+ *
+ * Adds detailed instructions to the system prompt explaining the hashline format,
+ * edit operations, and hash verification rules so the AI model can use them precisely.
+ *
+ * @param config - resolved hashline configuration
+ */
+declare function createSystemPromptHook(config?: Required<HashlineConfig>): NonNullable<Hooks["experimental.chat.system.transform"]>;
+
+export { HashlineCache, HashlineConfig, createFileEditBeforeHook, createFileReadAfterHook, createSystemPromptHook, isFileReadTool };

package/dist/utils.d.ts

@@ -0,0 +1,74 @@
+import { H as HashlineConfig, e as HashlineCache } from './hashline-Civwirvf.js';
+export { D as DEFAULT_CONFIG, f as DEFAULT_EXCLUDE_PATTERNS, g as DEFAULT_PREFIX, a as HashEditInput, b as HashEditOperation, c as HashEditResult, d as HashlineInstance, R as ResolvedRange, V as VerifyHashResult, h as applyHashEdit, i as buildHashMap, j as computeLineHash, k as createHashline, l as formatFileWithHashes, m as getAdaptiveHashLength, n as getByteLength, o as matchesGlob, p as normalizeHashRef, q as parseHashRef, r as replaceRange, s as resolveConfig, t as resolveRange, u as shouldExclude, v as stripHashes, w as verifyHash } from './hashline-Civwirvf.js';
+import { Hooks } from '@opencode-ai/plugin';
+
+/**
+ * OpenCode plugin hooks for Hashline.
+ *
+ * - `onFileReadAfter`: Injects hashline annotations into file-read tool output
+ *   so the AI model sees content-addressable line references.
+ * - `onFileEditBefore`: Strips hashline prefixes from the AI's edit arguments
+ *   before they are applied to the actual file.
+ */
+
+/**
+ * Check if a tool input looks like a file-reading tool.
+ * Matches by tool name OR by presence of path-like args.
+ *
+ * NOTE: This is a fallback heuristic. The OpenCode plugin API (as of v1.2.2)
+ * does not expose a semantic tool category (e.g. "read" vs "write") in the
+ * hook input. If a future API version provides an explicit tool type or
+ * category field, prefer that over this name-based detection.
+ *
+ * ### How tool name matching works:
+ *
+ * 1. **Exact match** — tool name (lowercased) is compared against the allow-list:
+ *    `read`, `file_read`, `read_file`, `cat`, `view`.
+ *
+ * 2. **Dotted suffix match** — for namespaced tools like `mcp.read` or
+ *    `custom_provider.file_read`, the part after the last `.` is matched.
+ *
+ * 3. **Fallback heuristic** — if the tool has `path`, `filePath`, or `file`
+ *    arguments AND the tool name does NOT contain write/edit/execute indicators
+ *    (`write`, `edit`, `patch`, `execute`, `run`, `command`, `shell`, `bash`),
+ *    it is treated as a file-read tool.
+ *
+ * ### How to customize:
+ *
+ * If your custom tool is not detected, you can either:
+ * - Name it to match one of the patterns above (e.g. `my_read_file`)
+ * - Include `path`/`filePath`/`file` in its arguments
+ * - Or extend the FILE_READ_TOOLS list in a fork
+ */
+declare function isFileReadTool(toolName: string, args?: Record<string, unknown>): boolean;
+/**
+ * Create the `tool.execute.after` hook.
+ *
+ * When a file-read tool completes, this hook annotates the output
+ * with hashline prefixes so the AI can reference lines precisely.
+ *
+ * @param cache - optional LRU cache for annotated content
+ * @param config - resolved hashline configuration
+ */
+declare function createFileReadAfterHook(cache?: HashlineCache, config?: Required<HashlineConfig>): NonNullable<Hooks["tool.execute.after"]>;
+/**
+ * Create the `tool.execute.before` hook.
+ *
+ * When a file-edit tool is about to execute, this hook strips any
+ * hashline prefixes from the content arguments so the edits apply
+ * cleanly to the original file.
+ *
+ * @param config - resolved hashline configuration
+ */
+declare function createFileEditBeforeHook(config?: Required<HashlineConfig>): NonNullable<Hooks["tool.execute.before"]>;
+/**
+ * Create the system prompt injection hook.
+ *
+ * Adds detailed instructions to the system prompt explaining the hashline format,
+ * edit operations, and hash verification rules so the AI model can use them precisely.
+ *
+ * @param config - resolved hashline configuration
+ */
+declare function createSystemPromptHook(config?: Required<HashlineConfig>): NonNullable<Hooks["experimental.chat.system.transform"]>;
+
+export { HashlineCache, HashlineConfig, createFileEditBeforeHook, createFileReadAfterHook, createSystemPromptHook, isFileReadTool };

package/dist/utils.js

@@ -0,0 +1,54 @@
+import {
+  createFileEditBeforeHook,
+  createFileReadAfterHook,
+  createSystemPromptHook,
+  isFileReadTool
+} from "./chunk-C2EVIAGV.js";
+import {
+  DEFAULT_CONFIG,
+  DEFAULT_EXCLUDE_PATTERNS,
+  DEFAULT_PREFIX,
+  HashlineCache,
+  applyHashEdit,
+  buildHashMap,
+  computeLineHash,
+  createHashline,
+  formatFileWithHashes,
+  getAdaptiveHashLength,
+  getByteLength,
+  matchesGlob,
+  normalizeHashRef,
+  parseHashRef,
+  replaceRange,
+  resolveConfig,
+  resolveRange,
+  shouldExclude,
+  stripHashes,
+  verifyHash
+} from "./chunk-IVZSANZ4.js";
+export {
+  DEFAULT_CONFIG,
+  DEFAULT_EXCLUDE_PATTERNS,
+  DEFAULT_PREFIX,
+  HashlineCache,
+  applyHashEdit,
+  buildHashMap,
+  computeLineHash,
+  createFileEditBeforeHook,
+  createFileReadAfterHook,
+  createHashline,
+  createSystemPromptHook,
+  formatFileWithHashes,
+  getAdaptiveHashLength,
+  getByteLength,
+  isFileReadTool,
+  matchesGlob,
+  normalizeHashRef,
+  parseHashRef,
+  replaceRange,
+  resolveConfig,
+  resolveRange,
+  shouldExclude,
+  stripHashes,
+  verifyHash
+};

package/package.json

@@ -0,0 +1,56 @@
+{
+  "name": "opencode-hashline",
+  "version": "1.0.0",
+  "description": "Hashline plugin for OpenCode — content-addressable line hashing for precise AI code editing",
+  "main": "dist/index.cjs",
+  "module": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "type": "module",
+  "files": [
+    "dist"
+  ],
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "require": "./dist/index.cjs"
+    },
+    "./utils": {
+      "types": "./dist/utils.d.ts",
+      "import": "./dist/utils.js",
+      "require": "./dist/utils.cjs"
+    }
+  },
+  "scripts": {
+    "build": "tsup",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "typecheck": "tsc --noEmit",
+    "benchmark": "npx tsx benchmarks/benchmark.ts",
+    "prepublishOnly": "npm run build"
+  },
+  "keywords": [
+    "opencode",
+    "opencode-plugin",
+    "plugin",
+    "hashline",
+    "line-hashing",
+    "ai",
+    "code-editing"
+  ],
+  "license": "MIT",
+  "peerDependencies": {
+    "@opencode-ai/plugin": "^1.2.2"
+  },
+  "devDependencies": {
+    "@opencode-ai/plugin": "^1.2.2",
+    "@types/node": "^25.2.3",
+    "@types/picomatch": "^4.0.2",
+    "tsup": "^8.5.1",
+    "typescript": "^5.9.3",
+    "vitest": "^4.0.18"
+  },
+  "dependencies": {
+    "picomatch": "^4.0.3"
+  }
+}