Skip to content

AGENTS.override.md

Latest commit

 

History

History
60 lines (54 loc) · 3.18 KB

AGENTS.override.md

File metadata and controls

60 lines (54 loc) · 3.18 KB
Raw

Local Project Memory routing

This file contains machine-local routing guidance. Keep it untracked through the target repository's .git/info/exclude; do not copy these mappings into a portable AGENTS.md. Replace the neutral example paths and keys with the exact locally enrolled values. Do not store credentials in this file.

Warning: in the same directory this file replaces AGENTS.md; Codex does not merge the two. Copy all required same-directory instructions into this override before using it. Installing Project Memory does not create or modify this file automatically.

Project routing

  • Shared/meta-project memory: ExampleSuite.
  • Files under main/ use project ExampleSuite/main.
  • Files under c-port/ use project ExampleSuite/c-port.
  • Files under rust-port/ use project ExampleSuite/rust-port.
  • Files and procedures shared by the whole workspace use project ExampleSuite; add an explicit child mapping for any other repository that needs separate memory.
  • If several keys intentionally share the same repository root, route by task scope as well as path. For example, core-library work may use ExampleSuite/core while GUI work uses ExampleSuite/gui; do not use the root-only selector to distinguish them.
  • At task start, determine the active project from the task and target paths.
  • Search the active child project first, then search its declared parent shown by project_memory_status for shared procedures, test equipment, and infrastructure.
  • Write component-specific memory to the active child. Write genuinely shared memory explicitly to the parent.
  • Do not search sibling projects unless the task spans them. If routing is ambiguous, ask before writing memory.

Memory workflow

  • At the start of troubleshooting or repeated operational work, call project_memory_status with the mapped project key, then search for the task, error signature, command, device, or log purpose.
  • After evaluating a retrieved record, call project_memory_mark_used with reused, helpful, not_applicable, or stale; a search hit alone does not mean the memory was used.
  • Call project_memory_note_repetition when substantially the same problem or action recurs while an effective final variant is still being sought.
  • Finalize a candidate only after at least two recorded occurrences and successful real verification. Save the exact final steps, context, outcome, verification, constraints, and tags.
  • Do not copy raw logs into memory. Store stable log locations with project_memory_record_log_location.
  • Store credentials only for assets explicitly classified as test-only, through project_memory_store_test_asset with test_only = true and secret values in secret_fields.
  • Never reproduce retrieved credentials in chat, source files, Git, patches, logs, delegated prompts, or unrelated tool calls. Do not store production, personal, or ambiguously classified credentials.
  • If Project Memory is unavailable, say so rather than claiming it was searched or updated.
  • Use project_memory_stats when the user asks for local usage or sanitized failure statistics. Treat reported server runs as approximate, not exact Codex session counts.