Bring your own agent
Which frameworks work with Aarmos.
Aarmos governs agents at the HTTP boundary, not at the SDK layer. Any framework whose transport honors HTTPS_PROXYworks with one env var — no wrapper, no monkey-patch, no code change.
Honesty rule: Verified means we have a runnable example in
examples/<name>/ that CI exercises. Anything else is Planned. No row is upgraded on vibes.| Framework | Lang | Tested | Adapter | Status | Guide |
|---|---|---|---|---|---|
| LangChain.js | TypeScript / JavaScript | 0.3.x | HTTPS_PROXY (fetch) | Verified | Open → |
| CrewAI | Python | 0.70+ | HTTPS_PROXY (requests/httpx) | Verified | Open → |
| AutoGen (agentchat) | Python | 0.4+ | HTTPS_PROXY (httpx) | Verified | Open → |
| LangGraph | Python / TS | — | planned via HTTPS_PROXY | Planned | — |
| LlamaIndex | Python / TS | — | planned via HTTPS_PROXY | Planned | — |
| OpenAI Swarm | Python | — | planned via HTTPS_PROXY | Planned | — |
What "Adapter" means
HTTPS_PROXY— Node fetch / undici / axios (with env), Pythonhttpx, Go stdlib. Zero code change; 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 yield hostname-level receipts. Add an
@aarmos/adapter-*package when you want prompt- and argument-level detail.
Missing your framework?
If it speaks HTTP and honors proxy env, it already works — run aarmos doctor, run eval "$(aarmos env)", and open /audit. If you'd like it added to this matrix, open a PR with an example under examples/<framework>/ that mirrors the shape of the three Verified rows above.