Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Dynamic Workflows in Claude Code

claude.com

Post reply on HN
Print view View original

61–70 of 160 posts

Re: Dynamic Workflows in Claude Code

#61

Post by bryan0 »

bcherny wrote: post #43
bryan0 wrote: post #39

Earlier quoted context omitted.

Thanks to you and the anthropic team for developing such exciting tools! The blog post seems to position workflows for “breadth”: generating fixes / refactors against large code bases. What about for “depth”: developing specific new features and functionality end-to-end? I’ve struggled to make this work reliably using the current experimental agent teams. Does this replace or augment that functionality?

Yes, it also helps! That's a place where raw model capability is the most helpful, but we do find that some dynamic workflow configurations can be helpful too.

Cool! If you can point to any examples of those types of workflow configurations I’d be super interested. For example, to have a team of agents review a PR and iterate on it until all requirements are met including UX, security and product functionality goals. If they could “converge” to a solution like workflows seems to be designed for that would be amazing.

Re: Dynamic Workflows in Claude Code

#62

Post by brap »

>Claude dynamically writes orchestration scripts

So, is this like a skill the LLM should follow, or an actual "workflow" in the deterministic sense?

If it's the former, is it even reliable for long running tasks? If it's the latter, can users interact with it?

Re: Dynamic Workflows in Claude Code

#63

Post by isoprophlex »

rahkiin wrote: post #37
bcherny wrote: post #19

Earlier quoted context omitted.

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…

You _reduced_ its _efficiency_? Why do you make CC more inefficient?

Maxxing everything is all the rage. Gotta cpumaxx or bossman isnt getting his money's worth

Re: Dynamic Workflows in Claude Code

#64

Post by JimJohn4292 »

bcherny wrote: post #19
thallavajhula wrote: post #13

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…

Boris, what are your thoughts on WASM as a technology and it's practical implications for AI in the future?

Re: Dynamic Workflows in Claude Code

#65

Post by aabdi »

wrote something similar for my own use/work stuff; seems everything is converging towards similar ideas.

IMO, this style of workflow/agentics is how all SWE'll look like long term. Automate everything into a big pipe-y thing. How it's gonna be modelled is up in the air though. lots of different approaches:

mine: https://github.com/portpowered/you-agent-factory

https://github.com/ComposioHQ/agent-orchestrator

https://github.com/gastownhall/gastown

https://github.com/openai/symphony

Re: Dynamic Workflows in Claude Code

#66

Post by franze »

bcherny wrote: post #10

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.

just wanted to say thank you, just did a 2 days "ai computer use" workshop - think a virtual desktop on hetzner with claude code in yolo mode, a github account, vercel and logged in into a google account and claude had all the credentials and then let a mix of marketing / product manager / sales / customer support let loose. 2k token budget ... and just let them see do magic again and again.

thx for all that amazing tec and save ai

Re: Dynamic Workflows in Claude Code

#67

Post by afro88 »

I tried this out yesterday - lucky enough to have access through EAP at work. The workflows that are generated are quite good - smart parallelisation and phasing. End results for larger chunks of work are also much better, which I attribute to more of the work having clean context windows (Opus 4.7 is unusable past 200k conversation length, and each subagent ends up using less than that IME). They also seem to have a validation phase hint in the workflow generator which also helps a lot. Speed is a bonus.

You can achieve a similar result manually prompting to use subagents, yes. But the TUI for in flight dynamic workflows is really nice - great visibility into exactly what's happening.

Honesty, for anything larger than a 1 shot PR, it's worth firing off a workflow for better automatic context management alone (more work done in the first 20% sweet spot)

Re: Dynamic Workflows in Claude Code

#68

Post by afro88 »

brap wrote: post #62

>Claude dynamically writes orchestration scripts So, is this like a skill the LLM should follow, or an actual "workflow" in the deterministic sense? If it's the former, is it even reliable for long running tasks? If it's the latter, can users interact with it?

It's the later. You can view it and see fine grained progress, but you can't interact with it. I hope that's coming next, because it would be useful to steer later phases or even agents

Re: Dynamic Workflows in Claude Code

#69

Post by sangeeth96 »

bcherny wrote: post #19
thallavajhula wrote: post #13

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…

> 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

Curious to learn more on this (unless there’s a write-up in the works). I’m naive on this matter but:

1. is this because it’s higher cost when passing objects back and forth across the JS/native boundary? 2. Does this have anything more specific to do with use of Bun? 3. is the stance for claude code then to keep all the deps in raw TypeScript? 4. How do you folks keep these ported deps up-to-date?

Re: Dynamic Workflows in Claude Code

#70

Post by chinathrow »

SkyPuncher wrote: post #12

I 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.

I think for now it's better to convert tokens into code/library code and then work with that for deterministic results rather than relying on Claude being correct or not.
Post reply on HN