81–90 of 160 posts
A few of us from the Claude Code team will be hanging around if anyone has questions! Very excited for this launch -- dynamic workflows have been a game changer for engineering here at Anthropic. Can't wait to hear what you think.
I have my own version and the workflow keyword conflicts with it rather heavily. Will there be a way to disable that prompt section/keyword?
I am diffing Claude Code with them, I tend to agree with the analysis.
So far, versus my system, there are tradeoffs, but the dynamic workflows are over tuned to use way more agents that I have ever found add value.
It used 8 to diff our systems. I would have used 4, for example.
Is this equivalent of DAGs for sub agents inside claude code? Can i pause and resume/retry workflows? How stateful are they?
Really appreciate it someone claude code can throw more light on above. I’m trying to see if I can get langgraph equivalent DAGs here.
Like 90 agents ran to do a code review of a fairly small package I have.
They're really looking for us to increase token usage aren't they?
Earlier quoted context omitted.
How do you guys plan feature support between the CLI and Claude Desktop?
We generally build features into the Claude Agent SDK, which is shared by CLI, Desktop, VSCode, and cloud.
Eg is Zed capable of using a Claude Code Subscription?
Earlier quoted context omitted.
Hi Boris! Thanks for Claude Code. Is there an example of how y'all use Dynamic Workflows internally that you could share with the rest of us here so that we can mimic something similar?
Hey, yep. A few things I personally used dynamic workflows for over the last few weeks: 1. Autonomously landed 20+ optimizations to reduce Claude Code's token usage by ~15% 2. Ported tree-sitter, color-diff, yoga-layout, and a number of other WASM and Rust native modules to TypeScript, improving CPU and memory use by 2-10x in the process 3. Made our CI faster, and repeatedly found and fixed flaky tests (with /loop) 4…