Edan Starfire

I spent all night on this, and came across 2 things: 1. Getting the callback signature exactly right is important because it kinda gently suggests there's a problem with the...

Details from my update above: SDK Release: v0.0.22 Claude Version: v1.0.113 Steps to Reproduce: Update script in https://github.com/anthropics/claude-code-sdk-python/blob/main/examples/tool_permission_callback.py with the following on Line 132: ```python print(f"{message=}") ``` It'll throw an...

I've gotten around this by providing API keys in my automation I'm using, but not sure about the OAuth flow for subscriptions. :/

I can tell you it's via using the `can_use_tool` callback. I've got another [issue ](https://github.com/anthropics/claude-code-sdk-python/issues/159) with a description of how to get it working, but it looks like it's not...

They have fixed the permissions issue since at least v0.1.3 (where it wasn't matching the updated control PermissionResult schema). When it bails out and doesn't actually send you the permission...

Yeah. A ton of it had been trial and error for me, but it's pretty solid. I'm having a blast and getting myself much more deeply familiar with it as...

This PR fixes this issue: https://github.com/anthropics/claude-agent-sdk-python/pull/174

For reference, the `init` messages received right at the start of the SDK agent running have a sessionID and that can be used to resume sessions. BUT - when you...

At ~/.claude If you're running in k8s though, you'll need to make that folder be persistent storage. Otherwise when the container goes poof, so does that history.

Yes, you can via giving it access to MCP tools and instructions at the start of the agent prompt along the lines of "use XYZ mcp tool/resource/prompt to search for...