mirror of
https://github.com/katanemo/plano.git
synced 2026-05-09 07:42:43 +02:00
* Fix code scanning and dependabot security alerts Code scanning fixes (14 alerts): - Fix XSS in OG image route by validating request origin against allowlist - Fix incomplete URL sanitization in blog layout using exact hostname matching - Bind port-check socket to 127.0.0.1 instead of 0.0.0.0 - Add explicit permissions to 7 GitHub Actions workflows Dependabot fixes: - Update @isaacs/brace-expansion 5.0.0 -> 5.0.1 (CVE-2026-25547) - Update bytes 1.10.1 -> 1.11.1 (CVE-2026-25541) - Update time 0.3.41 -> 0.3.47 (CVE-2026-25727) - Update cryptography 45.0.7 -> 46.0.5 (CVE-2026-26007) - Update python-multipart 0.0.20 -> 0.0.22 (CVE-2026-24486) - Update urllib3 2.6.2 -> 2.6.3 in test lockfiles (CVE-2026-21441) - Update Werkzeug 3.1.4 -> 3.1.5 (CVE-2026-21860) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Address PR review feedback - Replace plano.katanemo.com with planoai.dev in allowed hosts - Add planoai.dev to OG route and blog layout allowlists - Revert socket bind to 0.0.0.0 (intentional for port-in-use check) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| crewai | ||
| langchain | ||
| config.yaml | ||
| docker-compose.yaml | ||
| Dockerfile | ||
| openai_protocol.py | ||
| pyproject.toml | ||
| README.md | ||
| traces.png | ||
| uv.lock | ||
Travel Agents in CrewAI and LangChain - with Plano
What you'll see: A travel assistant that seamlessly combines flight booking (CrewAI) and weather forecasts (LangChain) in a single conversation - with unified routing, orchestration, moderation, and observability across both frameworks.
The Problem
Building multi-agent systems today forces developers to:
- Pick one framework - can't mix CrewAI, LangChain, or custom agents easily
- Write plumbing code - authentication, request routing, error handling
- Rebuild for changes - want to swap frameworks? Start over
- Limited observability - no unified view across different agent frameworks
Plano's Solution
Plano acts as a framework-agnostic proxy and data plane that:
- Routes requests to the right agent(s), in the right order (CrewAI, LangChain, or custom)
- Normalizes requests/responses across frameworks automatically
- Provides unified authentication, tracing, and logs
- Lets you mix and match frameworks without coupling, so that you can continue to innovate easily
How To Run
Prerequisites
-
Install Plano CLI
uv tool install planoai -
Set Environment Variables
export OPENAI_API_KEY=your_key_here export AEROAPI_KEY=your_key_here # Get your free API key at https://flightaware.com/aeroapi/
Start the Demo
# From the demo directory
cd demos/use_cases/multi_agent_with_crewai_langchain
# Build and start all services
docker-compose up -d
This starts:
- Plano (ports 12000, 8001) - routing and orchestration
- CrewAI Flight Agent (port 10520) - flight search
- LangChain Weather Agent (port 10510) - weather forecasts
- AnythingLLM (port 3001) - chat interface
- Jaeger (port 16686) - distributed tracing
Try It Out
-
Open the Chat Interface
- Navigate to http://localhost:3001
- Create an account (stored locally)
-
Ask Multi-Agent Questions
"What's the weather in San Francisco and can you find flights from Seattle to San Francisco?"Plano automatically:
- Routes the weather part to the LangChain agent
- Routes the flight part to the CrewAI agent
- Combines responses seamlessly
-
View Distributed Traces
- Open http://localhost:16686 (Jaeger UI)
- See how requests flow through both agents
Architecture
┌──────────────┐
│ AnythingLLM │ (Chat Interface)
└──────┬───────┘
│
v
┌─────────────┐
│ Plano │ (Orchestration & DataPlane)
└──────┬──────┘
│
├──────────────┬──────────────┐
v v v
┌────────────┐ ┌────────────┐ ┌──────────┐
│ CrewAI │ │ LangChain │ │ Jaeger │
│ Flight │ │ Weather │ │ (Traces) │
│ Agent │ │ Agent │ └──────────┘
└────────────┘ └────────────┘
├──────────────├
v v
┌─────────────┐
│ Plano │ (Proxy LLM calls)
└──────┬──────┘
Travel Agents
Flight Agent
- Framework: CrewAI
- Capabilities: Flight search, itinerary planning
- Tools:
resolve_airport_code,search_flights - Data Source: FlightAware AeroAPI
Weather Agent
- Framework: LangChain
- Capabilities: Weather forecasts, conditions
- Tools:
get_weather_forecast - Data Source: Open-Meteo API
Cleanup
docker-compose down
Next Steps
- Add your own agent - any framework, just expose the OpenAI-compatible endpoint
- Custom routing - modify
config.yamlto change agent selection logic - Production deployment - see Plano docs for scaling guidance
