Claude Code SDK ships in four languages

More shim than SDK: it turns Claude Code's private runtime contract into a copy-pastable library, which is exactly why power users will love it and platform teams will worry.

• –Four language ports lower the integration tax for teams that want Claude Code-style agent loops inside their own tooling.
• –The NDJSON bridge is the real developer win: it makes the SDK easy to shell out to from automation, CI, or orchestrators.
• –Built-in shell, file, glob, and grep tools plus MCP support make this more of an agent substrate than a thin API wrapper.
• –MIT licensing and single-file distribution make adoption trivial, so the project can spread even if it stays unofficial.
• –The auth path is the risk: undocumented headers, keychain OAuth, and a billing token hidden in the system prompt are brittle and may be ToS-sensitive.