openai / openai/codex

Browser API lacks supported document/session identity for detecting same-tab reload/navigation

Open
#41,272 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser enhancement
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

Codex App on macOS with the official OpenAI Chrome extension

What feature would you like to see?

Problem

Codex browser workflows expose a stable tab identity, but I could not find a supported document/session identity that changes when the same tab reloads, navigates, or replaces its current document.

This creates an observability gap for fail-closed governed browser workflows.

Why it matters

A workflow can prove it is still using the same tab, but cannot prove that the document/session inside that tab has not been replaced between an authorization boundary and prompt submission.

URL, title, DOM state, composer state, and conversation identifiers are not sufficient for this.

Requested capability

A supported, read-only document/session identifier that:

  • is stable for the current document/session;
  • changes on reload, navigation, or document replacement;
  • can be observed together with the existing tab identity;
  • is not caller-supplied or forgeable.

An opaque cross-browser identifier would be sufficient; it does not need to expose Chrome-specific internals.

Environment

  • Codex App on macOS
  • official OpenAI Chrome extension
  • stable tab ID available
  • no supported current-document/session identity found

This currently blocks a fail-closed governed browser workflow before model interaction.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by tracing the existing supported tab identity in the Codex App and official Chrome extension, then check how reload, navigation, and document replacement are represented. Done means a supported, read-only, non-forgeable document/session identity is exposed alongside tab identity and covered for those transitions.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
api, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.