4 ms·
Both Codex and Claude have trained their models to their harnesses. There are some experimentations by Igor Warzocha to extract Codex shapes and put it in Pi:
by whazor 2mo ago
Both Codex and Claude have trained their models to their harnesses.
There are some experimentations by Igor Warzocha to extract Codex shapes and put it in Pi: https://github.com/IgorWarzocha/howaboua-pi-stuff/tree/main/packages/pi-codex-conversion https://github.com/IgorWarzocha/howaboua-pi-stuff/tree/main/...
I'm expecting every model will have a fine tuned Pi extension at some point.
- rcarmo 2mo agoI’ve been using both families of models inside pi/piclaw (https://rcarmo.github.io/projects/piclaw/ https://rcarmo.github.io/projects/piclaw/) and I assure you they work _better_ in that environment than in the originals. The models are not trained to the harnesses, the harnesses provide cues that the models follow.
- whazor 2mo agoYou can see the approach in his post: https://howaboua.dev/writing/how-i-gave-pi-17-tools-without-loading-17-schemas/ https://howaboua.dev/writing/how-i-gave-pi-17-tools-without-... The result: 38% fewer startup tokens, 17 tools exposed through just three schemas, and 19 skills loaded only when needed.
- Szpadel 2mo agoin my experience pi does much better than codex for compaction and token use. And this is the main reason I switched to it. migrating to the same compaction and exact tools as codex uses will make it at the same level as codex so what benefit will it have over codex? sure you can customize tui to your liking and add something on top, but the efficiency gains will be gone