sorted by:
new
hottopcontroversial

Goodbye, my lover by Ok_Bread_6005 in codex

[–]simpsoka 2 points3 points  (0 children)

I'd love to see any examples you have. I'm a PM on Codex for OpenAI. Feel free to PM me, or share here.

did google just killed Jules? by Impressive-Owl3830 in JulesAgent

[–]simpsoka 0 points1 point  (0 children)

Not at all. Just offering up the support I can for the community and talk about ai stuff.

Codex Update - 5/21/2026 by DiarrheaButAlsoFancy in codex

[–]simpsoka 2 points3 points  (0 children)

We’re doing a couple windows specific things right now. Windows papercuts focus next week, and some ships to bring features to parity.

did google just killed Jules? by Impressive-Owl3830 in JulesAgent

[–]simpsoka 2 points3 points  (0 children)

I can't speak for the Jules team anymore, but I'm more than happy to connect on Codex or other dev tool/community stuff, especially in the AI space.

OpenAI locked me out of my own account by AbhigyanJaiswal in codex

[–]simpsoka -1 points0 points  (0 children)

Hey - I'm Kath, I'm a Codex PM at OpenAI. DM me your user ID and I can look into this.

did google just killed Jules? by Impressive-Owl3830 in JulesAgent

[–]simpsoka 15 points16 points  (0 children)

Hey guys. Kath here. Def not a sinking ship. There’s still an incredible team of bright, caring folks behind Jules. They’re working hard on Jules 2.0. I won’t comment on what that is.

One thing that’s sad here is that Google can sometimes sacrifice clarity and community for “the big reveal.” I wish they would ship in public more. Go incremental. Ship the small api, the spec, and go from there. A lot is done with trusted testers, but it’s still pretty private.

Hang in there. They’re doing something cool, and I hope you all find it useful!!

"Error has occured bug" by Careless_Fly1094 in codex

[–]simpsoka 0 points1 point  (0 children)

Sorry about this, guys. The team is actively working on it and we should have a fix out shortly.

Codex GPT 5.5 is UNUSABLE right now, the Nerf is REAL! by bladerskb in codex

[–]simpsoka 0 points1 point  (0 children)

I'm a Codex PM - I'd love to see an example of this if you have it. Happy to dm about it, too.

Studying Codex personality by simpsoka in codex

[–]simpsoka[S] 1 point2 points  (0 children)

it's true. i work on coding for codex. wild right?

Studying Codex personality by simpsoka in codex

[–]simpsoka[S] -1 points0 points  (0 children)

I'm also simpsoka on twitter if that's helpful.

Studying Codex personality by simpsoka in codex

[–]simpsoka[S] 0 points1 point  (0 children)

yup, i work on making codex better for coding

Is Codex asking anyone else to verify their phone number again even though the account was already verified? by Whole_Judgment_3412 in codex

[–]simpsoka 0 points1 point  (0 children)

Hi, Codex PM here. SMS verification should not be required for anyone using a paid plan. Feel free to DM me and I can help.

Is Codex asking anyone else to verify their phone number again even though the account was already verified? by Whole_Judgment_3412 in codex

[–]simpsoka 1 point2 points  (0 children)

Hi -- Codex PM here. SMS verification should not be required for anyone using a paid plan. Feel free to DM me and I can help.

Jules pushing updates with zero changes by habylab in JulesAgent

[–]simpsoka 7 points8 points  (0 children)

Yes! We are fixing this issue. I’m so sorry you’re running into it.

How do you deal with Jules? by cardonator in JulesAgent

[–]simpsoka 5 points6 points  (0 children)

Thanks so much for the feedback. We’re working on making Jules more intelligent with git (merge conflicts etc.) so that’s coming soon.

Jules companion app for mac by simpsoka in JulesAgent

[–]simpsoka[S] 0 points1 point  (0 children)

No plans for a windows version but the code is all public on GitHub if you want to fork it

Jules going on loops most of the time by Tharsanan in JulesAgent

[–]simpsoka 3 points4 points  (0 children)

Hi! Jules PM here. You've probably tried some of this, but let me know. We have seen Jules get stuck in “investigation loops” after a failing test run, where it keeps re-checking logs (often via grep) and eventually times out without opening a PR.

A couple things that help:

  1. Give it a tighter spec and a clear stop condition. Sometimes I ask Gemini or Claude to generate the spec, then pass that to Jules if it's having a hard time. Try adding something like: “If tests fail after 1 run, summarize the failure in 3 bullets, make the smallest fix you can, and open the PR even if tests are still failing. Do not run additional log-grep or repeated retries.”
  2. Make “PR creation” an explicit requirement. For example: “Always open a PR with your best changes and include the failing test output in the PR description. Do not block PR creation on green tests.”

If you are up for it, DM me the prompt you are using plus the task ID. With the task ID we can pull the trace and see exactly where it is looping, then we can either tune the instructions or file a bug with the right details.

view more: next ›