OpenCode v1.18.33 (2026-09-28) makes Cloudflare AI Gateway models honor provider response/stream timeouts, reports MCP browser launcher exits, redacts credentials in debug config output, and aligns Gemini thinking defaults/effort options with supported controls across model generations.

Key Takeaways

  • ✓Shipped v1.18.33 — CF AI Gateway timeouts honored
  • ✓MCP browser launcher immediate-exit failures reported
  • ✓Debug config redacts credentials/sensitive headers
  • ✓Gemini thinking defaults/effort aligned across generations
OpenCode 1.18.33: Cloudflare AI Gateway honors timeouts, MCP browser launch failures surface, debug config redacts credentials
🖼️Official Media
Click to view high-res
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Core Background & Industry Pain Points

OpenCode behind Cloudflare AI Gateway or Gemini thinking often fails silently: ignored timeouts hang streams, MCP browser launch failures stay quiet, and debug logs leak API keys.

Architecture Highlights & Internals

v1.18.33 applies provider response/stream timeouts on CF AI Gateway paths (#51549), surfaces immediate MCP browser launcher exits, redacts credentials in debug config, and aligns Gemini thinking defaults/effort with supported controls (#50841).

Authoritative Benchmarks & Measured Scores

No public SWE-bench/latency table—validate timeout abort, MCP launch errors, and credential redaction on your stack.

Developer Hands-on Guide

Upgrade via docs to v1.18.33. See the release notes.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextCloudflare open-sources security-audit-skill: 6-phase multi-agent audits with confirmed/needs_validation/rejected
Read Now→