https://docs.all-hands.dev/ logo
Join Slack
Powered by
Fable 5 is back: - <https://github.com/OpenHands/s...
# proj-agent
m
d
> Until July 7, you can use up to 50% of your plan's weekly usage limit on Fable 5. If you hit your limit, you can continue on Fable 5 with usage credits.
dude these anthropic guys are so freaking stingy smh lol
😂 2
nod 1
b

Yep▾

🤑 2
😂 1
d
oh! also, i got so distracted by the new 50% limit i forgot that originally i wanted to ask if we're going to consider providing Fable access to our dynamic workflows tooling at some point when we evaluate it?
tbh I'm not sure if our dynamic workflows is as polished as claude code's yet but i'd still be curious about it since Fable is basically a dynamic workflow machine
c
Doesn't that work out of the box? cc @modern-fireman-99755
d
Last time i checked the code when we evaluated Fable our dynamic workflow tool was not a default tool used in our evals but i’d love to be proven wrong about that
aha 1
m
I don't think it should be in the standard tool set. It could be an addition that you can use but not always present.
d
the ask specifically is if we can evaluate Fable using our dynamic workflows tool
the ask is not necessarily adding it as an always on standard tool
the reason for the ask is because when i use Fable with Claude Code it uses dynamic workflows all the time. Easily kicking off multiple information gathering agents, implementation agents, code review and adversarial agents, etc. etc. All on its own. It's really extraordinary to watch. It also made me feel like in the near future dynamic workflows will be yet another must have primitive building block as the very frontier models become more and more advanced.
But also when we evaluated Fable the first time, we didn't give it access to a dynamic workflow tool. I'm asking if we could consider doing that this time, maybe on a special run specifically just for that tool. If the team isn't interested that fine but that is the background of my ask here
c
We could try! cc @millions-crayon-32880
m
Although I am curious, we are being more selective with running benchmarks, so not a priority at the moment.
c
What are the priorities?
m
Moreover, it will be crazy expensive as every sub-agent created by the dynamic workflow will run with Fable. Claude code use Haiku in general
d
ok I'm disappointed by the pushback frankly but OK
c
If you set Fable in Claude Code, it uses Fable with dynamic workflows with Haiku subagents?
m
I do think so… or the model can chose the sub-agent and it knows that it should take cheaper models
c
Can we do that?
m
With sub-agents yes (TaskToolSet) and it will be much easier to do that in the agent-canvas in the future For dynamic workflow tool I don't know
3 Views
Open in Slack
PreviousNext
Powered by