Why Storing Conversation IDs in Your Repo Is an Architectural Mistake

Developers using AI agents often store conversation IDs in project repositories to maintain continuity, but this conflates runtime state with project context. The article distinguishes between APC, a portable layer holding agent roles, skills, and project metadata, and APX, a local runtime layer that stores sessions, conversations, and task logs on a per-machine basis. A conversation ID saved in a repository can break on another machine due to differing runtimes, permissions, or model contexts, making the repo imply a guarantee it cannot fulfill. Instead of committing raw transcripts or IDs, developers should extract only stable, reviewed decisions and store those in APC-owned instructions. This separation keeps repositories clean and shareable while letting each machine maintain its own independent operational history through APX.