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

121–130 of 160 posts

Re: Dynamic Workflows in Claude Code

#121

Post by clickety_clack »

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.

A more interactive Claude code would be great instead of 50 “here’s a tiny snapshot of a change shorn of the context you need to understand it. Yes or no?”s

Re: Dynamic Workflows in Claude Code

#122

Post by unshavedyak »

fredoliveira wrote: post #112
unshavedyak wrote: post #88

Earlier quoted context omitted.

VSCode has an official client? Given IDE usage is being restricted from Claude Code via the CC SDK tokens going to the Claude API rather than your CC Subscription, i'm unclear which IDEs can actually use claude code now. Eg is Zed capable of using a Claude Code Subscription?

> is Zed capable of using a Claude Code Subscription? Yes. Zed connects to Claude Code via ACP.

to be clear, i'm referring to the recent fact where it appears that they're disabling all Claude Code (Subscription) usage from the SDK. Which ACP would be included on.

As usual though it's not super clear exactly what is allowed or not.

Re: Dynamic Workflows in Claude Code

#123

Post by Zopieux »

Who, beyond Anthropic themselves, can afford such purposefully wasteful uses of LLMs?

"the model sucks a bit so we just have best-of-4 & adversarial reviewing agents; surely one more agent will do the trick"

Re: Dynamic Workflows in Claude Code

#125

Post by NichoPaolucci »

vadansky wrote: post #60
wrs wrote: post #28

Earlier 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’m in a similar boat. I find that longer sessions will introduce “noise”. I have to be extremely explicit to avoid adding this noise, as it pollutes the future output of the models. Sometimes it’s innocuous, other times it can derail sessions as the 2nd or 3rd pass introduce even more of their own noise.

To me, it seems the models are inherently designed to do this. Creating more verbose output than input, generating plans introduce things I didn’t ask for, extras, more “defensive” code that makes sense at first but is completely unnecessary in practice… I find it exhausting, but it’s important to pare down the output / plans at each stage and trim the generated stuff that isn’t needed.

Re: Dynamic Workflows in Claude Code

#127

Post by sermakarevich »

Not sure why Claude does not have AskUserQuestion implementation that works for spawned sessions: subagents, teams, workflows. Without it, spawning hundreds of subagents and wait for final result without single input feels a bit risky.

Here is the solution to it. Built on a SQLite DB and MCP, blocking until the question is answered, supporting all possible question types, with a CLI or web interface for answers, `ask_human_question` fills the gap in efficient subagent management.

https://news.ycombinator.com/item?id=48320233

Re: Dynamic Workflows in Claude Code

#128

Post by brammertottens »

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.

[dead]
Post reply on HN