hexum_splice

Last updated 29 August 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. Hexum is a hosted MCP server. You keep Cursor, Claude Code, Antigravity, Codex, or Grok. Hexum is not an IDE and not a model.

Is hexum_check an LLM?

No. hexum_check is deterministic. It maps files to layers in architecture.hexum and reports forbidden imports. It does not call a model.

Does Hexum store my repo?

No. Zero Data Retention is on Usage and Teams. MCP payloads are not stored. Hexum does not train on your code. Policy: /zdr.