Problem accessing CommandCode from Russia

Summary

From Russia, whenever I send a request, it just hangs indefinitely. The UI shows 0 tokens used, but in reality, my tokens are being drained. Even using a VPN configured as a proxy doesn't help. The only way I can get it to work is by using TUN mode, and even then, it's completely hit or miss. Specifically, in TUN mode it usually works perfectly for the first 1 to 3 requests, but then it simply dies and goes back to hanging indefinitely. There are no timeout errors or disconnect messages, the terminal just freezes forever while tokens continue to drain in the background.

All other AI services work perfectly, and even if they don’t work in Russia, with a VPN everything works fine.

Expected Behavior

The application should successfully process requests or return a clear connection error timeout if access from the current region is restricted.

Tokens should not be deducted from the account balance if a request fails to execute or hangs indefinitely.

The application should work reliably when routed through a standard proxy VPN configuration, similar to other AI services.

Actual Behavior

When sending a request from Russia, the application hangs indefinitely without completing the prompt.

Despite the UI showing "0 tokens used", tokens are secretly being drained from the account balance during these hanging requests.

Standard VPN proxy configurations do not resolve the issue; the connection remains blocked or unstable.

The only partial workaround is using a VPN in TUN (Tunneling) mode, but even this method is highly inconsistent and unreliable.

Steps to reproduce the issue

Connect to the internet from Russia.

Enable a VPN in standard Proxy mode.

Note the current token balance on your account.

Send a prompt via the CLI.

Observe the request hanging indefinitely, while the UI displays "0 tokens used".

Check the account balance again and observe that tokens were actually deducted.

Switch the VPN to TUN mode.

Send 1 to 3 prompts (these will execute successfully).

Send another prompt and observe it hang indefinitely again without any timeout error, draining tokens in the background just like in step 5.

Command Code Version

0.34.1

Operating System

Windows

Terminal/IDE

terminal cli

Shell

Additional context

Start with the CLI request path used by the prompt flow and reproduce the hang on Windows with the reported proxy and TUN configurations. Trace request completion, timeout and error reporting, and token accounting; done means failed or stalled requests terminate with a clear error and do not deduct tokens.