> ## Content Index > Fetch the complete content index at: https://wuu73.org/aiguide-ghost/llms.txt > Use this file to discover other available public pages before exploring further. # How Agent Harnesses Edit Files - URL: https://wuu73.org/aiguide-ghost/coding-file-edits/ - Published: 2026-05-29T00:00:00.000Z - Updated: 2026-05-29T00:00:00.000Z - Description: A field guide to how agent harnesses — Cline, Codex, OpenCode, ADK-Rust, Reasonix, CodeWhale, CheetahClaws, Oh My Pi, Crush, DeerFlow, Dirac, Goose, OpenHands, Pi, Pochi, Qwen Code, Wintermolt, Zaica, and more — actually edit files in your codebase. - Author: WUU73 - Tags: Deep Dives, Coding File Edits, #Import 2026-09-12 06:38 🔧 Developer Guide • Updated April 2026 How do AI coding assistants actually edit your files? Discover the strategies, matching algorithms, fallback mechanisms, and provider-native, exact-match, capability-gated, or anchor-native editing contracts behind Cline, Codex, OpenCode, ADK-Rust, Reasonix, CodeWhale, CheetahClaws, Oh My Pi, Aider, Crush, DeerFlow, Dirac, Goose, OpenHands, Pochi, Qwen Code, and more. ## Why Does This Matter? When you ask an AI assistant to "add a new function" or "fix this bug," there's a critical gap between the LLM's text generation and your actual filesystem. The AI outputs text—but how does that become a working code change? Every AI coding agent solves this differently. Some use **surgical search-and-replace**, others apply **unified diffs**, some just **overwrite entire files**, and a small but important set use **hash-backed anchors** to survive drift. Dirac does it with cryptographic word anchors; Oh My Pi does it with compact line-plus-hash markers. Understanding these approaches matters if you're: - Building your own AI coding tool - Debugging why an AI edit failed - Choosing between different AI assistants - Curious about the engineering behind these tools ## The Core Challenge 💡 #### LLMs Are Non-Deterministic Even with the same prompt, an AI might output slightly different whitespace, comments, or formatting each time. A file editing system must handle these variations gracefully—or fail constantly. Consider what can go wrong: - **Whitespace mismatches:** The AI uses 2 spaces, but your file uses tabs - **Hallucinated content:** The AI "remembers" code that doesn't exist - **Partial context:** The AI only saw 50 lines but the file has 500 - **Race conditions:** You edited the file while the AI was generating ## The Landscape at a Glance We analyzed how the agents in `repos/` handle file editing, plus a few adjacent reference agents. Each takes a different philosophical approach: 🎯 ### Cline **The Precision Specialist** Uses search/replace with a 4-tier matching strategy. Doesn't trust AI whitespace—implements heavy fallback logic. 4-Tier Fallback🔧 ### Codex / Claude Code **The Patch Master** Uses custom patch syntax with `*** Begin Patch` markers. Treats file editing like version control. Custom Patch Format🛠️ ### OpenCode **The Fallback King** Implements **9 different matching algorithms** tried sequentially. Maximum redundancy approach. 9-Layer Fallback⚡ ### Aider **The Format Flexible** Supports three formats: SEARCH/REPLACE, whole file, and unified diff. Model-specific defaults. 3 Edit Formats🚀 ### Grok CLI **The Dual-Mode Agent** Traditional text editor + Morph AI-powered fast editing. User confirmation with diff previews. 4,500+ tok/sec💎 ### Crush / Neovate **The Redundant Matchers** JSON tool schemas with edit/write/multiedit tools and layered string-matching fallbacks for stubborn whitespace and escaping. Layered Replacement📌 ### Dirac **The Hash-Anchored Editor** Edits target stable line hashes instead of line numbers, then batch multi-file changes in reverse order to avoid drift. Hash Anchors🧪 ### Oh My Pi **The Hashline Lab** Makes hashline the default edit mode: compact line-plus-hash anchors, multi-section preflight checks, same-path merge logic, nearby anchor rebasing, and benchmark-driven iteration. Hashline Default🧩 ### OpenHands / Claude-style **The Standard Editor Interface** Uses `str_replace_editor`\-style commands: view, create, str\_replace, insert, and undo, usually inside a sandbox. Editor Command API🏗️ ### ADK-Rust **The Provider Delegate** Wraps provider-native editor contracts instead of building a giant local matcher. Anthropic tools execute strict exact-match edits; OpenAI `apply_patch` is surfaced as a native built-in. Native Tool Contracts⚙️ ### Pi / Pochi / Qwen **The Exact-Match Pragmatists** Prefer explicit old/new content with uniqueness checks, preview diffs, encoding preservation, and clear failure messages. Exact + Verified🔌 ### Goose / DeerFlow / Hermes **The Tool-Host Agents** File mutation often lives in extensions, sandbox tools, or MCP-like tool registries rather than a single built-in editor primitive. Extension/Sandbox Tools ## The Six Core Editing Methods Across all agents we analyzed, file editing boils down to these six fundamental approaches: | Method | Token Cost | Reliability | Best For | Used By | | -------------------------- | ---------- | ----------- | ----------------------------------------- | --------------------------------------------------------------------------------------- | | **Whole File Replacement** | High | 100% | New files, small files, last resort | All agents (fallback) | | **Search & Replace** | Low | Medium | Targeted edits, function changes | Cline, Aider, OpenCode, Crush, Pochi, Qwen Code, Neovate, ADK-Rust (Anthropic wrappers) | | **Unified Diff / Patch** | Very Low | Variable | Multi-file refactors, trained models | Codex, Aider, Claude Code/OpenClaudeCode, shell-based agents | | **Line-Based / Anchor** | Medium | Good | When exact match fails | OpenCode, Cline (fallback) | | **Multi-Edit / Atomic** | Medium | High | Variable renames, bulk changes | OpenCode | | **Hash-Backed Anchors** | Low-Medium | High | Repeated surgical edits in drifting files | Dirac, Oh My Pi | ## The "Secret Sauce": Fallback Cascades The top-performing agents don't rely on a single method. They implement **cascading fallbacks**—if one approach fails, they automatically try the next. 1**Exact Match** Try byte-for-byte string matching. Fastest, most reliable when it works. ↓2**Whitespace Flexible** Normalize spaces/tabs, trim lines. Handles indentation differences. ↓3**Anchor Matching** Match first/last lines of a block, fuzzy-match the middle content. ↓4**Diff/Patch Application** Use diff-match-patch or git cherry-pick algorithms. ↓5**Full Overwrite** Nuclear option. Works 100% but expensive and risky for large files. ↔️ #### Not every agent wants a fallback ladder ADK-Rust is one counterexample. It prefers provider-native tool contracts and sharp exact-match failures over adding more local heuristics. Oh My Pi is another: instead of endlessly extending fuzzy matching, it changes the address space with hashline anchors. ## Key Insights for Tool Builders ✅ #### Don't Force JSON For file editing, custom formats or XML reduce escaping errors significantly. Cline and Codex both avoid passing code inside JSON strings. ✅ #### LSP Integration OpenCode checks for syntax errors *immediately* after every edit using Language Server Protocol. Bad edits get caught and reported back to the AI. ✅ #### User Confirmation Grok CLI shows diff previews before every write. Users can approve, modify, or skip. This prevents catastrophic mistakes. ✅ #### 1-Indexed Line Numbers Codex, OpenCode, and ADK-Rust all use 1-based line numbers when communicating with LLMs. It matches how humans count lines in editors. ## Explore the Playbook [📚 Editing MethodsDeep dive into each editing approach: whole file, search/replace, unified diff, anchors, and multi-edit.](https://wuu73.org/aiguide-ghost/coding-file-edits-methods/)[🤖 Agent ComparisonsDetailed analysis of Cline, Codex, OpenCode, Aider, Grok CLI, Crush, Dirac, OpenHands, Pi, Pochi, Qwen Code, Goose, and more.](https://wuu73.org/aiguide-ghost/coding-file-edits-agents/)[💬 Prompts & InstructionsHow agents tell AI models to use their tools. System prompts, tool definitions, and error handling.](https://wuu73.org/aiguide-ghost/coding-file-edits-prompts/)[🏗️ ADK-Rust Deep DiveShort focused write-up on provider-native editing, strict exact matches, Anthropic editor wrappers, and OpenAI patch declarations.](https://wuu73.org/aiguide-ghost/coding-file-edits-adk-rust/)[🎯 Reasonix Deep DiveByte-exact SEARCH/REPLACE, edit-gate review, repair stages, snapshotting, and strict sandbox enforcement.](https://wuu73.org/aiguide-ghost/coding-file-edits-reasonix/)[🐋 CodeWhale Deep DiveDirect writes, exact-first replace with bounded fuzzy fallback, transactional patch rollback, approval gating, and diagnostic feedback from touched files.](https://wuu73.org/aiguide-ghost/coding-file-edits-codewhale/)[🐆 CheetahClaws Deep DiveMixed-mode editing with direct Read/Write/Edit tools, capability-gated kernel built-ins, notebook mutation, and unified diff feedback.](https://wuu73.org/aiguide-ghost/coding-file-edits-cheetahclaws/)[🧪 Oh My Pi Deep DiveFocused analysis of hashline editing, prompt helpers, nearby rebasing, multi-section preflight, and how it compares to Dirac and Pi Mono.](https://wuu73.org/aiguide-ghost/coding-file-edits-oh-my-pi/)[🛠️ Build Your OwnPractical guide with code examples. Implement fallback cascades, matching algorithms, and LSP integration.](https://wuu73.org/aiguide-ghost/coding-file-edits-implementation/) ## Quick Comparison Chart A visual overview of how different agents prioritize various aspects: #### Token Efficiency Lower is betterCodex★★★★★Aider★★★★☆Cline★★★☆☆OpenCode★★★☆☆ #### Fallback Depth More is more robustOpenCode9 layersAider5 layersCline4 layersCodex3 layers #### LSP Integration Syntax checkingOpenCodeFullClinePartialCodexMinimalAiderMinimal #### User Approval Confirmation flowGrok CLIFull diff previewCodexApproval req.ClineConfigurableAiderAuto-apply