RedPlanetHQ / RedPlanetHQ/core

CORE extension does not inject / interact with chatgpt.com when running inside ChatGPT Atlas browser

Open
#232 0 comments 0 reactions 1 assignee View on GitHub

@harshithmullapudi is already working on this.

Since Dec 16, 2025.

bug
Dominant language
TypeScript
Stars
2k
Forks
194
Avg merge
12m
Merged PRs (30d)
2

Description

Summary

On ChatGPT Atlas, the CORE extension fails to inject or interact with chatgpt.com, while it works in standard Chromium browsers.

Environment
  • Browser: ChatGPT Atlas (macOS)
  • Site: https://chatgpt.com
  • Extension: CORE / “Core memory” extension (version: ____ )
  • OS: macOS (version: ____ )
  • Account: ChatGPT Plus (if relevant)
Steps to Reproduce
  1. Install and enable the CORE extension in ChatGPT Atlas.
  2. Ensure the extension has site access for https://chatgpt.com/* (or “On all sites”).
  3. Open https://chatgpt.com/ in a normal tab.
  4. Attempt any action that normally requires injection (toolbar button, capture, sidebar, auto‑sync, etc.).
Expected Behavior
  • Content script injects successfully on chatgpt.com in Atlas.
  • CORE UI elements appear (if applicable), and context capture/sync functions operate normally.
  • No permission or CSP-related errors prevent CORE from running.
Actual Behavior
  • No visible injection/UI on chatgpt.com.
  • No apparent capture/sync behavior triggered from the page.
  • Extension indicates it’s active, but there is no on‑page effect.
Diagnostics / Evidence
  • Does CORE work on other websites inside Atlas? (Yes/No): Yes (Google Gemini; copy to features on others)
  • Does CORE work on chatgpt.com in Chrome/Edge? (Yes/No): N/A
  • Extension permissions in Atlas:
    • Site access: Yes
    • Host permissions include: https://chatgpt.com/* (Yes/No): On all Sites

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.