Agent Slugs Are the Smallest Handoff Key Between APC and APX

Agent Slugs Are the Smallest Handoff Key Between APC and APX

A lot of APC and APX discussion happens at the level of folders, memory, or runtimes. But there is a smaller boundary that matters every day: the agent slug.

APC is the portable context layer. It keeps the project contract in the repository: AGENTS.md, .apc/project.json, .apc/agents/<slug>.md, skills, commands, and curated memory that is safe to share. APX is the daily-use runtime and tooling layer. It reads that contract, runs agents, stores local runtime state under ~/.apx/, and gives you CLI, daemon, and web admin workflows.

The slug is where those two layers meet.

In APC, the slug identifies the structured agent definition. In APX, the same slug becomes the routing key for commands like apx run <slug>, apx exec -a <slug>, apx memory <slug>, and apx session new <slug>. APX also uses it to place runtime files under per-agent paths such as ~/.apx/projects/<project-id>/agents/<slug>/sessions.