← back NO. #ebcd416e

NO.: #ebcd416e
Topic: OTHER
Source: Anthropic Python SDK
Published: 2026-05-04 17:13:38
Importance: ★ 5/10 — radar 50
Original: github.com/anthropics/anthropic-sdk-python/releases/tag/v0.98.0

`anthropic-sdk-python` `v0.98.0` adds WIF, interactive OAuth, and auth profiles

Auth setup got much better, and Managed Agents APIs moved forward too. Useful if you juggle multiple creds or deploy across cloud environments; otherwise this is a solid maintenance upgrade.

[ KEY POINTS ]

Workload Identity Federation, interactive OAuth, and auth profiles landed together, cutting secret management friction across local and cloud setups.
You can now set headers via environment variables, which simplifies per-env routing, tracing, and proxy-style customization without code edits.
Managed Agents APIs were improved again, a signal that Anthropic is still actively shaping higher-level agent workflows in the SDK.
Streaming now carries stop_details onto the accumulated Message, fixing a state-loss bug that could break downstream control flow.
Multipart file array naming and Vertex AI async multi-region base_url bugs were fixed, reducing edge-case integration failures.

Originalgithub.com/anthropics/anthropic-sdk-python/releases/tag/v0.98.0Read original →

// related

#0001
#0001Other GeekNews2 hours ago
`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge
40radar
Bambu Studio3D printing slicer — based on PrusaSlicer
Copyleft obligations can reach bundled dynamic libraries and install info. If you fork AGPLv3 software, partial source drops are not enough.
- AGPLv3 Corresponding Source covers code needed to generate, install, run, and modify the work, not just visible app changes.
- A tightly coupled proprietary networking library may need source disclosure if it is dynamically linked into the modified app.
- Forking strong-copyleft projects for commercial software demands release-process checks before binaries ship.
Source: news.hada.io/topic?id=29694Read original →
FIG-0011:1
40radar
FIG-0011:1
#0002
#0002Other GeekNews2 hours ago
What's New in `Chrome` from Google I/O 2026
50radar
The web is shifting from human clicks to agent-driven browsing and AI-assisted development. Worth tracking before specs turn into defaults.
- Paul Kinlan, who leads Chrome DevRel, framed the last 6 months as a fast reset for web development workflows.
- One axis is preparing sites for agents that browse on users' behalf. Structured, machine-readable UX will matter more.
- Another axis is developer tooling. Chrome is positioning DevTools around AI-assisted debugging and building, not just inspection.
- The source is short and lacks API-level details, so this is a watchlist item rather than something to implement today.
Source: news.hada.io/topic?id=29693Read original →
FIG-0021:1
50radar
FIG-0021:1
#0003
#0003Other GeekNews5 hours ago
JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off
40radar
Small browser UIs can become heavy fast. WebAssembly helps, but async bridging to the JavaScript event loop keeps the payoff situational.
- Nested syntax and callbacks make JavaScript complexity grow quickly; bundle size is often a design outcome, not just tooling noise.
- Small UI surfaces can still pull in many libraries. Dependency defaults deserve review before reaching for another package.
- WebAssembly opens the browser to other languages, but Pyodide-style async event-loop integration adds real coordination cost.
Source: news.hada.io/topic?id=29675Read original →
FIG-0031:1
40radar
FIG-0031:1

`anthropic-sdk-python` `v0.98.0` adds WIF, interactive OAuth, and auth profiles

// related

`Bambu Studio` Faces Broad AGPLv3 Compliance Challenge

What's New in `Chrome` from Google I/O 2026

JavaScript Debloating: Complexity, Libraries, and the WASM Trade-off