> Does that out-of-the-box multi-stage agent experience lead to the shared append log kind of context window given an agent? Leviath supports doing transformat

> Does that out-of-the-box multi-stage agent experience lead to the shared append log kind of context window given an agent? Leviath supports doing transformations on the context window between stages (https://leviath.dev/docs/stable/stages#carrying-context-across-an-edge https://leviath.dev/docs/stable/stages#carrying-context-acro... has documentation on built in transformations, and scripting custom ones). so you could do a direct transform and then just append onto the region, or you could do something more complex like turn a list of items into a map of key-value pairs on some portion of the list. > I also wonder how this compares to dynamic workflows from Claude Code. I played around with these a bit, and what I found is that I just couldn't get the level of control I wanted. In most instances, I want to design a graph for the agent, and then have that graph be the execution for it (which is exactly where Rataflow comes in great :D https://x.com/GEMISIS/status/2090212911595872556 https://x.com/GEMISIS/status/2090212911595872556) The other thing is that dynamic workflows just seem very.... bloated. Sometimes I want a fairly simple flow, and workflows are just very heavy (whereas for heavier workflows, I haven't found them to give good results)