| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
parent directory.. | ||||
A hands-on tour of VeADK, from the smallest possible agent to a multi-agent workflow. Each folder is self-contained: a single main.py, an .env.example, and a bilingual README (English + 中文).
中文版见 README.zh.md
| # | Example | Level | What you'll learn |
|---|---|---|---|
| 01 | Quickstart | Simple | Agent + Runner, one question |
| 02 | Custom tools | Simple | Let the agent call your Python functions |
| 03 | Short-term memory | Medium | Multi-turn conversation with a persistent session |
| 04 | Web search | Medium | Use a built-in Volcengine tool |
| 05 | Knowledgebase RAG | Medium | Ground answers in your own documents |
| 06 | Multi-agent workflow | Complex | Compose specialist agents with SequentialAgent |
| 07 | Structured output | Medium | Get schema-validated JSON with output_schema |
| 08 | Model config | Simple | Model fallbacks + model_extra_config per agent |
| 09 | Long-term memory | Complex | Recall facts across sessions (auto_save_session) |
| 10 | Agent routing | Complex | A coordinator that delegates to specialists dynamically |
| 11 | Tracing | Complex | Observe LLM/tool calls; dump or export spans |
| 13 | OpenViking | Complex | Use OpenViking for knowledge retrieval and long-term memory |
There are also frontend-focused demos that run with veadk frontend --agents-dir examples:
For a deployable full app (web UI + agent API in one container, shipped to Volcengine AgentKit via veadk agentkit), see basic-app/.
The examples are grouped by concept: 01–02 basics, 03 & 09 memory, 04–05 tools & knowledge, 06 & 10 multi-agent, 07–08 model behavior, 11 observability, and 13 OpenViking-backed knowledge and memory.
Four examples use Agent(runtime="codex"), which hands the inner loop to a sandboxed coding agent that can write a file, run it, read the traceback and fix it. Two of them show what the runtime is for; two show how to wire it up.
| Example | Kind | What you'll learn |
|---|---|---|
| Data analysis | What it's for | Codex writes an analysis script, hits a real error in dirty data, fixes it, re-runs, reports — the self-iteration loop |
| Ops assistant | What it's for | Correlate logs, metrics and deploys with throwaway scripts to find a root cause, inside a no-network sandbox |
| Skill + MCP | How to wire it | The paths a local skill and an MCP tool take under this runtime |
| Deploy to AgentKit | How to deploy | Ship a runtime="codex" agent to Volcengine AgentKit |
Reach for this runtime when the steps cannot be enumerated as tools ahead of time — ad-hoc analysis, log triage, data wrangling. Keep runtime="adk" for a fixed tool call and a formatted answer: it is faster, cheaper, and does not reject sub_agents / output_schema / planner / code_executor. See when to use the codex runtime.
Install VeADK (example 05 with the local backend needs the extensions extra):
pip install veadk-python
# for example 05's local RAG backend:
pip install "veadk-python[extensions]"In each example folder, copy the env template and add your keys:
cd 01_quickstart
cp .env.example .envVeADK auto-loads .env from the current working directory. You can also use a config.yaml instead — see the configuration docs.
Run:
python main.py| Back | FazBrowse Home | New Git URL |