Inspiration
I regularly use both ChatGPT for Chrome and Codex Desktop.
ChatGPT for Chrome is useful when I want ChatGPT to understand and work directly with the page currently open in my browser. Codex Desktop provides a larger workspace and makes professional, multi-step tasks easier to manage.
However, the task selected in Chrome does not always appear as the active task in Codex Desktop. My current workaround is to completely close and reopen the desktop application. This interrupts my workflow and takes unnecessary time.
The problem
Users working across the Chrome and desktop experiences need a faster and clearer way to continue the same task.
Restarting the desktop application is not a good long-term solution. The experience should provide an explicit way to refresh or synchronize the current task without closing either application.
Proposed solution
Codex TaskBridge proposes a one-click task handoff between ChatGPT for Chrome and Codex Desktop.
The core interaction is a Sync now or Reload tasks action. When activated, it would refresh the available task state and help the user continue the task most recently selected in Chrome.
A future independent companion implementation could:
- Detect the task selected in Chrome.
- Record only the minimum task metadata required for matching.
- Display the latest handoff state.
- Help activate the corresponding task in Codex Desktop.
- Warn the user when tasks have duplicate names or cannot be matched.
- Keep synchronization metadata on the local computer whenever possible.
How I used Codex and GPT-5.6
I used Codex with GPT-5.6 to:
- Analyze the workflow problem.
- Turn a personal inconvenience into a structured product concept.
- Review the OpenAI Build Week requirements.
- Define the intended user experience.
- Explore a possible local-first architecture.
- Identify privacy, matching and conflict-handling requirements.
- Prepare the project description and future implementation plan.
Challenges
The main challenge is that ChatGPT for Chrome and Codex Desktop are separate product surfaces. A participant should not claim access to undocumented internal APIs or the ability to modify the official desktop application.
Because of the submission deadline, I was not able to complete and validate a functional integration. This submission therefore documents the problem, proposed interaction and planned implementation honestly as a concept-stage project.
What I learned
A synchronization problem is not only about transferring data. Users also need to know:
- Which task is currently active.
- Which surface made the latest selection.
- Whether synchronization succeeded.
- What to do when two tasks have the same title.
- How their conversation data is protected.
What's next
The next steps are:
- Validate which task information is safely available on each surface.
- Build a Windows proof of concept.
- Test task matching and duplicate-title handling.
- Measure the time saved compared with restarting Codex Desktop.
- Explore an official in-product refresh action if a supported integration becomes available.
Current status
Codex TaskBridge is currently a concept-stage submission. It is not an official OpenAI product, does not modify Codex Desktop and should not be interpreted as a completed integration.
Log in or sign up for Devpost to join the conversation.