𝗧𝗵𝗲 𝗔𝗣𝗫 𝗖𝗟𝗜 𝗜𝘀 𝗔 𝗗𝗮𝗶𝗹𝘆 𝗟𝗼𝗼𝗽, 𝗡𝗼𝘁 𝗔 𝗗𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱

Stop treating the APX CLI as a giant control panel. Treat it as a small daily loop.

The design relies on a split between APC and APX. APC stays in your repo as a portable context layer. APX stays on your machine as a local runtime layer. If you try to make the CLI do everything, you lose the boundary between them.

Keep the CLI focused with this routine:

• Register the project once. • Check your state before you work. • Read durable memory before you ask for help. • Tail messages to see what actually happened.

A project becomes an APX project once it has AGENTS.md and .apc/project.json. You register it with these commands:

apx init apx project add .

The repo stays portable because the .apc/ tree holds the contract. It holds agents, skills, and config. APX keeps runtime state local on your machine. This means you can clone a repo to a new machine and recover the project shape without old runtime history.

When you start work, check the runtime first:

apx status

This shows daemon health and engine status. It helps you see if the local runtime is the problem instead of the repo. If a project moved, fix the registration:

apx project rebuild

APX memory is for durable facts. Use this to review it:

apx memory reviewer

To add a note, append one line:

apx memory reviewer --append "Prefers short PR summaries"

Do not feed models raw context. Use stable context through memory.

If memory tells you what should be true, messages tell you what happened. Use this to audit the system:

apx messages tail --channel runtime -n 20

Keep these three things separate:

  • memory.md: For durable facts.
  • messages: For recent activity.
  • sessions: For invocation history.

One file should not do three jobs. APC defines the project. APX defines what happened today.

Use this sequence to stay oriented:

apx project list apx memory reviewer apx messages tail -n 20

The CLI works best as a habit. Use the repo for portable context. Use the machine for runtime state. Use the CLI to check the boundary every day.

Source: https://dev.to/agentprojectcontext/the-apx-cli-is-a-daily-loop-not-a-dashboard-1o98

Optional learning community: https://t.me/GyaanSetuAi