agno-local-dev-environment

Configure a docker-compose local environment simulating AWS, LLM providers, and observability for Agno agents.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/allankltsn/setup_kiro --skill agno-local-dev-environment-allankltsn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agno-local-dev-environment
Source: https://github.com/allankltsn/setup_kiro/tree/main/.kiro/skills/agno-local-dev-environment
Command: npx skills add https://github.com/allankltsn/setup_kiro --skill agno-local-dev-environment-allankltsn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developing an Agno agent against real AWS services, paid LLM providers, and production observability stacks is costly and slow. This Skill sets up a fully local docker-compose environment that emulates every third-party dependency so the agent code runs unchanged between local development and production. ## Core Features & Use Cases - LocalStack emulation: Simulates API Gateway, Lambda, DynamoDB, Secrets Manager, S3, and SSM with idempotent bootstrap scripts, letting you rehearse SAM deploys without an AWS account. - Ollama local LLM fallback: Runs a local model provider for offline, zero-cost inference alongside remote providers. - Pluggable observability backends: Compose profiles switch between SigNoz (default) and Grafana+Tempo+Loki+Prometheus, plus optional Langfuse for LLM tracing, all receiving OTLP telemetry from the agent. - AgentOS monitoring UI: Serves the agent through Agno AgentOS on port 7777 to inspect runs, sessions, tokens, and traces while developing. - Use Case: While building a support agent, run docker compose up -d, point .env.local at LocalStack and the local OTLP collector, then watch each agent run in AgentOS and traces in SigNoz before deploying to AWS Lambda. ## Quick Start Ask the AI to set up the local Agno development environment with docker-compose including LocalStack, Ollama, AgentOS, and a SigNoz observability backend for my agent project.

Frequently Asked Questions about agno-local-dev-environment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a local development environment for Agno agents?▼

Create a docker-compose.yml in the agent project with LocalStack, Ollama, AgentOS, and one observability backend, then run docker compose up -d. Point .env.local at the local endpoints so the agent code stays unchanged between local and production.

How to test AWS Lambda and DynamoDB locally without an AWS account?▼

Use LocalStack, which emulates API Gateway, Lambda, DynamoDB, Secrets Manager, S3, and SSM through a single endpoint on port 4566. Bootstrap scripts with awslocal create tables, secrets, and buckets idempotently, and samlocal deploy rehearses SAM deployments.

SigNoz vs Grafana stack for local OpenTelemetry observability?▼

SigNoz is an all-in-one OTLP backend handling traces, logs, and metrics in a single service, used as the default Compose profile. The Grafana profile runs Tempo, Loki, and Prometheus separately with Grafana for visualization, offering more modular control.

Can I use Ollama as a fallback LLM provider for Agno agents?▼

Yes, run Ollama in docker-compose on port 11434 and pull a model such as llama3.2. Set MODEL_PROVIDER_ORDER to include ollama after the remote provider, giving offline, zero-cost fallback inference.

Why should endpoints come from environment variables instead of code?▼

Environment-driven endpoints let the same agent code run against local docker-compose services or production AWS by only changing variables like AWS_ENDPOINT_URL and OTEL_EXPORTER_OTLP_ENDPOINT. This eliminates code divergence between environments.

What are the limitations of the AgentOS server in production?▼

AgentOS is a development and monitoring tool for inspecting runs, sessions, and traces locally on port 7777. Production deployment uses the same FastAPI app behind API Gateway and Lambda instead of AgentOS.