Windows Codex localhost proxy refuses FlutterFlow network requests

What version of the Codex App are you using (From “About Codex” dialog)?

Codex & OWL Version 26.901.51231 Released Sept 5, 2026

What subscription do you have?

Personal Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex cannot complete FlutterFlow CLI network requests through its Windows localhost proxy.

I am using the Codex Windows app with the agent environment set to Windows native. When Codex runs the read-only FlutterFlow branch-status command, the FlutterFlow CLI attempts to retrieve this manifest:

https://storage.googleapis.com/flutterflow-downloads/flutterflow-ai-packages/prod/builds/c40fa0b8/manifest.json

The request fails with:

Error: Network request failed: The remote computer refused the network connection

Earlier attempts showed that the failed request was being routed through 127.0.0.1 using changing localhost port numbers.

The same manifest URL opens successfully in Chrome and returns valid JSON. This shows that the computer’s normal internet connection can reach the FlutterFlow storage endpoint.

Troubleshooting completed:

1. Restarted the Codex app
2. Signed out and signed back in
3. Opened a new Codex session
4. Restarted Windows
5. Confirmed the correct FlutterFlow workspace
6. Confirmed that the FlutterFlow configuration file exists
7. Confirmed that the manifest opens in Chrome
8. Removed an unrequested third-party antivirus product and restarted Windows
9. Retested the read-only branch-status command once
10. Confirmed that the problem persists

Expected behavior:

The FlutterFlow branch-status command should connect and return the local head, server head, and Dirty status.

Actual behavior:

Codex cannot complete the network request through its localhost proxy. The local head can be read from the local configuration, but the server head and Dirty status remain unavailable.

FlutterFlow project ID:

montero-care-development-3cynku

Local head:

tTK6qguVs6dQimWWw64F

FlutterFlow package information:

Build ID: c40fa0b8
Version: 0.0.40+2
Minimum router version: 0.0.39

Related Codex feedback ID:

01a077a6-e933-7ef1-9acd-8ffabb3dd469

No project files or remote FlutterFlow resources were modified during these tests. Please investigate whether the Codex Windows sandbox or localhost network proxy is in a partial or broken state.

What steps can reproduce the bug?

1. Open ChatGPT for Windows, powered by Codex & OWL, version 26.901.51231.

2. Use the Windows-native agent environment with PowerShell.

3. Open an existing FlutterFlow AI workspace.

4. Ask Codex to run the read-only FlutterFlow branch-status command.

5. The FlutterFlow CLI begins retrieving this package manifest:

https://storage.googleapis.com/flutterflow-downloads/flutterflow-ai-packages/prod/builds/c40fa0b8/manifest.json

6. The request fails because the Codex session attempts to use a temporary localhost proxy address. The port changes between sessions.

Example error:

ClientException with SocketException: The remote computer refused the network connection, address = 127.0.0.1, port = 56682

A later attempt produced:

Error: Network request failed: The remote computer refused the network connection

7. Open the same manifest URL directly in an external web browser. It loads successfully and returns valid JSON.

8. Restarting ChatGPT, signing out and signing back in, restarting Windows, and opening a new Codex session do not resolve the problem.

The failure prevents the FlutterFlow CLI from completing its read-only branch-status check. No files are changed before the error occurs.

Windows: Windows 11 Pro 25H2, x64

In-app feedback ID: 01a077a6-e933-7ef1-9acd-8ffabb3dd469

Session ID: Not available in the app interface.

What is the expected behavior?

The Codex Windows session should allow the FlutterFlow CLI to retrieve the FlutterFlow package manifest through HTTPS without receiving a localhost connection-refused error.

After retrieving the required package, the FlutterFlow CLI should connect to FlutterFlow and return the requested read-only branch status, including the local head, server head, and dirty status.

Because the same manifest URL loads successfully in an external browser, the Codex session’s temporary localhost network proxy should route the request successfully or provide a working direct network path.

Additional information

Additional diagnostic details:

• ChatGPT Windows app version: 26.901.51231
• Agent environment: Windows native
• Windows: Windows 11 Pro 25H2, x64
• Dart SDK: 3.13.2
• FlutterFlow CLI: 0.0.39
• FlutterFlow AI package version shown by the manifest: 0.0.40+2
• FlutterFlow build ID: c40fa0b8
• Minimum router version: 0.0.39

The localhost proxy port changes between attempts, including ports 51341, 56682, and 64257. This suggests the failing address is a temporary proxy created for the Codex session.

The manifest URL works normally in an external browser on the same computer. The failure continues after restarting Windows, restarting the ChatGPT app, signing out and signing back in, and opening a new Codex session.

In-app feedback ID: 01a077a6-e933-7ef1-9acd-8ffabb3dd469

Start by reproducing the read-only FlutterFlow branch-status command in the Windows-native agent environment with PowerShell, then trace the temporary localhost proxy path and its connection-refused errors. Done means the manifest URL is retrieved successfully and the command returns the local head, server head, and Dirty status.