Thomas EinwallerFeb 26

Support colleague: "Customer isn't getting certain emails, can you check?"

Pasted her message into Codex CLI, right in the email service source directory. 5 minutes later it explained why
the system behaves exactly as designed — no bug.

Then asked it to draft a support reply a non-technical person can understand.

AI coding agents aren't just for writing code. They're incredibly fast at understanding existing codebases and
translating technical behavior into human language.

Show threadsaxxFeb 26
@tompson Can you tell us about the actual root cause in this case, except „works as designed“? How did Codex solve it?
Show threadThomas EinwallerFeb 26
@saxx the customer thought he and his colleagues should get a mail in that kind of event. But it was designed as only the administrator should get an email in that kind of event. Codex figured that out by the subject of the mails and looking at the logic in the code for sending out those mails.
Show threadsaxx
@tompson Cool 😊 I know you‘re quite hyped about these possibilities for a while now: Out of curiosity, how much would you be willing to pay for the current level of functionality/usage allowance in case OpenAI will increase prices to cover costs?
Feb 26 at 5:56pmIvory for iOS
Show threadThomas EinwallerFeb 26
@saxx I'm not sure if it will get that more expensive. Currently we are using multiple tools in parallel and I hope we can consolidate later but we are already spending a lot per month
Show threadsaxxFeb 26
@tompson Since even OpenAI are admitting that they loose money which each subscription, I think it’s safe to assume it will need to get much more expensive to cover even their OpEx. Not sure how they’ll ever get ROI on their CapEx.
Show threadThomas EinwallerFeb 26
@saxx I think I don't really get the point here. The logic would then be to use them now when they are cheap and decide later, when they are more expensive, if you still want to use them.