So after that i asked a Cursor to check out what that "tool" did.
Spended 50 percents of api
Aaaand
Ziva Agent – issues in my Godot project (practical report)
Setup
- Godot 4.7.stable (Windows 10)
- Ziva Agent plugin v3.1.2 (sidecar / zivacode)
- Project: Dialogic 2 visual novel (300MB, heavy
addons/ + assets)
- Machine is weak (old i5 / 8GB RAM) — may amplify some problems, but several failures look like plugin bugs
1) Local History / Snapshot hard-fails prompts
When sending a chat request, Ziva often dies before doing any work:
Local history git-commit timed out after 30000ms
Also saw:
Godot bridge call timed out after 30000ms: c2g_setSnapshotContext
And editor warnings like:
Godot editor main thread unresponsive for ~10s (frozen or CPU-starved)
So the agent can’t start because snapshot/git history times out at 30s. Retry sometimes works, sometimes not. This makes the tool unreliable on non-tiny projects.
2) Network / API socket drops mid-request
Even after snapshot succeeded, requests failed with:
The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()
Also in logs:
plugin.getActivationState RPC failed with the same socket error (19s)
- Chat title gateway / telemetry calls failing (
Cannot parse response body)
Site ziva.sh can still respond, but long-lived agent/RPC connections drop.
3) Broke runtime with a type mismatch (bar ending)
After asking Ziva to build the party/bar ending flow, the game crashed on entering the bar scene:
Trying to assign value of type 'Sprite2D' to a variable of type 'AnimatedSprite2D'.
Cause: shared EndingBase.gd expected AnimatedSprite2D for $Background, but Ziva’s ending_party.tscn used a plain Sprite2D background. Classic “works in one ending, crashes in another” regression.
4) Incomplete / inconsistent scene results
Ziva claimed it set up transitions, generated bar background, students, music, Dialogic timeline (party_start), etc. In practice I repeatedly got:
- old background still showing instead of the new one
- visual artifacts (harsh overlays / light rectangles)
- characters that didn’t blend / wrong scale / clipping against furniture
- needing manual cleanup (strip characters/physics/lights, keep only BG, rewire assets)
So output quality is hit-or-miss, and “done” in chat ≠ actually correct in the scene.
5) Small plugin quality issues
From gdext log:
Failed to load completion sound at res://addons/ziva_agent/audio/pop-bright.wav
Not critical, but another sign the package isn’t clean.
6) Pricing / limits feel bad when requests fail
On Hobby I saw very low limits (around 3 weekly / 3 monthly in rate-limit status). Burning a limited request on timeout/socket failure feels especially bad.
Expected
- Snapshot/local history shouldn’t hard-block the whole prompt after 30s (or should degrade gracefully and still run)
- API disconnects should retry / recover instead of dead-ending the chat
- Generated scenes should respect existing typed scripts (
EndingBase) and not crash on enter
- “Completed” tasks should match what’s actually in the
.tscn files
Happy to attach /export-logs zip if useful.