agy can't run different accounts in parallel (auth = one global Keychain login). But same-account workers each with their own $HOME (isolated ~/.gemini state) DO run concurrently — verified (3 workers, ~8s, no collision).
Idea: let clikae fan out N agy workers on the active account for parallel sub-tasks.
- Cheap to prototype (mechanism proven).
- Real cost is runtime: agy's ~23-25k token/request overhead × N against ONE account's quota; plus dispatch reliability (the hard part — see the headless-dispatch issue).
- Same-account fan-out only. Multi-account parallel is structurally impossible (global Keychain) and ToS-gray for shipped OSS — out of scope.
Defer until a concrete urgent/large/parallelizable agy task appears.
agy can't run different accounts in parallel (auth = one global Keychain login). But same-account workers each with their own
$HOME(isolated ~/.gemini state) DO run concurrently — verified (3 workers, ~8s, no collision).Idea: let clikae fan out N agy workers on the active account for parallel sub-tasks.
Defer until a concrete urgent/large/parallelizable agy task appears.