hexum_splice

Last updated 12 September 2026

When to call

When applying the patch.

Arguments

Required: file_path. Then either symbol_name + new_implementation, or line + new_source.

What comes back

The updated region, still valid source.

Example

{
  "name": "hexum_splice",
  "arguments": {
    "file_path": "src/ui/App.tsx",
    "symbol_name": "App",
    "new_implementation": "…"
  }
}

What the agent does next

Keep the write small: one symbol or one line. You keep Git.

All five tools: Hexum MCP tools. Contract file: architecture.hexum.

FAQ

What is hexum_splice?

Small write. Hexum is not a second copy of the repo. The workspace file is what Git sees.

When should the agent call hexum_splice?

When applying the patch.

Does Hexum replace Cursor or Claude Code?

No. You keep Cursor, Claude Code, Antigravity, Codex, or Grok. Hexum is not an editor and not a model. You paste a key into the agent you already use.

Does the architecture check use an AI?

No. It reads a rules file in your repo and reports forbidden imports. It does not call a model, so it does not guess.

Does Hexum store my repo?

No. We do not keep the code your agent sends. We do not train on it. Policy: /zdr.