Built a little tool for myself and figured some of you might find it useful.
I love Wispr Flow, but when building UI I kept describing edits, taking screenshots and trying to explain what I was pointing at. Not a great experience...
Everything goes straight into my coding agent via MCP, including a screenshot of what I pointed at, the element under the cursor and what I said. Claude Code, Codex or Cursor then fix it and mark it done.
@tseglevskiy Biggest unlock will be once the model just works with a central continuously updating memory from every part of your life. Across all agents and all tools...
@aka_ssy Agree, also many of the modern memory infra providers overcomplicate their architecture to lean into having a technical edge. In 90% of cases this infra is not even required
OpenAI should add a switch: let Codex use my ChatGPT memory
you can plan a project in ChatGPT with all the decisions and constraints, then open Codex and explain everything again because that context does not carry over.
(OpenAI docs confirm this separation)
this is not a new request either. people have been asking for ChatGPT and Codex memory to work together for nearly a year.
Not asking for Codex to ingest every chat. That's a mess and ChatGPT's idea of the code goes stale. Asking for an option, off by default:
- choose what Codex can access (saved memories only or one project)
- see what context Codex is using
- let users exclude anything or turn it off
If the product line is "one account, ChatGPT and Codex" the memory should be able to cross when you say so. Right now the user is the sync layer.