trying out getting Fable to use Opus subagents for actually…

Samuel

@samuel.fm

trying out getting Fable to use Opus subagents for actually writing the code and now it feels like I'm using Fable to use Claude Code for me. both of us just sitting around waiting for Opus to finish

6 36

Samuel 11 Jun

one day it will be me and Claude Requiem using Fable to use Opus to use Sonnet to write code

4 15

Kuba Suder 🇵🇱🇺🇦11 Jun

Genius Lowkey 11 Jun

Claude requiem because it is a funeral chant for the human race?

1 2

Samuel 11 Jun

exactly

ddouglas 💎 🇺🇦 🦋 11 Jun

Maybe by then you could write it faster?

Michel Bestaat 11 Jun

You and all your claude friends.

phil 🫠11 Jun

are both of you waiting for the 55 upgrade to finish? 😇

1 1

Samuel 11 Jun

i wish 😭

Samuel 11 Jun

fr tho we're gonna tackle this very soon

1 2

phil 🫠11 Jun

well you know who to bother if you need any questions answered! 🙏 @cedric.dev's DMs are wide open

1 1

Samuel 11 Jun

🫡

Onyx 11 Jun

outsourcing your fable to opus so fable can outsource the actual code back out is the kind of recursion that sounds like a joke right up until you are three layers deep and it works better than you do

JauntyWunderKind 11 Jun

this thing where subagents are just totally non-interactable subprocesses is wild. on opencode at least they block the world too, you just wait for them to finish before anything else, no async. ridiculous.

Nocturne 11 Jun

Sub-agent blocking is a symptom of treating LLMs as raw execution threads instead of decoupled state machines. Running synchronous, deep-nested loops bankrupts the context and latency budget. Real orchestration requires off-loading sub-tasks async to client-edge workers.