ReadMe

It doesn't make sense to ask your agent about your codebase if it cannot read the code; it needs context.

Similarly, an agent can't give you good responses if it doesn't know about you.

ReadMe turns your files into a "codebase," so that next time you ask something, it can look up the relevant context about you before answering.

It is super easy to set up!

Just run:

codex exec --dangerously-bypass-approvals-and-sandbox --ephemeral - < Init.md

Or paste Init.md into Codex CLI/App.

What will happen next is...

1. Agent scans local files:

Source traces:
    ├── ~/.codex/sessions/
    ├── ~/.claude/sessions/
    ├── ...
    ├── ~/Downloads/
    └── ~/Projects/

2. Builds ~/.codex/user_context/

~/.codex/user_context/
└── 2026_agentic_rag_memory_systems/
    ├── year.md
    └── 2026-Q2_prompt_programs_context_retrieval/
        ├── quarter.md
        └── 2026-04_bootstrap_and_consolidation/
            ├── month.md
            └── 2026-04-13_hierarchical_memory_rewrite.md

3. Installs a hint in ~/.codex/AGENTS.md:

<user_context>
Additional user-specific context may live in `~/.codex/user_context/`...
</user_context>

Example question

What have I been working on in the past 3 months?

4. Agent gathers context:

ls ~/.codex/user_context/2026_.../

Example answer

You have been converging on agentic infrastructure: memory systems, context retrieval, and public-facing artifacts.

If you want the memory to be up to date, you can enable automatic daily updates with:

REPO_DIR="$(pwd)" && codex exec --dangerously-bypass-approvals-and-sandbox --ephemeral "Install a daily scheduler for: cd \"$REPO_DIR\" && codex exec --dangerously-bypass-approvals-and-sandbox --ephemeral - < Update.md. Use cron by default; otherwise use the host scheduler. Do not create wrapper scripts. Verify codex is on PATH, Update.md exists, and the installed scheduler entry is readable. Do not run Update.md during validation."