Moved to Claude for daily stuff because of TOO MANT bugs/tradeoffs in windows. Especially with WSL integration.
Automations don't work, performance is poor, agent in WSL in UNSABLE, no computer use and browser automation in EU, and much more...
https://t.co/OEswM1iW86
For code, I still use Codex with CLI from wsl. But it's not a choice I like compared to the app...
@zeeg@amorriscode What about giving codex the ability to write custom order/filtering rules? "Keep threads about x pinned in the folder, temporary ones drop them" etc
@iAlexeyRu@LexnLin It's like the 3rd time. At this point it looks misleading and likely achieves the opposite of what they want. At least for power users
@trq212@bcherny would be cool if we could set auto fork + compaction for big threads of which cache is about to expire.
Right now I have a thread with 600k tokens, I forgot about it for a sec and cache expired. I would love to resume from a compaction, but it'd waste the full conversation load and compaction. I would have loved if it automatically forked and compacted, giving me the option to resume from there without wasting limits.
@Dimillian I really like opening a side chat, sending a raw prompt and asking it to rewrite it for the main thread. It works amazing and you guys should look into that.
It's like an always updated prompt optimizer. Tho it does need some prompt engineering skill to get it to work proper