---
title: "Comment by Esteban Fuster Pozzi (estebanrfp) on \"Defold AI: the MCP that connects Claude Code straight into your live Defold editor\" | Hashnode"
description: "Really appreciate this — you put your finger on the exact thing I cared about while building it: the action boundary . A few design choices that tackle it head-"
url: "https://hashnode.com/posts/defold-ai-the-mcp-that-connects-claude-code-straight-into-your-live-defold-editor/6a162094da253d50d4f30823/comment/6a26f2e490a24206524d0abd"
---

[Discussion](https://hashnode.com/posts/defold-ai-the-mcp-that-connects-claude-code-straight-into-your-live-defold-editor/6a162094da253d50d4f30823)

Comment [Defold AI: the MCP that connects Claude Code straight into your live Defold editor](https://hashnode.com/posts/defold-ai-the-mcp-that-connects-claude-code-straight-into-your-live-defold-editor/6a162094da253d50d4f30823)

[Esteban Fuster Pozzi (estebanrfp)](https://hashnode.com/@estebanrfp)

[Jun 8](https://hashnode.com/posts/defold-ai-the-mcp-that-connects-claude-code-straight-into-your-live-defold-editor/6a162094da253d50d4f30823/comment/6a26f2e490a24206524d0abd)

Really appreciate this — you put your finger on the exact thing I cared about while building it: the **action boundary**.

A few design choices that tackle it head-on:

-   **Every mutation goes through Defold's own `editor.transact` API** — changes are atomic and land in the editor's normal undo stack. A bad edit is just Ctrl+Z, nothing exotic.
-   **Nothing touches disk until an explicit `editor.save()`** — the AI stages changes in the live editor, but the developer decides when they get persisted.
-   **Read and write are split across tools** (`editor_state`, `*_get_*`, `*_find` are read-only; mutations are separate calls), so inspecting state never has side effects.

So it's exactly the "fast assistant, developer keeps final control" model you describe — not "Claude controls everything." The editor stays the source of truth and the human stays in the loop.

Thanks for the thoughtful read — this is exactly the kind of feedback that shapes where it goes next.

— Esteban. On a tangent, since you're clearly into AI + game tooling: I also maintain estebanrfp/gdb on github (a real-time graph DB) and a Godot integration, [godot-genosdb](https://github.com/estebanrfp/godot-genosdb) — different engine, but the same itch of keeping live state predictable. Might be up your alley.