OpenAI Might Be Experimenting with a Windows Recall-style Function for Its Codex Coding Agent: Implications for Users

Try Our Free Tools!
Master the web with Free Tools that work as hard as you do. From Text Analysis to Website Management, we empower your digital journey with expert guidance and free, powerful tools.

OpenAI’s Codex Introduces “Chronicle”: A Dual-Edged Sword for Developers

OpenAI, the creator of ChatGPT, is presently experimenting with a feature dubbed “Chronicle” within its AI coding platform, Codex. This function has elicited parallels to Microsoft’s contentious Windows Recall capability.

Chronicle is an opt-in research preview that allows Codex to take screenshots of users’ screens, utilizing this visual data to form contextual “memories.”

As a result, the AI agent can better comprehend ongoing tasks, thereby minimizing the necessity for users to rearticulate their workflows. Currently, this feature is exclusive to the Codex app on macOS, prompting concerns surrounding privacy and cybersecurity.

The Essence of Chronicle and Its Comparison with Windows Recall

As outlined in OpenAI’s documentation, accessible via The Register, Chronicle’s primary aim is to bolster Codex’s contextual awareness by tracking users’ activities.

The document specifies, “Chronicle enhances Codex memories with context derived from your screen. When you engage Codex, these memories facilitate its understanding of your work without necessitating repeated context restatement.”

Chronicle operates by periodically snapping screenshots and deploying optical character recognition (OCR) alongside other tools to extract text and contextual information. This data is subsequently transformed into text-based memory files for Codex to utilize in upcoming sessions.

The feature draws similarities to Microsoft’s Windows Recall, introduced in 2024, which autonomously captures desktop images at regular intervals, enhancing the AI Copilot’s utility.

Privacy advocates have expressed trepidation regarding this capability, cautioning that such screenshots could inadvertently store sensitive data.

Security analyst Michael Taggart underscored the parallels between the systems, remarking, “Oh my god, OpenAI reinvented Recall for macOS.”

Nevertheless, it is noteworthy that, in contrast to Recall, Chronicle remains an optional feature available solely for macOS users.

OpenAI disclosed that the screenshots are temporarily stored onsite for a maximum of six hours. Selected images are transmitted to OpenAI servers for processing into text-based memories.

Importantly, these screenshots are not designed for permanent storage or for use in training models. However, the generated memory files will reside locally until users opt for their manual deletion, with these files saved in: $CODEX_HOME/memories_extensions/chronicle/.

Users should exercise caution regarding potential privacy issues, as OpenAI warns, “Both directories for your screen captures and memories may contain sensitive information. Ensure that you do not share this content and recognize that other applications on your device could also access these files.”

Moreover, OpenAI acknowledges that Chronicle may introduce new vulnerabilities, stating, “Before enabling, be aware that Chronicle uses rate limits swiftly, heightens the risk of prompt injection, and stores memories unencrypted on your device.”

This suggests that users might exhaust Codex limits more rapidly while possibly exposing themselves to prompt injection attacks, should harmful material be displayed on-screen and subsequently captured by the AI.

The feature necessitates manual activation through Codex settings, along with granting permissions for screen recording. It is presently offered as a research preview for eligible macOS users, with availability limited outside the EU, UK, or Switzerland.

A woman presents to colleagues in a modern office, pointing at a screen displaying a macOS webpage, with Apple devices on the table.

For developers, Chronicle could minimize repetitive queries by enabling Codex to autonomously discern coding errors, files, and workflows.

However, for users managing sensitive information, it is imperative to meticulously assess privacy ramifications prior to activation, especially as captured screens and stored memory files may encompass passwords, private communications, documents, or financial details.

Source link: Timesofindia.indiatimes.com.

Disclosure: This article is for general information only and is based on publicly available sources. We aim for accuracy but can't guarantee it. The views expressed are the author's and may not reflect those of the publication. Some content was created with help from AI and reviewed by a human for clarity and accuracy. We value transparency and encourage readers to verify important details. This article may include affiliate links. If you buy something through them, we may earn a small commission — at no extra cost to you. All information is carefully selected and reviewed to ensure it's helpful and trustworthy.

Reported By

Souvik Banerjee

I’m Souvik Banerjee from Kolkata, India. As a Marketing Manager at RS Web Solutions (RSWEBSOLS), I specialize in digital marketing, SEO, programming, web development, and eCommerce strategies. I also write tutorials and tech articles that help professionals better understand web technologies.
Share the Love
Related News Worth Reading