v0.4.1

EvoForge v0.4.1
This release focuses on the Cloudflare integration: detection, connection status, UI polish, and — most importantly — making the agent actually aware of your connected Cloudflare account.
🔧 Fixed

Wrangler not detected on Windows. npm installs Wrangler as a .cmd shim, which Windows process creation cannot resolve by bare name. EvoForge now resolves external tools through PATH + PATHEXT, so a globally installed Wrangler (or the npx fallback) is detected reliably.

stdio MCP servers launched via npx failed to start on Windows. Same root cause, same fix — MCP extensions configured with npx/other npm-style commands now launch correctly.

False "Connected" status. wrangler whoami exits with code 0 even when logged out, which made EvoForge report a connection that didn't exist — and skip launching the login flow when you clicked Connect. Login state is now determined from the actual output, so Connect reliably opens the browser authorization when you're logged out.

Account name missing after login. The account name is now parsed from the table layout newer Wrangler versions print, in addition to the legacy Account Name: format.

🤖 Agent

The agent now knows Cloudflare is connected. Previously the model would truthfully claim it had no Cloudflare access even with a connected account. When Wrangler is authenticated, the agent is informed of the connected account and will operate Cloudflare through wrangler (deploy Workers and Pages, manage D1/KV/R2/queues/secrets, stream logs). Destructive operations still require your explicit confirmation.