deer-flow

I fixed up deer flow: https://github.com/bytedance/deer-flow What I did was create docker containers with pandoc, compilers (rust, go, python, javascript) and it can create all manner of reports.

I (not the asked) run deer flow: https://github.com/bytedance/deer-flow

I've been running deer-flow (https://github.com/bytedance/deer-flow) for doing research and it's quite good even with low context sizes.

setup deer-flow: https://github.com/bytedance/deer-flow its pretty good for building any kind of research report using search engines and it manages context corrextly.

i've been playing around with https://github.com/bytedance/deer-flow and they seem to figure out how to get around context sizing issues and has a more automated prompt system. Essentially the problem with current hanrsses is they just can't find/evict context and want to ensure KV cache isn't evicted. If they evict the old prompt and tried to keep all the proper rules, then you get token churn anyway, as what you want is an entirely new chain of events where your rules/guidance sit at the front of the model chain. What we're getting to is there really isn't an economical way for cloud models to do it; you can do it with a local model, but at comfortable speeds, you need smaller sized. I think a good harness via Qwen3.6-35B-A3B is possible, as the token gen is only 3B since that's the active parameters. So it's mostly that to keep rules p

hrm, there's tons of tools to do that, take https://github.com/bytedance/deer-flow the better argument is: you pay to vibe code and you'll pay again in 6 months to vibe fix, etc.