ChaosSearch - search combos

[psylligent]

I love chaos mode, I just want it to work for search providers as well, similar to https://github.com/paperfoot/search-cli
Ideally, combos for search approach, or chaos search :)
Plssss

[diegosouzapw]

Hey @psylligent! Cool idea -- love the enthusiasm.

Current state of the world: chaos mode (open-sse/services/autoCombo/chaosEngine.ts) only dispatches chat combo targets, while search is a separate routing surface (web-search tool-call rewriting to custom search providers). So "chaos over search providers" doesn't exist today and isn't a config away.

That said, it is a coherent feature: treat search-capable targets as first-class combo members so a chaos/fan-out strategy could race them. I've opened an issue to track the idea -- will link it here in a follow-up so you can follow progress.

[diegosouzapw]

Follow-up @psylligent -- opened #11128 to track this. It covers treating search-capable targets as first-class combo members so chaos can fan-out across them (ChaosSearch). Subscribe there to follow progress.

[diegosouzapw]

Follow-up @psylligent — a status correction, because #11128 now shows as closed and "not planned", which reads worse than the actual state.

ChaosSearch was analyzed, verified against the code, and moved into the implementation backlog for an upcoming cycle. The GitHub issue was closed as part of keeping the tracker lean, with the tracking living in the internal pipeline instead. The implementing PR will reference #11128 when it ships. "Not planned" is GitHub's label for that closure, not the decision.

The technical finding from the analysis is worth having here: chaos fan-out currently dispatches every panel member through the single-model chat pipeline, while search providers sit on a separate surface entirely. So treating search-capable targets as first-class combo members is not a small wiring change, it means bridging two dispatch paths that do not share a contract today. That is why it is queued rather than quick.

I understand a closed issue is a poor signal for "queued and analyzed". Flagging it here since you would otherwise reasonably read it as a rejection.