FlutterFlow Desktop 7.0.73 AI Agent permission/ACP failures — AbortError: Stream closed and -32603 Internal error

[shamy55]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

After FlutterFlow Desktop auto-updated to 7.0.73 on macOS, the AI Agent became unreliable.

Normal Claude Code tool calls frequently trigger repeated permission prompts. Commands that need the permission/approval channel — especially compound Bash commands, redirection, pipes, or mutating shell commands — often fail with:

Tool permission request failed: AbortError: Stream closed

and sometimes:

ACP turn failed: JsonRpcRequestException(-32603, Internal error)

The project itself still compiles and pushes successfully. The failures occur even with tiny shell commands, so this does not appear related to project/file size.

Expected Behavior

Permission requests should reliably reach FlutterFlow Desktop, approval should return to Claude Code, and approved commands should execute without terminating the ACP turn.

AI Agent sessions should remain stable during normal project inspection/editing.

Steps to Reproduce

Open FlutterFlow Desktop 7.0.73 on macOS.
Open a project and start the Claude AI Agent.
Ask the agent to perform normal project work that requires Bash inspection or file operations.
Commands using &&, pipes, redirects, or writes frequently trigger permission prompts.
Approve the requested command.
The approval round-trip intermittently fails with:
AbortError: Stream closed
or the ACP turn terminates with:
JsonRpcRequestException(-32603, Internal error)

This has reproduced across fresh sessions/restarts.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4kksmAsJRJocNY1rrPbe1KvCEXKUd/TLJEpu0bWUkbGO/4O5kfdeP7M1tVZNyzaH47Ilr9mkcy/s3Git/2G+0EGEmuY7pazc0JdxPPbGOib8muDZeafEd8EflWfH61yrug2SUlBLdtR0IT2Gb3OfOyRT+Cf9qOYwx5e6fDbOY=

Visual documentation

Environment

- FlutterFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

This started after the FlutterFlow Desktop auto-update. The same project and workflow were working before the update.

I am on a paid plan and this regression is significantly disrupting development because normal AI Agent sessions repeatedly stop for permission prompts and can then fail during the approval round-trip.

I would appreciate confirmation whether this is a known 7.0.73 issue, whether a hotfix is planned, and whether there is a supported way to roll back FlutterFlow Desktop to the previous working release.

[shamy55]

Reproduced again after restarting FlutterFlow Desktop.

This time there was no Bash permission prompt involved — the ACP turn failed directly during a normal Edit operation on dsl/edit.dart after 2m 8s:

ACP turn failed: JsonRpcRequestException(-32603, Internal error)

This further suggests the issue is in the ACP/Desktop transport itself rather than the Bash permission rules. The project itself remains valid and has been compiling/pushing successfully outside these intermittent ACP failures.

[shamy55]

Another reproducible symptom on FlutterFlow Desktop 7.0.73:

Local Run intermittently fails during the export step with:

Failed to export code.
SocketException: Write failed (OS Error: Broken pipe, errno = 32), port = 0

Important context: this is the same project that continues to compile/push successfully, and restarting FlutterFlow Desktop often makes Local Run work again without any project-code changes. This suggests the failure may be another Desktop-side transport/process instability rather than a Foodycall code issue.

Given the separate ACP failures already documented in this issue (AbortError: Stream closed and JsonRpcRequestException(-32603, Internal error)), this broken-pipe export failure appears consistent with the broader post-7.0.73 instability we are seeing in Desktop communication/process handling.