March 27, 2026
Product Release
Enterprise-Ready Memory for Agents, Now with Proxy Support
ByteRover CLI now works in real enterprise network environments. For developers behind corporate firewalls, VPNs, and mandatory proxies, core workflows like brv login and brv pushcould fail because the CLI daemon bypassed proxy settings. We launched proxy support to remove that blocker and make ByteRover usable where many enterprise teams actually work.
Check the doc:
Built for enterprise environments
A persistent memory layer is only valuable if teams can deploy it inside their actual infrastructure. Proxy support makes ByteRover more practical for organizations with strict security controls and lays the groundwork for broader compatibility, including workflows that use external LLM providers behind enterprise proxies.
Important note: Currently, proxy support is exclusively available for ByteRover’s Provider. While this lays the groundwork for broader compatibility, other external LLM providers are not yet supported.
Reduce setup friction for new users and teams
Instead of forcing developers to invent workarounds for locked-down networks, ByteRover can now respect common proxy configurations such as HTTP_PROXY, HTTPS_PROXY, NO_PROXY, and ALL_PROXY, including SOCKS5 and basic authentication. That means faster onboarding and fewer environment-specific surprises.
Make the CLI more reliable day to day
Proxy awareness is not just a compatibility checkbox, but it improves the success rate of network requests across different enterprise architectures and ensures the background daemon behaves correctly at runtime, not only the foreground CLI.
Faster troubleshooting and recovery
The CLI now catches common proxy and SSL-related failures such as certificate-chain and timeout errors, then returns more actionable guidance instead of low-level stack traces. For enterprise users, that means less confusion and faster recovery when firewall or SSL inspection rules interfere with requests.