CLAUDE CODE V2.1.70 HARDENS PROXIES, BEDROCK, AND MCP; ECC V1.8.0 SHIPS AN AGENT HARNESS
Claude Code v2.1.70 delivers critical stability fixes for proxies, Bedrock model IDs, MCP caching, and Windows/VS Code, while ECC v1.8.0 adds a cross-tool agent...
Claude Code v2.1.70 delivers critical stability fixes for proxies, Bedrock model IDs, MCP caching, and Windows/VS Code, while ECC v1.8.0 adds a cross-tool agent harness.
Claude Code v2.1.70 fixes 400 errors behind third‑party gateways by detecting proxy endpoints when using ANTHROPIC_BASE_URL and disabling tool_reference blocks, and resolves “effort” parameter 400s with custom Amazon Bedrock identifiers. It also stabilizes ToolSearch responses, prevents MCP instruction-induced prompt‑cache busts, and cleans up Windows/VS Code issues (clipboard, extra windows, voice mode), plugin marketplace refresh, and git compatibility for security review.
ECC v1.8.0 reframes ECC as an agent harness with new commands (/harness-audit, /loop-start, /loop-status, /quality-gate, /model-route), model routing, and reliability hooks for safer cross‑platform runs. It aligns behavior across Claude Code, Cursor, OpenCode, and Codex to make agent loops and quality gates reproducible in CI and local workflows.
For structured rollout guidance and org-wide usage patterns, Anthropic’s Academy has practical “Claude for work” resources, including integrations and project organization tips Claude for work.
Proxies and Bedrock setups stop breaking on edge model identifiers and gateway routing.
ECC’s harness makes agent workflows testable and consistent across tools.
-
terminal
Run end‑to‑end flows through your proxy (ANTHROPIC_BASE_URL) and confirm tool search no longer injects tool_reference blocks.
-
terminal
Validate Bedrock inference profiles with non‑standard model IDs to confirm the 'effort' parameter 400 no longer appears.
Legacy codebase integration strategies...
- 01.
Upgrade to v2.1.70 and retest MCP servers, proxies, and Bedrock profiles without changing app logic.
- 02.
Adopt ECC harness incrementally by wrapping existing Claude Code/Cursor usage and gating loops with /quality-gate.
Fresh architecture paradigms...
- 01.
Start with ECC’s model routing and harness defaults to get reproducible agent runs from day one.
- 02.
Standardize MCP tool schemas and Claude settings to avoid prompt‑cache churn and legacy model pinning.