دانلود CLI Proxy API 6.7.33

Changelog
- f36a5f5654cd81474b66c41f5629807db2907123 Merge pull request #1294 from Darley-Wey/fix/claude2gemini
- c1facdff6718922c0a5abceddae2132f4514aed6 Merge pull request #1295 from SchneeMart/feature/claude-caching
- 4ee46bc9f27ced19440712693ef3118413188108 Merge pull request #1311 from router-for-me/fix/gemini-schema
- c3e94a8277589368a31660ca09637ebceb00a2b2 Merge pull request #1317 from yinkev/feat/gemini-tools-passthrough
- 3a43ecb19b698ad60c30b6280ca6a5bd92ec228d feat(caching): implement Claude prompt caching with multi-turn support
- 538039f583ed677a572cb3504f53df5a00c5dda9 feat(translator): add code_execution and url_context tool passthrough
- d0d66cdcb76f6988614d6e53bfc3188f2601d939 fix(gemini): Removes unsupported extension fields
- 2666708c30f54d99d4858b39905d0dd7011c8703 fix: skip empty text parts and messages to avoid Gemini API error When Claude API sends an assistant message with empty text content like: {"role":"assistant","content":[{"type":"text","text":}]} The translator was creating a part object with no data field, causing Gemini API to return error: "required oneof field 'data' must have one initialized field" This fix: 1. Skips empty text parts (text=) during translation 2. Skips entire messages when their parts array becomes empty This ensures compatibility when clients send empty assistant messages in their conversation history.
- ca796510e932549c70e9217eb6e5a92cf9ee3687 refactor(gemini): optimize removeExtensionFields with post-order traversal and DeleteBytes