agents-cli-langchain
Use when working in this project — adding tools, editing the agent, running, evaluating, serving or deploying it — or when guidance mentions ADK, LlmAgent, google.adk, adk web, or an ADK runner. This project is LangChain/LangGraph scaffolded by agents-cli, so ADK-specific instructions do not apply.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-05
- Stars
- ★ 6.3k
- Forks
- 733
01 前言 Front Matter
- name
- agents-cli-langchain
- description
- Use when working in this project — adding tools, editing the agent, running, evaluating, serving or deploying it — or when guidance mentions ADK, LlmAgent, google.adk, adk web, or an ADK runner. This project is LangChain/LangGraph scaffolded by agents-cli, so ADK-specific instructions do not apply.
02 资源文件 2
- 参考文档references/langchain.md5.9 KB
- 参考文档references/samples.md3.5 KB
03 SKILL.md 正文
LangChain project (agents-cli)
The agent is a compiled LangGraph graph exported as root_agent from
app/agent.py. There is no google.adk dependency and no ADK runner. Other
google-agents-cli-* skills assume ADK; where they describe the agent itself,
this skill wins.
Experimental, and Agent Runtime is degraded. Deploy to cloud_run or gke. On
agent_runtime the app serves, but publish gemini is refused, the Console
playground cannot invoke it, and Console sessions/traces stay empty: all three want the
ADK reasoning_engine routes this project does not serve. Say so before recommending it.
What ADK guidance maps to here
| ADK guidance | This project |
|---|---|
LlmAgent, Agent, google.adk.tools |
langchain.agents.create_agent, plain Python functions as tools, or any compiled StateGraph |
adk web, adk run |
agents-cli playground (runs langgraph dev) |
ADK runner behind agents-cli run |
agents-cli run invokes the graph in-process |
agents-cli eval dataset synthesize, eval optimize |
Unavailable: both drive the agent through ADK. The command says so and exits |
Add an LlmAgent in app/agent.py |
Change the graph in app/agent.py; keep the name root_agent |
The contract
Keep these two, whatever you build inside them:
app/agent.pyexportsroot_agent, a compiled graph withmessagesstate. Callers only useroot_agent.invoke({"messages": [...]})androot_agent.astream(stream_mode="messages").app/fast_api_app.pyexposesapp. Every deployment target runsuvicorn app.fast_api_app:app.
Adding a tool means writing a typed function with a docstring and passing it in
tools=[...]. Switching frameworks (LangGraph StateGraph,
deepagents.create_deep_agent) means rewriting app/agent.py only. Pre-1.0
LangChain (LCEL chains, AgentExecutor) is not supported: not compiled graphs.
Commands
agents-cli install # uv sync
agents-cli playground # langgraph dev, port 8080
agents-cli run "hello" # invoke the graph in-process
agents-cli eval generate --dataset tests/eval/datasets/basic-dataset.json -o tests/eval/output/
agents-cli eval grade --traces tests/eval/output/<dataset>.json --config tests/eval/eval_config.yaml
agents-cli deploy # unchanged
agents-cli scaffold enhance -d cloud_run --cicd-runner github_actions # add infra later
playground, run and eval generate are overridden by
agents-cli-extension.yaml at the project root. Prefix any command with
AGENTS_CLI_DISABLE_OVERRIDES=1 to reach the built-in instead.
Serving
A2A only: JSON-RPC at POST /a2a/app, card at
/a2a/app/.well-known/agent-card.json, health at /health. Token streaming
comes from astream(stream_mode="messages").
Common mistakes
- Renaming
root_agentorapp, which breaksrun, eval and deploy. - Reaching for
eval dataset synthesizeoreval optimize: they need ADK. Write cases intotests/eval/datasets/and useeval generate+eval grade. - Expecting
/run_sseor ADK session routes; this server serves A2A. - Running
agents-cli run --url ...against a deployed agent withoutAGENTS_CLI_DISABLE_OVERRIDES=1, which invokes the local graph instead. runandeval generatecall Gemini on Gemini platform with ADC, so they needGOOGLE_CLOUD_PROJECTand credentials, orGOOGLE_API_KEY/GEMINI_API_KEYin.env.
References
references/langchain.md— framework contract and per-command detail.references/samples.md— agents worth copying from, by shape.
04 同仓库更多 Skills
google-agents-cli-workflow
This skill should be used when the user wants to "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs the ADK (Agent Development Kit) development lifecycle and coding guidelines. Entrypoint for building ADK agents. Always active — provides the full workflow (scaffold, build, evaluate, deploy, publish, observe), code preservation rules, model selection guidance, and troubleshooting steps for ADK or any agent development.
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers `agents-cli scaffold create`, `scaffold enhance`, and `scaffold upgrade` commands, template options, deployment targets, and the prototype-first workflow. Do NOT use for writing agent code (ADK projects: use google-agents-cli-adk-code) or deployment operations (use google-agents-cli-deploy).
google-agents-cli-publish
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-observability
This skill should be used when the user wants to "set up tracing", "monitor my agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring deployed agents, including ADK (Agent Development Kit) agents. Covers Cloud Trace, prompt-response logging, BigQuery Agent Analytics, third-party integrations (AgentOps, Phoenix, MLflow, etc.), and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment setup (use google-agents-cli-deploy) or API code patterns (use google-agents-cli-adk-code).
google-agents-cli-eval
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
google-agents-cli-deploy
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts, rollback, and production infrastructure. Applies to any framework agents-cli deploys (ADK, LangChain, ...). Part of the agents-cli skills suite. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), evaluation (use google-agents-cli-eval), or project scaffolding (use google-agents-cli-scaffold).