mirror of
https://github.com/pchuan98/codex.git
synced 2026-07-01 00:31:56 +08:00
jif-oai
de513a83f3
## Why The memories extension now owns the read-path developer instructions it injects at thread start. Keeping that prompt builder and template in `codex-memories-read` left the extension depending on a helper crate for extension-specific prompt assembly, and kept async template/truncation dependencies in the read crate after the remaining read surface no longer needed them. ## What changed - Moved `prompts.rs`, its tests, and `templates/memories/read_path.md` from `memories/read` into `ext/memories`. - Wired `MemoryExtension` to call the local prompt builder and added the moved templates to `ext/memories/BUILD.bazel` compile data. - Removed the now-unused prompt export and prompt-related dependencies from `codex-memories-read`. ## Testing - Not run locally.
16 lines
449 B
Rust
16 lines
449 B
Rust
//! Read-path helpers for Codex memories.
|
|
//!
|
|
//! This crate owns memory injection, memory citation parsing, and telemetry
|
|
//! classification for read access to the memory folder. It intentionally does
|
|
//! not depend on the memory write pipeline.
|
|
|
|
pub mod citations;
|
|
mod metrics;
|
|
pub mod usage;
|
|
|
|
use codex_utils_absolute_path::AbsolutePathBuf;
|
|
|
|
pub fn memory_root(codex_home: &AbsolutePathBuf) -> AbsolutePathBuf {
|
|
codex_home.join("memories")
|
|
}
|