APC and APX, two layers of a developer toolchain, use a stable 'agent slug' as the smallest handoff key between portable project contracts and local runtime state. The slug, defined in APC's structure…
A developer argues that agent memory should be split into two layers: APC for durable project facts and APX for runtime state. The APC/APX split prevents repositories from filling with private notes a…
A developer clarifies the distinction between APC (Agent Project Contract) and MCP (Model Context Protocol), explaining that APC defines the project contract while MCP defines the tool protocol. The d…
APX, the local runtime and tooling layer for the APC portable context layer, introduces `apx mcp check` to debug shadowed MCPs by showing source files, active entries after merge, and conflicts. The c…
APX CLI is designed as a small daily loop rather than a comprehensive dashboard, maintaining a clear boundary between portable context (APC) and local runtime (APX). The developer advocates for a focu…
APX, a daily runtime for the APC portable context layer, introduces project pinning for Telegram channels to eliminate context guessing. By pinning a channel to a specific project, APX automatically s…
A developer warns that MCP scopes in APC/APX are trust boundaries, not settings, and misusing them leads to conflicts and fragile onboarding. The three scopes—runtime, shared, and global—each serve di…