OpenAI has introduced a feature called Computer History that converts a user's clicks and keystrokes into a searchable timeline stored inside ChatGPT's memory system. Instead of only recalling what you typed into a chat window, the assistant can now draw on a record of what you actually did on your screen — which pages you opened, which buttons you pressed, and in what order.
According to The Decoder, the feature organizes this activity as a chronological log that ChatGPT can query later, rather than treating it as a disposable stream of input events. That distinction matters: a search bar over your own digital history is a different product than a chatbot that simply "remembers what you told it."
It is also a notable expansion of what "memory" means for a consumer AI product. Most chatbot memory to date has been built from explicit statements — facts a user typed in, preferences they confirmed, summaries the model wrote. Computer History instead treats passive interaction data as a legitimate memory source, on the same footing as a written note.
From conversation memory to activity memory
ChatGPT's existing memory features already let the model retain facts across sessions — a user's job, their writing style, a recurring project. Those memories are curated: the model decides what is worth keeping, and the user can review or delete entries. Computer History works differently. It captures raw behavioral signals — clicks, keystrokes, navigation — and turns them into an indexed timeline rather than a handful of remembered facts.
That shift moves ChatGPT's memory closer to how a browser history or an activity log works, except searchable through natural language instead of a URL bar. In practice, that means a user could plausibly ask the chatbot what they were working on last Tuesday afternoon and get an answer built from actual on-screen activity, not from something they explicitly told it to remember.
What a searchable activity timeline actually requires
Turning raw clicks and keystrokes into something a chatbot can usefully recall is a data-engineering problem before it is a conversational one. Three pieces have to work together for a feature like this to be useful rather than noisy:
- Capturing interaction events (clicks, focus changes, keystrokes) as structured signals, not just screenshots or raw text dumps
- Indexing that stream chronologically so it can be filtered by time, app, or task
- Making it queryable in natural language, so "what was I doing yesterday" returns something coherent instead of a raw event list
None of that is exotic — it is closer to building a personal search engine than to training a new model. But it does require OpenAI to hold onto a much denser, more sensitive stream of user data than a chat transcript ever produced.
Why builders should pay attention
For teams building their own chatbots or AI assistants, Computer History is a useful reference pattern rather than a feature to copy wholesale. The relevant idea is treating behavioral telemetry — not just typed text — as a first-class memory input:
- A support bot that can see which screen a user was stuck on before they asked a question needs far less back-and-forth to diagnose the problem
- An in-app assistant that indexes user actions chronologically can answer "what changed since my last visit" without the user reconstructing it themselves
- Search over activity, not just over conversation history, is the difference between a chatbot that "remembers" and one that merely stores transcripts
The catch is that few teams have OpenAI's infrastructure or trust position for this. Logging clicks and keystrokes is a meaningfully bigger privacy commitment than logging chat messages, and it needs its own consent flow, retention limits, and a visible way for users to inspect or delete what has been captured — not an afterthought bolted onto an existing memory setting.
AiiN's takeaway
The practical value here is real: a chatbot that can reconstruct context from what a user actually did, not only from what they bothered to type, is a genuinely more useful assistant for recurring, multi-session work. For developers building conversational products, the takeaway isn't "add click tracking" — it's that memory built from behavior is a stronger signal than memory built from self-reported facts, and it's worth designing for from the start rather than retrofitting later. Whether users are comfortable with that level of tracking by default is a separate question, and one OpenAI will have to keep answering as it expands what "memory" means for ChatGPT.