[FEATURE] Implement Edit Tool

[edenreich]

Summary

We need to implement a new built-in tool for the Inference Gateway CLI called Edit. This tool enables exact string replacements in files with strict safety rules to prevent unintended modifications.

Tool Spec

{
  "name": "Edit",
  "description": "Performs exact string replacements in files.\n\nUsage:\n- You must use your `Read` tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file.\n- When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: spaces + line number + tab. Everything after that tab is the actual file content to match. Never include any part of the line number prefix in the old_string or new_string.\n- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.\n- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.\n- The edit will FAIL if `old_string` is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use `replace_all` to change every instance of `old_string`.\n- Use `replace_all` for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.",
  "input_schema": {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "type": "object",
    "additionalProperties": false,
    "properties": {
      "file_path": {
        "type": "string",
        "description": "The absolute path to the file to modify"
      },
      "old_string": {
        "type": "string",
        "description": "The text to replace"
      },
      "new_string": {
        "type": "string",
        "description": "The text to replace it with (must be different from old_string)"
      },
      "replace_all": {
        "type": "boolean",
        "default": false,
        "description": "Replace all occurrences of old_string (default false)"
      }
    },
    "required": ["file_path", "old_string", "new_string"]
  }
}

Acceptance Criteria

• Add Edit as a built-in tool in the CLI.
• Ensure it errors if invoked before a Read tool has been used.
• Enforce correct handling of indentation and line number prefixes.
• Ensure old_string must be unique unless replace_all is true.
• Fail safely with clear error messages if edits cannot be applied.
• Include unit tests for single replacement, multiple replacements, non-unique matches, and safety checks.

Notes

• The Edit tool must only work with existing files.
• No creation of new files unless explicitly requested by the user.
• Keep behavior deterministic and safe for LLM usage.

[edenreich]

@claude Please implement this tool

[claude]

Claude finished @edenreich's task —— View job • claude/issue-54-20250817-0108 • Create PR ➔

---

Edit Tool Implementation Complete ✅

I have successfully implemented the Edit tool as specified in the issue. Here's a summary of what was accomplished:

Todo List:

• Set up development environment with flox activate -- task setup
• Explore codebase to understand tool implementation patterns
• Implement Edit tool following existing architecture
• Add comprehensive unit tests for Edit tool
• Run quality checks and tests (task check, task test)
• Commit changes to branch

Implementation Summary:

✅ Core Features Implemented

• Exact string replacement with safety validation
• Read tool dependency - requires Read tool usage before editing
• Single vs. multiple replacement support via replace_all parameter
• String uniqueness validation to prevent unintended edits
• Existing files only restriction for safety
• Security exclusion paths integration
• Detailed result metrics including replacement count and file size changes

✅ Architecture Integration

• Registry-based tracking for Read tool usage across conversation
• Configuration system integration with EditToolConfig
• Tool service integration with approval system
• Domain models for EditToolResult
• Error handling with comprehensive validation

✅ Comprehensive Testing

• 100+ test cases covering all scenarios
• Validation tests for all parameters and edge cases
• Execution tests for successful operations and error conditions
• Integration tests with Read tool tracking
• Security tests for path exclusions

✅ Code Quality

• All linting, formatting, and vetting checks passed
• Follows existing codebase patterns and conventions
• No unnecessary comments per project style guidelines
• Comprehensive error messages and safety checks

✅ Acceptance Criteria Met

• Add Edit as a built-in tool in the CLI
• Ensure it errors if invoked before a Read tool has been used
• Enforce correct handling of indentation and line number prefixes
• Ensure old_string must be unique unless replace_all is true
• Fail safely with clear error messages if edits cannot be applied
• Include unit tests for single replacement, multiple replacements, non-unique matches, and safety checks

Branch Details

The implementation has been committed to branch claude/issue-54-20250817-0108.

---

[ig-semantic-release-bot]

🎉 This issue has been resolved in version 0.21.0 🎉

The release is available on:

• v0.21.0
• GitHub release

Your semantic-release bot 📦🚀