I'm not a fan of this new codex sidebar. I think it introduced a regression where unread threads don't move up the list, I'm forced to click on the bell to see unread threads.
It is either this or I've gotten so used to my own coding agent that I assumed that was how codex works
At this point, deepseek is essentially free. What a difference in price. Now that opencode has even doubled the offering of deepseek.
Well, I'll just say enjoy building! And ensure you you build everything you need to. This is a golden opportunity
This has been motivation behind building CodeInOven.
I was a heavy jetbrains user, although I started with notepad, then notepad++ then straight to jetbrains for student, phpstorm to be precise. I was on that for years till I gradually transitioned to nvim and sveltekit thanks to ThePrimeagen
Then LLM assisted coding came in. I quickly found out that I needed a better way to manage these sessions. Between spending the whole day on opencode, a portion on nvim, others on lazygit and multiple tabs opened on the terminal.
It led me to try cmux thanks to Ben Davis, which worked for a while, but that eventually wasn't enough.
I started enjoying the codex app, but whenever tokens expire it felt like all the energy drained from me and moving back to the UX of opencode was like a downgrade.
However I wanted opencode's flexibility but codex UX. So I built CodeInOven.
Released it 2 days ago and it's been doing exactly what I want, I keep improving it as more needs arise.
We have been shipping features and never tweeting about them. Not because we didn't want to, it's because switching context to write a tweet after pushing code felt like too much. So we built something that does it automatically. Introducing Shiptawk
@Favedevv Don't vibe code the MVP. Use AI for repetitive tasks like tests documentation and refactoring. But don't vibe code it. When the mvp is shipped then let the vibe coding begins.. It gives you 99% control. Lastly, don't use Claude code for your backend, use codex.
The whole "apply to production" flow for Google play store has been quite exhausting lately, I have been rejected 3 times pushing my app release backwards (6 weeks). I'm tired