We know you have concerns on how Codex works and its undetectable nature. Here is our address them.

Browser Sandboxing

When you participate in a coding interview on platforms like HackerRank, CoderPad, or CodeSignal, all of that activity runs inside your browser’s sandboxed environment. Modern browsers isolate each tab in its own process, enforcing strict permissions so that code executed in one tab cannot access your file system, inspect other applications, or leak data beyond that tab. In other words, what happens inside that interview tab is walled off from the rest of your system.

js
// Inside a webpage you might see this…
window.addEventListener('blur', () => {
  console.log('Tab lost focus—but nothing beyond that!');
});

What Interview Platforms Can See (Inside the Bubble)

Within their own sandboxed tab, interview sites can monitor a handful of browser‐level events:

• Tab Blur/Focus: They know when you click away from the tab or switch windows.
• Paste Events: They can catch large or frequent pastes into the code editor.
• Webcam / Screen‑Share Streams: If you explicitly grant permission, they can view your camera feed or anything you choose to share.

But crucially, they cannot see anything outside their sandbox:

• They don’t know which other app or tab you opened.
• They cannot list or inspect other running processes.
• They cannot read memory or capture keystrokes outside their own context.

Why Codex Interview Is Different & How It Counteracts Detection

Codex Interview is not a browser extension or in‑page script. It is a native desktop application that runs in parallel with your other apps — completely separate from your browser. with these key advantages:

• Operates Outside the Browser The browser sandbox has zero visibility into our process or windows. We don’t inject code into the page; we render our overlay independently.
• Excluded from Screen Capture & Sharing We leverage standard OS APIs (e.g. SetWindowDisplayAffinity on Windows, and NSWindow.sharingType = .none on macOS) to mark our window as “do not capture.” This is a public, documented feature used by privacy‑focused apps.
• No Focus Steal / Tab Change Our global hotkeys (e.g. ⌘+B or Ctrl+B) are registered at the OS level. Toggling the overlay does not trigger a blur event in the browser, nor does it change the active tab.
• Transparent Overlay & Click‑Through Mode We can position a semi‑transparent window directly above the coding area. When in click‑through mode, your clicks and typing go straight to the browser while you still see our hints beneath.
• Real‑Time Collaboration Codex Interview streams your code edits and your teammate’s feedback over a secure WebSocket connection directly onto the overlay canvas. Our desktop app never logs hotkeys or captures screenshots.

js
// No browser API can detect or interact with external native overlays.
if (window.myOverlay) {
  // Inaccessible — browser scripts can’t reach native system processes!
}

What About Dedicated Proctoring Apps?

Some high‑security assessments ask you to install a native proctoring client. In theory, that could see everything on your desktop—but in practice, most companies avoid it because:

• It poses a significant security risk (potential for abuse).
• It triggers serious privacy concerns.
• It erodes candidate trust and goodwill.

Until those platforms mandate a full‑blown proctoring client, Codex Interview will continue to operate unseen.

The Bottom Line

Because coding interviews run inside a locked‑down browser sandbox—and Codex Interview runs entirely outside that sandbox using legitimate OS features—standard detection methods simply can’t spot us. We built Codex Interview from the ground up to respect both browser security boundaries and user privacy, ensuring that your interview session remains yours alone.