Brick is a cheap & smart spatial router that plugged into claude code redirects the query to the best model in your pool. You can use it to save tokens, use other providers in claude code without changing models by hand or making your plans way longer in code time
For sure that’s absolutely true because you’re switching context from a kV cache to another one. We introduced 2 algorythms for solving this :
1) sticky : switches model only when convenient
2) smartsqueeze : fast advanced compression for reingesting context
If you switch models, you have no cache. There is no way to change this as they depend on sending the tokens through the weights and saving the computation results. Different model, different tokens, different weights, different calculation.