What problem does it solve? Agents editing files through ad-hoc shell commands lose track of document state, apply edits against stale coordinates, and corrupt files when external processes change them. This Skill provides a server-owned editing protocol where every mutation is guarded by a revision, every search hit is addressable by id, and external changes are detected and resolved explicitly. ## Core Features & Use Cases - Revision-guarded editing: insert, replace, undo, redo, and save all require the current revision, with optional expected-text verification and match-id targeting from search results, so edits never apply to stale coordinates. - Multi-mode inspection and search: read files as UTF-8 text, raw bytes, or hex rows, and search with exact, wildcard, regex (Rust/PCRE2), and six fuzzy modes, with paged results persisted in SQLite. - Large-file and recovery support: files above 256 MiB use bounded reads and acknowledged streaming large-edit jobs, journaled edits survive crashes, and external changes are resolved via reload, merge, backup, or force-save. - Use Case: An agent needs to rename a function across a 300 MB log file: it opens the file, runs a bounded exact-text search, confirms the hit with preview lines, applies a replace by match-id, and saves with the returned revision. ## Quick Start Ask the agent to open a file with ai-text-editor, search it for a specific string, and replace that match using the reported revision.
