heather

indie dev has time to tweet for weeks instead of fixing the app breaking bugs i reported? bet. too bad for you my toxic trait is building a competitor instead of asking for a refund for your saas that doesn't work as advertised.

@kimmonismus Would super surprised if this wasn’t intentional. Removing easy visibility and awareness from the UI amidst all the rate limit issues gives them more room to obfuscate and deny issues.

Codex Desktop no longer shows visible context/token usage indicator? Bug or did they delete it?

5.5 has been ultra nerfed and rate limits aren’t fixed on the 20x plan. This constant instability is beyond annoying.

@mattjay Hooks

Everyone using Claude code and/or Codex - how are you enforcing them to not pull in new/potentially malicious packages from npm or PyPi?

you can outsource your thinking but you cannot outsource your understanding

Ugh @thsottiaux Codex limits are completely messed up again on the $200 plan. I've done nothing today and my 5h limit is half used and overnight weekly usage has gone from ~70% down to 36%. This is getting pretty ridiculous.

@halveknots @thsottiaux Same here, on $200 Pro plan

@thsottiaux The limits reset reverted. I'm back to 0%! 20x Pro Plan (with party invite increase, if that makes a difference)

For those of you living inside the codex app, what should we prioritize among features, reliability or performance?

Hey @thsottiaux reset limits from yesterday are screwed up and reverted to the prior state all of sudden. Back to the exact weekly value it was on before the reset. I appreciate the extra usage with resets but not if this is going to keep happening and I have to keep wondering when I can use what I'm paying for again on the $200 plan.

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

@Dimillian @PaulSolt Continuing conversations on mobile that were started on Mac doesn’t show responses/output on mobile when turn is complete. But I can see them on Mac. Kind of useless in this state. Need multiple account support.

It’s time. Now you’ve tried our Codex mobile, tell me the top missing feature for your workflow! And yes, we’re aware of the current bugs and shortcomings. We’re working hard on it!

Literally every time I open @cursor_ai.

@trq212 but have you heard your users? #issuecomment-4397737634" target="_blank" rel="nofollow noopener">github.com/anthropics/cla…

"everyday we're trying to obtain more compute to pass on to you, we're sorry if it takes sometime but we're going to acquire as much as we can" you heard the man

Would be nice if the Codex changelog kept up with the updates...

@romainhuet Convex

We’re thinking about the next wave of Codex plugins. What’s one you’re missing today?

@ClaudeDevs Lies upon lies. Repeatedly said nothing was wrong while everyone reported issues. Also zero updates on this bug that makes Claude Code totally unusable: #issuecomment-4260648737" target="_blank" rel="nofollow noopener">github.com/anthropics/cla…

Over the past month, some of you reported Claude Code's quality had slipped. We investigated, and published a post-mortem on the three issues we found. All are fixed in v2.1.116+ and we’ve reset usage limits for all subscribers.

@trq212 @trq212 Why now? This exact issue was reported a month ago: github.com/anthropics/cla…

@EthanLipnik hmm we're looking into this more, are you able to reproduce this pretty reliably? if so would love to hop on a call to debug it

Claude Code has become unusable for me. Does anyone know how to fix the state where it just infinitely thinks with no new tokens?

me watching the llm do the job i used to love

@Joule_00 @seraleev Application itself is not useful. Apple will tell you to pound sand until you have the trademark in full ( which will take a year or more to get).

@seraleev Developers reading this: if you are worried about 4.1c, file a trademark application for whatever your app name is. This gives you a legal standing ground if Apple were to think your app name is similar to another developer's.

Apple just updated its guidelines, and two changes immediately stand out: • 4.1(c) It’s now officially prohibited to use another developer’s icon, brand, or product name in your app’s icon or title – unless you have their explicit permission. (Meaning: no more banana icons or “Nano Banana” tricks.) In short, Apple is tightening the rules around the use of someone else’s intellectual property. • 5.1.2(i) Apple clarified its requirements for handling personal data: you now must clearly disclose exactly where user data is being sent, including to third-party AI services. And most importantly – you must obtain explicit, separate consent before sharing any data with third parties. These changes are especially important for anyone using AI models, third-party APIs, or “borrowing inspiration” from existing brands when designing app icons or names. My advice: take a moment to review your apps, metadata, and data-handling flows. Spending an hour now is much better than dealing with a harsh rejection – or a ban – later.

If there’s a clear answer, AI can do it

@itsMeBennyB Still not Arc

This is not a drill!!! 👀

You are the author of your own life, and it’s never too late to replace the stories you tell yourself and the world. It’s never too late to begin a new chapter, add a surprise twist, or change genres entirely.