Governed at the origin, across governed calls. One runtime you own.
Aarmos brokers the protocol your framework already emits.
This page covers which frameworks and protocols reach a supported origin. Release compatibility with your workspace is a separate question, answered by aarmos upgrade preflight.
You do not rewrite your agent, install an Aarmos-flavored fork of your framework, or import a framework-specific SDK. Aarmos sits below the framework, at the protocol layer, and enforces policy + writes a signed AVAR receipt on the way out.
Why protocol-first, not framework-first
- Zero-line enrolment. Point a framework at
eval "$(aarmos env)"and every proxied call runs under Aarmos policy. No import. No wrapper. - Runtime-invariant. The moat is the runtime, not the SDK. A per-framework SDK for every framework is a hedonic treadmill — the protocol set is finite.
- No hosted request path. The proxy binds 127.0.0.1 and forwards to the client's original destination. Tool traffic on this path does not pass through Aarmos servers.
Framework → protocol → on-ramp
| Framework | Emits | Aarmos on-ramp |
|---|---|---|
| LangChain / LangGraph | HTTP · OpenAI-compatible endpoint | aarmos proxy (zero code) · openapi adapter |
| AutoGen | HTTP · OpenAI-compatible endpoint · Docker exec | aarmos proxy (zero code) · openapi adapter |
| CrewAI | HTTP · OpenAI-compatible endpoint | aarmos proxy (zero code) · openapi adapter |
| OpenAI Swarm / Assistants | HTTP · OpenAI-compatible endpoint | aarmos proxy (zero code) |
| MCP client (any) | Model Context Protocol | mcp adapter |
| Custom scripts, cron, shell agents | HTTP · webhooks · URL schemes | aarmos proxy · deeplink adapter |
Aarmos ships no framework-specific package — dedicated SDKs for LangChain, AutoGen, CrewAI, or Swarm are explicitly banned as headline features. Zero lines beats three.
Zero-code on-ramp
# 1. Start the transparent local proxy
aarmos proxy
# 2. Point your framework at it — on any integrated framework
eval "$(aarmos env)" # authenticated HTTPS_PROXY + HTTP_PROXY
# 3. Run your agent unchanged
python my_langchain_agent.py
▸ tool: openapi://api.openai.com/v1/chat (adapter: proxy) ✓ scoped
▸ tool: openapi://api.slack.com/post (adapter: proxy) ✓ scoped, confirm
✓ AVAR receipt: .aarmos/avar/9a4b…c1.avar
verify: in-browser verifier or @avar-standard/verifyThe proxy forwards to the ORIGINAL destination. It never routes through an Aarmos-hosted service, and it never phones home on the request path.
The CLI is distributed to authorized workspaces only and is not publicly issued; the commands above are reference examples.