A single AuthMiddleware on the parent app now covers REST, /mcp, and WebSocket transports, so auth no longer drifts from one transport to the next. JWTMiddleware stays as a backward-compatible alias, so existing setups keep working while every entry point enforces the same rules.
View the AgentOS AuthMiddleware docs to learn more.