Bring your own agent
Which frameworks work with Aarmos.
The CLI is not publicly distributed. Commands on this page are reference examples, not instructions you can run today.
Aarmos governs agents at the HTTP boundary, not at the SDK layer. A framework whose HTTP transport honors HTTPS_PROXYcan use the local proxy when correctly configured. Some clients need transport wiring as well as environment variables. Traffic that ignores the proxy is not governed.
| Framework | Lang | Version reference | Adapter | Documentation | Guide |
|---|---|---|---|---|---|
| LangChain.js Historical run receipts exist. Automated end-to-end execution of this example has not been established. | TypeScript / JavaScript | 0.3.x | HTTPS_PROXY (fetch) | Documented | Open → |
| CrewAI A separate, bounded CrewAI email-tool journey was qualified end to end. That does not qualify this proxy example or its optional lineage adapter. | Python | 0.70+ | HTTPS_PROXY (requests/httpx) | Documented | Open → |
| AutoGen (agentchat) Example documentation exists; actual governed AutoGen execution has not been established. | Python | 0.4+ | HTTPS_PROXY (httpx) | Documented | Open → |
| LangGraph A dedicated integration example and execution review remain pending. | Python / TS | — | planned via HTTPS_PROXY | Planned | — |
| LlamaIndex Retriever + LLM calls both honor proxy env; no runnable example yet. | Python / TS | — | planned via HTTPS_PROXY | Planned | — |
| OpenAI Swarm Experimental upstream; will publish an example when Swarm's API stabilizes. | Python | — | planned via HTTPS_PROXY | Planned | — |
What "Adapter" means
HTTPS_PROXY— only clients configured to honor proxy settings use this path. Node fetch / undici requires proxy wiring; see the LangChain guide. Enroll the shell witheval "$(aarmos env)".- No CA certificate is needed — the proxy tunnels HTTPS by hostname without decrypting it, so your certificate chain stays intact.
- Proxied calls are decided and recorded at hostname level. Connecting an MCP, OpenAPI or deep-link adapter does not by itself enforce rules on arguments; argument-level decisions apply only to tool calls routed through a reviewed tool binding on a supported enforcing path.
Missing your framework?
If its HTTP client honors proxy settings, it may use this path; confirm the actual execution and its limits. Reference checks include aarmos doctor, run eval "$(aarmos env)", then aarmos activity on the same machine to see each proxied call and its decision. Proxied calls do not appear in the web app's audit page. If you'd like it added to this matrix, share an integration example and its execution evidence through Support.