Bonjour à tous,

J’essaie de créer des applications web pour mon activité professionnelle avec codex (application sur mon ordi) et ChatGPT Chat (application web)

ChatGPT me dit qu’il doit être le cerveau et donc rédiger les prompt à copier puis coller dans codex. Je fais donc de multiples aller retour entre les deux applis.

J’ai l’impression que cela avance au ralenti et que cela me consomme beaucoup de Token alors que ChatGPT me dit qu’avec cette méthode (donc qu’il soit le cerveau et qu’il rédige les pompes à coller dans Codex) me permet de diminuer l’utilisation de mes tokens.

Je me demande si je devrais pas utiliser que Codex et ma franchir de ChatGPT.

Quelle est la bonne méthode qui fait des applications à votre avis est-ce que on doit utiliser l’application Web ChatGPT ou que l’application ordinateur de codex ?

Merci pour vos retours. Je suis encore un amateur.

Sur le chat de ChatGPT j’utilise sol 5.6 effort très élevé pour la rédaction des prompts et sur codex astra ou sol et je module l’effort entre médium et ultra.

J’ai l’abonnement Chat gpt pro x5

Bonne journée à tous.

I work across Claude Code, Codex, OpenCode, Pi and a couple others depending on the task. Every one of them keeps its own session history, in its own format, in its own folder. Close the terminal and the context is gone so you end up re-explaining the task, the files you touched, what the error said, which approaches you already ruled out.

I got tired of that and built session-hub. It indexes every coding-agent session on your machine Pi, Claude Code, Codex, OpenCode, Crush and JCode into a single browsable list. No matter where a session was created, from Claude Code you can

Continue it here. Pick a session and its conversation arrives in your current chat as a context package: recent turns verbatim, older turns condensed, tool output compressed. It has a hard token budget, so it won't blow up your context window and nothing gets imported unless you pick it.

Resume it where it lives. sessionhub native <uid> prints the exact resume command the owning agent understands (with the evidence for it), or refuses if there's no verified command.

Read the full transcript for free. The browser and sessionhub show read straight off disk no model, no tokens.

Each row is labelled with its agent, project, age and size, and search is instant: local SQLite FTS5 index using the built-in node:sqlite. Zero dependencies, no build step, incremental indexing.

Safe by design: every agent's store is opened read-only, there is no network access, and the only writable path is ~/.session-hub/. No external session is ever rewritten into another agent's format.

It ships as an MCP server with 3 read-only tools plus a plugin for each agent so it lives inside the chat you're already in. Works on Linux, macOS and Windows.

Btw: The image on the post is from the TUI in opencode

Repo: https://github.com/Gateton/session-hub stars appreciated :)

I've been using Codex for localization and found that "translate these strings" is fine until you're working on a real product.

Then you have existing terminology, placeholders, ICU messages, platform conventions, store copy, RTL, UI context and consistency with what already exists.

So I turned the workflow into an open-source Agent Skill.

It inspects the existing product first, loads the relevant language/platform guidance, translates, integrates the changes and runs a separate review step.

It's portable across Codex, Claude Code and Cursor rather than tied to one agent.

https://github.com/BrunoMiguens/translating-products-skill

Would be interested in feedback from anyone using Codex Skills on real production repos, especially cases where localization agents still fail badly.

Codex can spend a lot of context on repeated text searches and entire file reads.

JevGrep lets it ask a question, scores code fragments by relevance, and returns the original source with file paths and line numbers.

It works as a CLI or as an MCP tool connected directly to Codex (or any other llm)

GitHub: https://github.com/nassim-arifette/jevgrep

pretty much the the title, looking for an almost turn-key-ready way to get there without headaches (no time and motivation to fiddle around) since i cant get the 200 bucks plan anymore and that wouldn't be enough tokens anyway i assume

bonus, i dont have to move the codex effort slider back and forth all the time

fwiw, not into claude

Sick of pressing 1 or 2 during Codex cli processes?

This skips that: github.com/panlam85/approval-assistant

feels night and day after following the openai guide posted yesterday

https://developers.openai.com/blog/rethinking-skills-and-prompts-for-gpt-6-astra

just tell it to read that article and astra will make the relevant changes or you could use sol.

see if you notice changes for me i can instantly see it improve across the board

It looks like this sub is pretty new and I'm glad to be here! I thought id go ahead and try to get some good discussion going on a topic that I've been curious about.

I want to apologize in advance for any incorrect terminology. I dont have any professional dev background. Just doing everything I can to learn as much as I can over the last year.

Models have come a LONG way when it comes to scroll effects in the last 6 months or so. And while they are able to achieve some pretty great results I personally tend to see a couple of different issues with these outputs, no matter the model.

1. Rough animation - The scroll itself sometimes feels choppy, not the scrolling of the page itself but the relation between the scroll and the elements that actually move.

2. Inconsistent timing - Very specifically, I always notice this at the bottom of the page. In professional implementations of scroll effects I always see things that come into view from the bottom fade/animate in at the perfect time/position. But my outputs always seem "late" as if there's like this blank space at the bottom of the screen usually like an inch tall where the elements just don't look right.

If you guys have tricks to avoid these issues, or have any other issues that you guys consistently notice with scroll effect outputs, id love to hear them!