What problem does it solve? Turning a local Agno agent into a production service requires wiring up an API, a UI for testing, tracing for debugging, and a deployment path, which is error-prone when done ad hoc. ## Core Features & Use Cases - AgentOS API packaging: Wrap agents, teams, and workflows in a FastAPI app with AgentOS, served via uvicorn on port 7777. - Web UI and tracing: Connect os.agno.com to the local endpoint to chat, inspect sessions, and review step-by-step traces of tool calls and reasoning. - Evaluation workflow: Compare agent versions using the same inputs and review persisted sessions to measure quality and regressions. - AWS EC2 deployment: Follow a documented flow covering security groups, environment variables, systemd, Nginx with HTTPS, and pinned versions. - Use Case: You built a chat agent with Agno and want to expose it as an API, debug its traces in the Agno UI, then deploy it to a small EC2 instance behind HTTPS. ## Quick Start Serve my Agno agent with AgentOS, enable tracing, and walk me through deploying it to an EC2 instance.