This is great! Especially the GitHub Actions issue/PR integration[0] that’s paired with this is exactly what I’ve been wanting!
[0]: https://docs.anthropic.com/en/docs/claude-code/github-action...
Claude Code SDK
51–60 of 201 posts
Re: Claude Code SDK
#52The new GitHub action is exactly what I have been looking for https://docs.anthropic.com/en/docs/claude-code/github-action... but there doesn't seem to be a way to use it with the Claude Code's Max plan?
As it only accepts an API key as far as I can tell.
Re: Claude Code SDK
#53Earlier quoted context omitted.
Not sure about that golden end state. Mine would be being in a room surround by screens with AI agents coding, designing, testing, etc. I would be there in the center giving guidance, direction, applying taste, etc… All conversational, wouldn’t need to touch the keyboard 99% of the time. That's what I want and look forward one day
Is this a me thing, or a millenial thing? I hate using voice for anything. I hate getting voice messages, I hate creating them. I get cold sweats just thinking about having to direct 10 AI Agents via voice. Just give me a keyboard and a bunch of screens, thanks.
receiving audio = slow
sending audio = fast
Re: Claude Code SDK
#54Earlier quoted context omitted.
Not sure about that golden end state. Mine would be being in a room surround by screens with AI agents coding, designing, testing, etc. I would be there in the center giving guidance, direction, applying taste, etc… All conversational, wouldn’t need to touch the keyboard 99% of the time. That's what I want and look forward one day
Is this a me thing, or a millenial thing? I hate using voice for anything. I hate getting voice messages, I hate creating them. I get cold sweats just thinking about having to direct 10 AI Agents via voice. Just give me a keyboard and a bunch of screens, thanks.
One advantage is speaking is generally faster than typing. Imagine instead of talking to a bunch of AI you’re talking to a room full of coworkers about the architecture to develop.
Re: Claude Code SDK
#55Claude has been left in the dust by Gemini with its million token session and ability to upload a zip file of my entire code base.
I’ve tried Gemini 2.5 Pro a couple of times and honestly don’t like its output. Claude Sonnet 3.7 is much better at correctly understanding and executing my imprecise prompts.
Gemini 2.5 Flash on the other hand has excellent. I’ve started using it to rewrite whole files after talking the changes through with Claude, because it’s just so ridiculously fast (and dependable enough for applying already outlined changes).
Re: Claude Code SDK
#56If I was making an AI code assistant, the last thing I would do is to lock it in to a particular foundation model provider. The only possible way for this to be a successful offering is if we have just now reached a plateau of model effectiveness and all foundation models will now trend towards having almost identical performance and capabilities, with integrators choosing based on small niceties, like having a famil…
"Lock i-"
At this point Claude Code is a software differentiator in the agent coding space.
I am building things related to AI code assistants - we were hacking ways to integrate Claude Code - it was the first thing we wanted to build around.
It's too early to care about lock in.
Need the best, will only build around the best.
Re: Claude Code SDK
#57Claude has been left in the dust by Gemini with its million token session and ability to upload a zip file of my entire code base.
This is Claude Code.
The two work really well with Gemini as a planner and Claude Code as an executor.
Re: Claude Code SDK
#58Earlier quoted context omitted.
> The "golden" end state of coding agents is that you give it a Feature Request (EG Jira ticket), and it gives you a PR to review and give feedback on. I see your point but in the other hand how depressing to be left only with the most soul crushing part of software entering - the Jira ticket.
Say what you will, but this would have the wonderful side effect of forcing people who write JIRA tickets to actually think through and clearly express what it is they want built.
In that timeline, it wouldn't matter anymore since the people complaining about the poor JIRA tickets would be gone.
Re: Claude Code SDK
#59Earlier quoted context omitted.
> The "golden" end state of coding agents is that you give it a Feature Request (EG Jira ticket), and it gives you a PR to review and give feedback on. I see your point but in the other hand how depressing to be left only with the most soul crushing part of software entering - the Jira ticket.
Say what you will, but this would have the wonderful side effect of forcing people who write JIRA tickets to actually think through and clearly express what it is they want built.
Yeah, that’ll be the product-oriented engineers / engineer-oriented product folks.
We will drop the narrow-minded deadweight that can only collect naive requirements, and the coding side that can only implement unambiguous tickets.
Re: Claude Code SDK
#60The way Claude Code is going is exactly what I want out of a agentic coding tool with this "unix toolish" philosophy. I've been using Claude code since the initial public preview release, and have seen the direction over time. The "golden" end state of coding agents is that you give it a Feature Request (EG Jira ticket), and it gives you a PR to review and give feedback on. Cursor, windsurf, etc, are dead ends in tha…
Not sure about that golden end state. Mine would be being in a room surround by screens with AI agents coding, designing, testing, etc. I would be there in the center giving guidance, direction, applying taste, etc… All conversational, wouldn’t need to touch the keyboard 99% of the time. That's what I want and look forward one day
If that’s the future, that means a massive reduction in software engineers no? What you are describing would require one technical product manager, not a team of software engineers.