> Rewriting Bun with dynamic workflows
There ya go, the rewrite was for marketing.
Dynamic Workflows in Claude Code
91–100 of 160 posts
Re: Dynamic Workflows in Claude Code
#92Re: Dynamic Workflows in Claude Code
#93Earlier quoted context omitted.
I think the theoretical answer here is this: "Agents address the problem from independent angles, other agents try to refute what they found, and the run keeps iterating until the answers converge." So you will be supplying the "ground truth" (test suite, detailed spec, whatever) and empower an agent to use it to guide the other agents. Currently a lot of people do this sequentially in the form of multiple code-revie…
I don't know, maybe I'm doing it wrong but I feel LLMs add a slop debt, and each agent pass just exuberates it. Like I had an LLM implement a spec and said it was done... Except it had a ton of `casts` everywhere. Okay, my bad, I should have been clear "NO CASTS", so I use the LLM to remove the casts, except it just kept making things more and more complicated and ugly. It took me taking a break and having a shower t…
I've been reading writing Rust for a long while now, since before 1.0. I'm capable of critically evaluating Rust code. I'm also a happy Claude Code user, mostly for lightweight uses like generating scaffolding, prototyping, and debugging.
The pure LLM, no human intervention vibe-coded PRs on Bun since the vibe-rewrite to Rust contain the worst coding horrors I've seen in 20 years of programming.
Setting aside the quality of the change itself (I would have done it differently, for sure: it is pretty straightforward to build a safe abstraction out of this type), the utterly pointless "source-text consistency test" added here is easily the worst example of "test repeats implementation" I have seen in my career:
https://github.com/oven-sh/bun/pull/30728/files#diff-863477b...
Re: Dynamic Workflows in Claude Code
#94I don't really get this. At this point, my limiting factor is not how quickly Claude can self-trudge through code. It's whether Claude is going to do the task correctly or not. I need more mechanisms for controlling long-running sessions and dynamically injecting my thoughts, correction, and nudges rather than faster ways to burn through my tokens without knowing if the results are going to be correct.
Dynamic workflows, in my experience, make Claude more effective at complex long-running tasks. They help precisely with getting Claude to do the task correctly. It feels more like a bespoke build system for the specific task/project than prompting a freeform chat.
[deleted]
Re: Dynamic Workflows in Claude Code
#95Earlier quoted context omitted.
As long as agents are fuzzy (which they will continue to be with the Transformers architecture), the need to validate will continue to exist. I cannot imagine merging code without at least 1 human review.
I've used agents quite a bit and I agree. The current baseline workflow is something like agent output -> human review -> agent refinement -> human review -> agent refinement -> ... But agents are capable of making meaningful improvements to their own output. I'm hoping dynamic workflows move towards something like: agent output -> agent review -> agent refinement -> (cycle to fixed point) -> final human review
[deleted]
Re: Dynamic Workflows in Claude Code
#96Earlier 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…
this feels more like a PR statement than a description of how you used the tool though
Re: Dynamic Workflows in Claude Code
#97A 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.
Hi Boris. Love the velocity of features. Are you planning on adding a secrets manager? Enterprise workflows almost always require an encrypted parameter or calling a secret.
Why should secrets be built in? What's the issue with tool use and something like 1password's or Vault's CLI?
Re: Dynamic Workflows in Claude Code
#98I just hit my Claude Max limit for the first time _ever_ thanks to workflows lol 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?
This is a fundamental incentive issue with any company that does all of training models, building harnesses for them, and offering them as a service.
Re: Dynamic Workflows in Claude Code
#99Cloudflare just launched a feature with this same name, just this month. Why would Anthropic choose the same exact name? https://blog.cloudflare.com/dynamic-workflows/ Also isn’t all of this already easy to do on any of the platforms (include Claude before this and OpenAI too).
[deleted]
Re: Dynamic Workflows in Claude Code
#100Earlier quoted context omitted.
I think the theoretical answer here is this: "Agents address the problem from independent angles, other agents try to refute what they found, and the run keeps iterating until the answers converge." So you will be supplying the "ground truth" (test suite, detailed spec, whatever) and empower an agent to use it to guide the other agents. Currently a lot of people do this sequentially in the form of multiple code-revie…
I don't know, maybe I'm doing it wrong but I feel LLMs add a slop debt, and each agent pass just exuberates it. Like I had an LLM implement a spec and said it was done... Except it had a ton of `casts` everywhere. Okay, my bad, I should have been clear "NO CASTS", so I use the LLM to remove the casts, except it just kept making things more and more complicated and ugly. It took me taking a break and having a shower t…
[flagged]