𝗧𝗵𝗲 𝗪𝗲𝗯 𝗔𝗱𝗺𝗶𝗻 𝗜𝘀 𝗔 𝗪𝗶𝗻𝗱𝗼𝘄, 𝗡𝗼𝘁 𝗔 𝗦𝗲𝗰𝗼𝗻𝗱 𝗦𝗼𝘂𝗿𝗰𝗲 𝗢𝗳 𝗧𝗿𝘂𝘁𝗵

The APX web admin panel is not the center of the system.

The design is strict. The daemon owns the state. The web UI is a local client. This distinction matters. It decides where truth lives and how much data can drift.

APC provides the portable context layer. APX provides the runtime and tooling layer. The web admin belongs to APX. It lets you inspect the runtime in a browser. It does not hold its own copy of project truth.

The architecture works like this:

  • The daemon runs a local HTTP server.
  • Every surface talks to the daemon over HTTP.
  • The web admin is served by the daemon.
  • The browser fetches a token from the daemon.

The browser is not a peer database. It is just one surface. When a web panel becomes a second source of truth, it fails.

Two copies of state lead to errors:

  • The CLI writes one thing while the UI shows another.
  • A browser session edits a config but the daemon uses old data.
  • A reload shows one project while another tab shows stale data.
  • A UI fix never reaches the actual runtime.

APX avoids this by keeping the browser thin. The UI asks the daemon. The daemon asks the core. The core reads or writes the real backing store. This chain is simple. Simple is good.

A good local panel does three things:

  • Show the live state.
  • Send a small action.
  • Revalidate after the action.

The panel lets you browse projects, agents, routines, sessions, MCPs, and settings. It is a view of the system, not a fork of the system.

Implementation details keep it local:

  • Dev mode uses Vite and proxies to the daemon.
  • Production serves the built app from the daemon.
  • Same origin keeps auth and routing simple.
  • The browser never needs direct repo write access.

The benefit is not visual polish. The benefit is that every action resolves through one backend.

If you edit a setting in the panel, the panel submits the change to the daemon. The daemon updates the project store. The next render reads the same source of truth the CLI reads. One system, many surfaces.

The UI can disappear without harming your project. You can close the tab or move machines. The state stays in the daemon and in the .apc/ folder.

The mental model is simple:

  • APC: what the project is.
  • APX: how the project runs.
  • Web admin: one window into that runtime.

Keep this boundary clean. The stack stays replaceable. The browser stays optional. The daemon stays authoritative. The project stays portable.

Source: https://dev.to/agentprojectcontext/the-web-admin-is-a-window-not-a-second-source-of-truth-2aip

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