Positive users praise the ask-pro plugin wrapper as super useful with GPT-5.6 Pro critiquing Codex code while negative users call the model split unintuitive and the workflow painfully manual.
Based on 5 visible X reactions from 45 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@willdepue That's been my feeling since 5.4 pro days So now my agents use an ask-pro plugin wrapper that's super useful. Does all of it in one go, no silly manual browser control. Super token-efficient https://github.com/Pimpmuckl/ask-pro
@willdepue Or better yet... There's only one model instead of 2 separate models and the model just knows when to be more agentic vs not...
@willdepue you can mention(@) the pro chat session in codex, but u can not do the inverse way, it kinda suck
@willdepue This workflow gap is real. Pro critiquing codex output is painfully manual right now
@willdepue I have been begging for this. It’s at least 100x smarter than codex
gpt 5.6 pro is substantially smarter than 5.6 in codex. it is inordinately good at critiquing and fixing 5.6's dumb ideas and implementations. there must be a better way than asking 5.6 codex to write research reports, me pasting into pro, then copying instructions back!
i think we need 5.6 pro in codex, and we need some integrated system to critique and review what the agent is off doing every 30 minutes. otherwise agents get lost and waste time and do weird stuff without this
@willdepue EZ have it use the browser on its own
Positive users praise the ask-pro plugin wrapper as super useful with GPT-5.6 Pro critiquing Codex code while negative users call the model split unintuitive and the workflow painfully manual.
Based on 5 visible X reactions from 45 accounts; directional sample.
Ask a question below.
Published answers will appear here.