@daniel_mac8: Codex Pro tip: turn Codex into a research engineer. Take any new agent paper and: 1. Ask: “How would this work in Codex…
Summary
A tip for Codex users to implement agent research papers directly into their Codex environment using goal mode and local config, with SkillOpt as an example that improved a GPT-5.5 agent by +24.8 points.
View Cached Full Text
Cached at: 05/26/26, 03:11 PM
Codex Pro tip: turn Codex into a research engineer.
Take any new agent paper and:
- Ask: “How would this work in Codex?”
- Enter /goal mode
- Set the goal to implement it in your local config
There’s a wave of research coming out on harness engineering: skills, memory, eval loops, tool use, scaffolds, agent feedback.
This workflow lets you pull those ideas into your actual Codex environment instead of just bookmarking them.
SkillOpt is a perfect example.
It treats agent skills as trainable external state: run a rollout, edit the skill, validate, keep what works.
In the paper, SkillOpt improved GPT-5.5 inside a Codex-style harness by +24.8 points over the no-skill baseline.
That’s the loop you can implement today. It’s already possible:
research paper → Codex goal → local agent upgrade
Similar Articles
@reach_vb: Codex Tip: ask Codex to look through your past sessions and turn repeated prompts into reusable skills + subagents you’…
A tip for using Codex to turn repeated prompts into reusable skills and subagents, improving workflow efficiency for tasks like CI failure checking and PR review.
I replaced a fairly complex Reddit research agent with a Codex skill. I'm starting to think many "agents" should just be skills.
The author argues that many research agent projects can be replaced by 'skills' running inside existing harnesses like Codex, sharing their experience implementing a Reddit customer-research workflow as a Codex skill with only deterministic Python helpers, and questioning when custom agent runtimes are truly needed.
Harness engineering: leveraging Codex in an agent-first world
OpenAI describes an internal experiment building a production software product with zero manually-written code using Codex agents, achieving approximately 10x faster development with 1.5M lines of code written by AI in five months. The team learned that effective agent-driven development requires engineers to focus on systems design, scaffolding, and feedback loops rather than writing code directly.
@jxnlco: jason from the codex team here, heres a draft on codex maxxing and the primatives i use on a daily basis https://jxnl.g…
Jason Liu shares his workflow primitives for using Codex effectively, including durable threads, voice input, and steering to extend AI agents beyond coding into knowledge work.
@daniel_mac8: This is an amazing Codex tip. Works even better when paired with persistent Codex memory files in Obsidian. Gave me 8 r…
A tweet highlights a Codex tip using the openai/skills repository to install relevant skills, enhanced by persistent memory files in Obsidian.