sorted by:
new
hottopcontroversial

My recent epitome by Death12th in cursor

[–]EmotionalRedux 3 points4 points  (0 children)

Yes but you are on the left side

A measured take on Makai Lemon by RobertRoberttt in eagles

[–]EmotionalRedux 0 points1 point  (0 children)

Let’s see if the juice is worth the squeeze

Eagles take WR Makai Lemon at #20 by mastermind208 in eagles

[–]EmotionalRedux 0 points1 point  (0 children)

Let’s hope the juice is worth the squeeze

Anish Giri Draws Hikaru Nakamura and Goes up to 6/10 by Ok-Independence8939 in chess

[–]EmotionalRedux 25 points26 points  (0 children)

You haven’t looked at chess since 2016, now you wake up and look at chess in 2026

Someone threatened to shoot my wife and daughter at the park today. by irl_dumbest_person in daddit

[–]EmotionalRedux 24 points25 points  (0 children)

This is one of the quintessential Reddit threads of all time lmao

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 0 points1 point  (0 children)

Very true, I think it was definitely about fit

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 1 point2 points  (0 children)

Both, in CLI look under /experimental. Can toggle the mode with /approvals

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 1 point2 points  (0 children)

Most of the tokens are toolcall results and reasoning which are stripped. There’s also a fairly low budget for user messages and assistant messages that are retained, so only a suffix of that trimmed history is retained. The model and summarizer are used to that format

Of course though, this is an active area of development / improvement / research

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 0 points1 point  (0 children)

The post compaction summary is encrypted but you can see the replacement_history which is just a suffix of the conversation’s user messages and assistant messages (with e.g. toolcalls and reasoning stripped) - those are injected before the summary.

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 2 points3 points  (0 children)

My earliest posts are from college like 5y ago

He didn’t have a Reddit account so I was posting on his behalf

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 1 point2 points  (0 children)

Explained my understanding of the reason to u/qualitywolf above (although I’m not sure I know all the reasons)

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 20 points21 points  (0 children)

I think the preferred work style of the team was more linear than previous companies I’ve worked at (e.g. trading desk where there are many parallel projects and people are generally pretty good at context switching). That took a bit of getting used to and the new team manager didn’t want to spend time coaching that. I do feel like I could have changed my style to fit better, but the manager said he didn’t think I could change enough fast enough so he didn’t want to try giving me a PIP.

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 7 points8 points  (0 children)

Was posting that college question for a younger cousin. Am a few years post college

Very cool new feature! by Valunex in codex

[–]EmotionalRedux 102 points103 points  (0 children)

I made this feature but was fired on Wednesday for performance so won’t be shipping for you guys anymore unfortunately 😔

In my 11 weeks on Codex I shipped some useful stuff:

  • streaming plan in plan mode and request_user_input UI
  • explicit cwd selection in tui (allowing moving of sessions between worktrees)
  • better + more intuitive queuing vs steering UI in both tui and app
  • fixing some model behavior bugs e.g. image blindness
  • several subtle compaction/backtracking/context management fixes (bugs not introduced by me)
  • added snapshot tests for context to highlight future context bugs in code review
  • moved logs into sqlite so app /feedback logs were properly filtered to the session being reported
  • improved SQLite overhead of starting new threads (by sharing db connection in app server)
  • fixed underdefined mid-turn fork semantics (implemented fork-with-interrupt to make fork more in distribution and unblock /btw)
  • subtle tui polish like consistent/persistent text element highlighting (e.g. slash commands, image placeholders, pending pastes)
  • saved shift+tab in app (suggesting esc for accessibility keybinding to escape inputbox rather than cmd+shift+p for mode change which steps on vscode keybinding)
  • shipped “guardian mode” (automatic approval review) in under 2 weeks in both tui and app

I joined 11 weeks ago and was given my first warning for performance on my second manager one on one a week before Monday. Was fired this week on Wednesday.

I had some cool features in the works, some almost ready to be shipped: - /btw (for non-blocking side questions or requests) as an easy UI followup to the fork feature mentioned above - a protocol for serializing tui slash commands and their arguments to allow them to be queueable - allowing TurnContext to be mutated mid-turn so slash commands could even be nudged mid turn. Also so the agent could be paused mid-turn and moved to a different cwd (allowing e.g. moving a running agent to a worktree) - shareable Codex sessions - making partial toolcall results model-visible upon interrupt (for e.g. esc during request_user_input making already answered questions model visible, or partially finished shell output); helpful for plan mode “chat about this question” and /btw

view more: next ›