vibehacker
News

More news

View all

Claude Code 2.1.307 adds /claude-api api-version to migrate code and stops double-sent MCP tool calls

The Oct 21 release adds /claude api api version to move your Claude API code to the new 2026 10 21 version, plus a claude code.safety event OpenTelemetry event for every tool call a permission rule, auto mode, hook, or sandbox blocked or prompted. It also stops HTTP MCP tool calls being sent twice when a connection drops mid call (only read only or idempotent tools retry now), and Code Review gains @claude review stop to end an always on PR subscription…

LiteLLM 1.107.0 on PyPI and Docker was compromised with a credential stealer; pin 1.106.2

On Oct 21, an attacker controlled build pushed litellm==1.107.0 to PyPI (live 11:39 to 13:23 UTC) and to the latest , main latest , and main stable Docker tags, adding a .pth startup hook that steals cloud keys, SSH keys, and /.cursor , /.claude , and /.kiro configs on any Python start. If you installed it, remove cook.pth , cook.py , and sitecustomize.py from site packages, rotate credentials from a clean machine, and pin 1.106.2 (OSV advisory)…

LiteLLM Blog

Claude API ships version 2026-10-21, its first bump since 2023, and drops temperature, top_p, and top_k

Released Oct 21, requests on the new anthropic version return a 400 if they send temperature , top p , or top k , put document blocks in assistant messages, or attach citations to user text blocks; 2023 06 01 keeps working if you need the old behavior. New SDKs (Python 2.0.0, TypeScript 1.0.0, Go 2.0.0 and others, now Apache 2.0) send it by default (release notes)…

Antigravity CLI 1.4.4 brings Auto mode to Windows and passes the root conversation ID to MCP servers

Auto mode now works on Windows 11 24H2+ for personal Google Accounts ( mode auto or Shift+Tab ; Agent stays the default), and it now checks every subcommand in a pipeline and prompts before destructive Git or file commands. MCP tools/call requests also carry meta["antigravity.google/root conversation id"] , so servers see the top level conversation even when a nested subagent makes the call…

GitHub moves its busiest repos to Azure by locking per branch, not per repo, as agent pushes surge

In an Oct 21 engineering post, GitHub says it's changing its write quorum from the whole repository to individual references, so agents and developers pushing to their own branches no longer queue behind each other, which removes the 25ms round trip penalty that kept its busiest repos out of Azure. GitHub says pushes grew 4.9x year over year to 3.35 billion a month (earlier post)…

GitHub Blog

Spotted something we missed? Start a thread.