@prometheus-ai/hashline
v0.5.8
Published
Hashline: a compact, line-anchored patch language and applier. Pluggable FS/IO so it works over disk, in-memory, or any custom backend.
Maintainers
Readme
@prometheus-ai/hashline
A compact, line-anchored patch language and applier.
Hashline is a diff format designed for LLM-driven file edits. It binds every hunk to a file-content hash so stale anchors are rejected before they corrupt code, and it abstracts over the filesystem so the same patcher works on disk, in memory, over the network, or against any custom backend.
Quick start
import {
Filesystem,
InMemoryFilesystem,
InMemorySnapshotStore,
Patcher,
Patch,
} from "@prometheus-ai/hashline";
const fs = new InMemoryFilesystem();
const snapshots = new InMemorySnapshotStore();
const before = `const greeting = "hi";\nexport { greeting };\n`;
await fs.writeText("hello.ts", before);
const tag = snapshots.record("hello.ts", before);
const patcher = new Patcher({ fs, snapshots });
const patch = Patch.parse(String.raw`[hello.ts#${tag}]
replace 1..1:
+const greeting = "hello";`);
const result = await patcher.apply(patch);
console.log(result.sections[0].op); // "update"
console.log(await fs.readText("hello.ts"));Format
See src/prompt.md for the user-facing description and
src/grammar.lark for the formal grammar.
Each file section starts with [PATH#TAG]. The tag is a 4-hex
content hash of the full normalized file text recorded by the
SnapshotStore, and it is not meaningful outside that store. The patcher
protects against stale anchors by resolving the tag, verifying the live file
still matches the recorded content hash, and refusing or attempting
session-aware recovery on mismatch.
Inside a section:
replace A..B:— replace lines A..B with following+TEXTbody rows.replace block A:— replace the syntactic block beginning on line A.delete A..B/delete block A— delete concrete lines or a resolved block.insert before A:/insert after A:/insert head:/insert tail:— insert following body rows.+TEXT— literal body row (use+alone for a blank line).
Abstractions
Filesystem
Read and write text by path. The default implementations:
InMemoryFilesystem— backed by aMap. Tests, sandboxes.NodeFilesystem— disk-backed viaBun.file/Bun.write. Default for CLIs.
Subclass Filesystem to wire hashline into any storage: VFS, S3, an LSP
text-document protocol, a Git tree, anything.
SnapshotStore
Required. Hashline tags are full-file content hashes recorded per path, so
Patcher must receive the store that observed them. Recovery replays edits
against the cached pre-edit snapshot and 3-way-merges onto current content
when the live file diverged.
Patcher
The orchestration class. Reads, normalizes line endings + BOM, applies edits,
restores line endings, and writes via the configured Filesystem. Multi-section
patches are preflighted up front so a partial batch never lands.
