← all repositories
agentscope-ai/agentscope

An agent framework that gets out of the model's way

AgentScope 2.0 bets that modern LLMs need less hand-holding, not more orchestration.

26.4k stars Python AgentsLanguage Models
agentscope
Velocity · 7d
+30
★ / day
Trend
steady
star history

What it does AgentScope is a Python framework for building and deploying LLM agents. It wraps models, tools, memory, and multi-agent workflows into an async-first API, then ships with a FastAPI service and a web UI so you can run it locally or on Kubernetes. It also includes built-in fine-tuning support and OpenTelemetry instrumentation.

The interesting bit The authors explicitly reject rigid prompt engineering and “opinionated orchestrations.” Their pitch: newer models reason and use tools well enough that your framework should expose those abilities, not smother them. It’s a bet against over-engineering that will either age very well or very badly.

Key highlights

  • Requires Python 3.11+; installable via PyPI or uv
  • Built-in ReAct agent, tool toolkit (Bash, Grep, file I/O, etc.), memory, planning, voice, and evaluation
  • Supports MCP and A2A protocols; message hub for multi-agent workflows
  • Ships with a FastAPI-based multi-tenancy service and a pre-built web UI in examples/web_ui
  • Fine-tuning and OTel observability included without extra glue

Caveats

  • The README’s quickstart hardcodes DashScope (Alibaba’s Qwen API); other model backends exist but aren’t shown front-and-center
  • The “5 minutes” claim assumes you’re already set up with the right API keys and Python environment
  • AgentScope 2.0 is fresh enough that real-world battle scars aren’t visible in the docs yet

Verdict Worth a look if you’re building agent services that need to graduate from notebook to production without rewriting everything. Skip it if you want a framework that enforces strict control flows or if you live entirely outside the Python/K8s ecosystem.

heatdrop uses Google Analytics to see which pages get read — nothing else. Your call. How we handle data.