DEV Community

Cover image for APX 1.36.0 — A Local Runtime for AI Agents, Built on APC

APX 1.36.0 — A Local Runtime for AI Agents, Built on APC

APX 1.36.0 — A Local Runtime for AI Agents, Built on APC

APX just shipped 1.36.0. If you have not run into it yet: APX is the reference runtime for the APC protocol — a local daemon, a CLI, and a web admin that let you run AI agents against one portable project context, no matter which coding tool you reach for that day.

This is a quick map of what APX is at 1.36.0 and where the recent releases landed.

The one idea

Project context should not be re-explained to every tool. You write it once, commit it to the repo, and any runtime reads the same thing.

APX is opinionated about that split:

  • Committed to the repo (.apc/) — agent definitions, project metadata, MCP hints, skills, and curated memory.
  • Local to the machine (~/.apx/) — sessions, conversations, message logs, and caches. Never committed.

The filesystem is the source of truth. No vendor database, no hidden state, no lock-in.

What you actually run

npm install -g apx
apx setup        # provider -> model -> channels -> daemon
apx init         # register any folder that has an AGENTS.md
Enter fullscreen mode Exit fullscreen mode

From there:

  • apx run sofia --runtime claude-code "Review the open PRs" — hand the task to a full external runtime (Claude Code, Codex, OpenCode, Aider, Cursor Agent). If one is not installed, APX falls back to another.
  • apx exec sofia "What is my role here?" — a quick one-shot LLM call through Anthropic, OpenAI, Gemini, or a local Ollama model.
  • apx messages tail — watch every channel as it happens.

Same context, same memory, whichever runtime or engine you pick.

Three surfaces, one daemon

  • CLI — run agents, read memory, tail messages, manage sessions.
  • Web admin — the same runtime in your browser at localhost:7430. Browse projects, agents, sessions, MCPs, engines, and channels. It talks only to the local daemon.
  • Telegram — operate your project agents from your phone. Identity roles gate who can do what, and every message is logged per channel for a full audit trail.

What the recent releases added

The last few cuts have been about making that runtime nicer to live in day to day:

  • 1.34 — Variables. Per-project and global variable management, so config stops being copy-paste.
  • 1.35 — Skill Inspector. An opt-in, per-turn middleware that pulls the right skill into a turn instead of loading everything up front.
  • 1.36 — Conversations with channels + summaries. Conversation management now understands channels and can summarize threads, which keeps long-running agent chats readable.

None of it changes the contract: context stays in the repo, runtime state stays local.

Why bother

The honest pitch is boring on purpose. APX does not try to be a new IDE or a new model. It is the plumbing that makes one project context usable across the tools you already use — with secrets and machine state kept in runtime storage where they belong.

If you already have an AGENTS.md, you are most of the way there.

npm install -g apx
Enter fullscreen mode Exit fullscreen mode

Top comments (0)