Promote Computer History into durable knowledge
Pattern: Promote Computer History into durable knowledge
Computer History and Oddlynew solve different parts of the continuity problem. Computer History helps ChatGPT and Codex understand recent activity across apps and websites. Oddlynew preserves the selected decisions, evidence, methods, and artifacts that should remain usable across chats, agents, collaborators, and time.
The useful pattern is not to copy all activity into Oddlynew. It is to let recent history reveal what may matter, then deliberately promote the durable result into the organization whose audience and trust boundary fit it.
Source and availability: OpenAI's Computer History documentation, reviewed 2026-08-14. Computer History is currently a macOS desktop feature for eligible ChatGPT Pro, Business, and Enterprise users. It is off by default, requires Memories, and is not currently available in the European Economic Area, Switzerland, or the United Kingdom.
The division of labor
Computer History is personal recent-work context. It records permitted interaction events such as app switches, clicks, typing, and keyboard shortcuts, then periodically turns them into timeline summaries and local Markdown memory files. It can help a person find recent work, resume after a break, notice patterns, or identify a repeatable workflow.
Oddlynew is deliberate durable knowledge. An authorized agent writes selected knowledge into documents inside an organization. Those documents can carry references, provenance, versions, comments, and an audience boundary. They become a starting point for later people and compatible agents.
The agent performs the promotion. In a session that can access Computer History and is also authorized to use Oddlynew, the person can ask the agent to inspect recent work, identify what deserves to survive, retrieve the underlying source when available, and draft or update the appropriate Oddlynew document. This is a composable workflow, not an automatic Computer History integration shipped by Oddlynew.
This follows the existing product boundary in How to Start: Oddlynew does not automatically capture everything said or done. Work becomes durable when an authorized person or agent deliberately writes it.
A practical promotion loop
Ask: What did I work on recently that should not disappear into app history?
Let the agent group candidates into decisions, research, reusable methods, unresolved questions, useful artifacts, and temporary noise.
For a promising candidate, retrieve the original file, conversation, page, or other evidence when the agent has authorized access. Computer History is a locator and context signal, not necessarily the authoritative source.
Choose the correct Oddlynew organization based on audience and trust boundary. Do not promote private personal context into a shared organization merely because it appeared in history.
Extend the adjacent canonical document when one exists. Create a new document only when the knowledge has a distinct durable purpose.
Preserve provenance, uncertainty, and open questions. Do not turn an observed action into a settled decision or an inference into a quote.
Review sensitive or consequential promotions before writing or sharing them.
Example prompts:
Review my recent Computer History. Which decisions or discoveries are not yet captured in Oddlynew?
Find repeated work from this week that could become an Oddlynew operating pattern or capability.
Look at what I was doing before my break, retrieve the relevant source, and update the existing project document rather than starting from scratch.
Where did I repeatedly reconstruct context that an Oddlynew document could preserve for the next agent?
Show me the proposed Oddlynew destination and summary before writing anything sensitive.
What is worth promoting
Good candidates include:
a decision and the reasoning that should guide later work;
research findings and their evidence;
a correction that should change future agent behavior;
a repeated workflow that could become an operating guide, skill, or capability;
project state that another person or agent must be able to continue;
an artifact whose meaning would otherwise be lost outside its original application;
a recurring context-reconstruction problem that durable knowledge could remove.
Usually do not promote:
every click, search, or raw timeline summary;
credentials, private messages, health or financial information without an explicit appropriate purpose;
third-party communications without considering consent and audience;
temporary thoughts that have not earned durable status;
copied source material when a reference and concise conclusion would be safer and more useful.
The objective is durable continuity, not indiscriminate memory. See Use Cases: Start with the Outcome.
Privacy and trust boundaries
OpenAI states that Computer History does not capture screenshots, audio, or private-mode browsing. Temporary interaction-event files remain on the Mac for up to 48 hours; generated local memory files remain until deleted. The memory files are plain-text Markdown and are not encrypted by Computer History.
OpenAI also warns that Computer History increases prompt-injection risk from content in apps and websites. It recommends excluding sensitive sources and turning the feature off during communications with other people unless they have given prior express consent.
These constraints make deliberate promotion essential. Treat Computer History as untrusted, personal source context. Before writing to Oddlynew, verify important claims against the underlying source, remove irrelevant sensitive detail, preserve provenance, and select the organization whose members should actually receive the knowledge.
Why this matters for Oddlynew
Computer History reduces the burden of remembering where work happened. Oddlynew removes the burden of rebuilding the useful knowledge after the activity is gone. Together they create a natural funnel:
activity history -> candidate insight -> verified source -> durable document -> reusable organizational context
This also clarifies Oddlynew's ecosystem position. Personal memory systems, model memories, browsing history, meeting transcripts, and application histories can all serve as sensors. Oddlynew does not need to replace them. It can be the destination where a person and their chosen agent preserve what should become durable, shared, and reusable.