Ziva 3.3.6: steadier on large Godot projects and unstable networks
Release

Ziva 3.3.6: steadier on large Godot projects and unstable networks

By Ziva.sh • November 7, 2026 • 4 min read

Ziva 3.3.6 is a reliability release. It fixes common ways Ziva failed when your project was big, your editor was busy or your connection was shaky:

  • Busy editor: Ziva waits for Godot to finish loading or importing before starting your message, instead of failing it.
  • Large projects: the first message shows that Ziva is indexing, instead of looking frozen.
  • Unstable networks: a dropped connection is retried automatically. If the retries go through, the worst-hit user sees up to 14 times fewer errors.
  • Smaller setup download: the tools Ziva downloads on first start are up to 62% smaller, which helps most on slow connections.
  • Updates: the update check waits for a busy editor. Its old 2-second limit hit 42% of the users who had an update error. This one takes effect from the next update on.

The numbers below come from Ziva's error reports from before the fix, plus one large-project test, with their caveats.


Ziva waits while Godot is busy

Large projects

Godot can stay busy for minutes while it opens, imports or rescans a large project. Before each message, Ziva asks Godot to save its open editor state so Ziva can make a restore point for undo. If Godot didn't answer within 45 seconds, the whole message failed:

Before 3.3.6: Work failed after 45s, with a Godot bridge call timed out error

That happened about 10 times a week. Ziva 3.3.6 waits for Godot instead and shows Waiting for Godot to respond... in the chat. If you'd rather not sit through the import, Stop cancels the wait. Because nothing gives up while the project is busy, these failures should drop to zero.


The first message in a big project shows progress

Large projects

The first time you message Ziva in a project, it indexes your files so it can undo its own changes later. In a very large project this takes a while, and the chat used to sit there with no explanation. Ziva now says what it's doing:

Ziva 3.3.6 showing Indexing project (first time only)... with a timer

We tested it on a project with 301,000 files and 2.3 GB of data. Later messages skip the wait.


Chats survive a dropped connection

Unstable networks

Sometimes the secure connection to Ziva is interrupted before your message leaves your computer. Proxies, VPNs, antivirus that inspects HTTPS and flaky Wi-Fi can cause it, often on Windows. Ziva used to show an error and make you press Retry:

Before: Ziva couldn't finish this request, with an EPROTO TLS handshake error

After: the same message gets a normal reply

Because the message never reached the model, sending it again can't charge you twice, so Ziva 3.3.6 retries by itself. You may briefly see a Retrying status before the reply arrives.

Before the fix this caused 141 errors for 25 users in a week. The worst-hit user had 43 failed messages that week, and 40 of them were this error. If the retries go through, that user sees up to 14 times fewer errors. If something on your network blocks every attempt, the retry can't help; check whether a proxy, VPN or antivirus inspects secure connections, or try another network.


A smaller first-time download

Unstable networks

The first time Ziva starts, it downloads its tools. In 3.3.6 that download is smaller, so it finishes sooner and has less chance of being cut off on a slow or unstable connection. Measured from the release files:

  • Apple Silicon Mac: 44.7 MB, down from 117.8 MB (62% smaller)
  • Windows x64: 60.2 MB, down from 73.0 MB
  • Linux x64: 178.3 MB, down from 222.3 MB

Updates wait for the editor too

Updates

Ziva checks for updates when Godot starts, which is exactly when Godot is busiest. The check gave the editor 2 seconds to answer, then showed an error and told you to close Godot and reinstall Ziva by hand:

Ziva's update banner before 3.3.6, showing a Godot bridge call timed out error and a Retry button

This was the biggest single cause: 56 of the 132 users who hit an update error in the 14 days before the fix ran into this timeout, 42% of them. The old code didn't report some of these failures, so the real share is probably higher. The check now waits for the editor to finish, however long the import takes.

One honest caveat: each Ziva version installs the next one with its own code. Updating from 3.3.5 to 3.3.6 still uses the old check, so the improvement starts with the update from 3.3.6 to 3.3.7. If you see this banner now, wait until Godot finishes importing and click Retry, or follow the update guide.


Ziva updates itself from the banner at the top of its panel. New to Ziva? Download it free. Release notes for every version are in the changelog.

Frequently asked questions

Does Ziva work on large Godot projects?
Yes. Godot can stay busy for minutes while it opens, imports or scans a large project. Since Ziva 3.3.6, Ziva waits for the editor during that time instead of failing, shows Waiting for Godot to respond... while it waits, and lets you cancel with Stop. The first message in a project also builds a one-time index for undo and shows Indexing project (first time only) while it runs. We tested it on a project with 301,000 files and 2.3 GB of data.
Does Ziva work on unstable Wi-Fi or behind a proxy?
Ziva 3.3.6 retries a message by itself when the secure connection drops before the message is sent, which proxies, VPNs, antivirus that inspects HTTPS and flaky Wi-Fi can cause. Nothing reached the model, so a retry can't charge you twice. If something on your network blocks every attempt, the message still fails; check whether a proxy, VPN or antivirus inspects secure connections, or try another network.