Genius! Use external Obsidian to permanently preserve Codex's important memories, so Codex won't forget key tasks! I have organized the content you need to send to your Codex into a super prompt: (Remember to specify the Vault path) Please help me configure Obsidian as Codex's cross-project long-term memory repository. My Obsidian Vault path is: <your Obsidian Vault path> Please create a folder in this vault called: Codex记忆 (Codex Memories) The target structure is as follows: Codex记忆/ ├── AGENTS.md ├── TODO.md ├── agent/ │ └── open-loops.md ├── 项目/ (Projects) ├── 人物/ (People) ├── 工作流/ (Workflows) ├── 决策/ (Decisions) └── 素材/ (Materials) Please complete the following: 1. Create the above directories and base Markdown files. 2. Write the Codex memory usage rules in `Codex记忆/AGENTS.md`. 3. Append an "Obsidian Codex Memory" rule to Codex's global AGENTS.md or custom instructions, so that Codex will know this directory is the long-term memory repository in the future. 4. Do not modify any content in the global AGENTS.md unrelated to Obsidian Codex memory. 5. Do not save any sensitive information such as Cookies, Tokens, API Keys, passwords, verification codes, ID numbers, bank cards, or private contact details. 6. Do not write full chat logs into the memory repository; only save information that is long-term valid and will be used repeatedly in the future. 7. After completion, verify that the files are successfully created, and tell me which files were created and which global configuration file was modified. Please write the following rules into `Codex记忆/AGENTS.md`: # Codex Memory Usage Rules This folder is Codex's cross-project long-term memory repository. It resides inside the Obsidian vault. All content should be readable, editable, searchable, and diff-able Markdown. ## When to Read Before starting more important or longer-duration tasks, quickly browse this file and check the relevant directories based on the task type: - Project-related: `项目/` (Projects) - People, collaborators, user personas: `人物/` (People) - Reusable processes, commands, checklists: `工作流/` (Workflows) - Important choices, trade-offs, reasons: `决策/` (Decisions) - Reusable materials, templates, expressions: `素材/` (Materials) - Cross-project unclosed items: `TODO.md` and `agent/open-loops.md` ## When to Write Only write information that is long-term valid and will be used repeatedly in the future. Prioritize saving the following: - User's long-term preferences, clear boundaries, repeatedly emphasized work styles - Project stable paths, key commands, environment differences, release processes - Verified fault causes, fixes, troubleshooting sequences - Important decisions and their reasons - Cross-project to-dos, pending issues - Reusable article structures, script flows, research templates, prompts ## Do Not Write - Do not save full chat logs, running logs, temporary emotions, one-time intermediate processes - Do not save Cookies, Tokens, API Keys, passwords, verification codes, ID numbers, bank cards, private contact details - Do not copy third-party platform configurations, account credentials, or sensitive values from logs into here - Do not write low-value summaries just to "look like you have memory" ## How to Write - Prefer updating existing notes; create new ones only when no suitable note exists - Write only small, checkable Markdown sections each time - Use clear titles, dates, source tasks, and scope of applicability - Separate facts from inferences; avoid solidifying guesses as rules - If you find old memory is outdated, do not delete it directly; first mark it as "outdated" and explain why ## Closing Rules Before finishing an important task, perform a memory closeout: - Determine if there is any long-term valuable content that needs to be written - If so, update the corresponding file - Write unclosed items into `TODO.md` or `agent/open-loops.md` - In the final reply, briefly describe which memory files were changed Please append the following to Codex's global AGENTS.md or custom instructions: ## Obsidian Codex Memory Use this directory as the cross-project long-term memory repository: `<your Obsidian Vault path>/Codex记忆` Before starting more important or longer-duration tasks, quickly browse: `<your Obsidian Vault path>/Codex记忆/AGENTS.md` When you learn information that is long-term valid and will be used repeatedly in the future, update the relevant Markdown files in `<your Obsidian Vault path>/Codex记忆`. Focus on saving: project stable paths, key commands, user long-term preferences, clear boundaries, verified troubleshooting conclusions, important decisions, reusable workflows, cross-project unclosed items. Do not save full chat logs, do not write running logs, do not treat temporary processes as memories. Do not save Cookies, Tokens, API Keys, passwords, verification codes, ID numbers, bank cards, private contact details, and do not copy third-party platform configurations or sensitive values from logs into Obsidian memories. Writing rules: prefer updating existing notes; create new ones only when no suitable note exists. Write only small, checkable Markdown sections each time. Separate facts from inferences. When discovering old memory is outdated, do not delete it directly; first mark it as "outdated" and explain why. Before finishing an important task, do a memory closeout: judge whether any long-term valuable content needs to be written; if so, update the corresponding file; write unclosed items into `<your Obsidian Vault path>/Codex记忆/TODO.md` or `<your Obsidian Vault path>/Codex记忆/agent/open-loops.md`; in the final reply, briefly describe which memory files were changed.

Codex记忆/
├── AGENTS.md
├── TODO.md
├── agent/
│   └── open-loops.md
├── 项目/
├── 人物/
├── 工作流/
├── 决策/
└── 素材/