← 全部工具

@miller-tech/uap

热度 65 更新于 开发与构建

Autonomous AI agent memory system with CLAUDE.md protocol enforcement

npmauto-collected

安装

npm
npm install -g @miller-tech/uap

通过 npm 安装。

<div align="center"

Universal Agent Protocol (UAP)

The discipline layer that turns a talented-but-unreliable AI coding agent into a dependable member of your software delivery line.

v1.163 · 220+ modules · 200+ test suites · 9 agent harnesses

Quickstart · Why UAP? · The delivery pipeline · uap deliver · Docs

</div

---

Why UAP?

Shipping software with an AI agent is a lot like running a small factory floor. Intent comes in one end; working, verified, merged code should come out the other. In between are stations — understand the job, set up a bench, build it, check it actually works, ship it — and a jam at any one of them quietly ruins everything downstream.

Coding agents are capable but undisciplined line workers. They forget yesterday's shift, grab the wrong tool, build something that looks right, stamp it "done" without plugging it in, and trip over the other workers on the floor. That's not a problem you fix by swapping in a smarter model — it's a process problem. UAP is the process: it sits underneath your agent harness (Claude Code, Factory, Cursor, OpenCode, and more) and puts a station at every point where the line usually breaks — no model change required.

| Where the line jams | What UAP puts there | What you get | |---|---|---| | Agent starts every session amnesiac | 4-tier memory with semantic recall + write-gates | It remembers your codebase and past decisions | | Tool output floods the context window | MCP Router — tool-hiding + output compression | Up to ~98% smaller on big tool calls | | "Looks right" but doesn't run | uap deliver — a loop against your real gates | Code that compiles, not a mock-up of it | | Agent grades its own homework | Execution/runtime verify + a separate acceptance judge | "Done" means verified done | | Two agents clobber each other | Worktree isolation + live file coordination | Conflict-free parallel work | | "Guidelines" get ignored | Policy gates as executable hooks, not prose | Violations are blocked, not politely suggested | | Same mistake, every session | Memory promotion + pattern learning | The floor gets better every run |

→ Take the full station-by-station tour: The UAP Delivery Pipeline.

---

Quickstart

# Install globally
npm install -g @miller-tech/uap

# One friendly, arrow-key guided setup in your project
cd your-project
uap setup

uap setup walks you through the whole line — memory, patterns, policy gates, model routing, multi-agent coordination, and the verification gates — and wires it into every agent session. Take the defaults and you're one Enter away from a disciplined agent.

uap memory query "how did we handle auth last time?"   # semantic recall
uap deliver "add rate limiting to the API"             # drive a model to verified completion
uap dashboard overview                                  # live task / agent / memory state

---