Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Deploy deep agents to LangSmith

未关闭
  • 哪里不对？
#75 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
fastapi, next.js, python, typescript
领域
backend, cloud, devops, frontend, observability

调研方向

Start by reading apps/agent/main.py, apps/agent/langgraph.json, and pyproject.toml, then review the LangSmith deployment documentation. Trace how the frontend CopilotKit API route reaches the current FastAPI/Uvicorn service. Done means the agent deploys successfully, skills and dependencies work, frontend requests reach the cloud URL, traces appear in LangSmith, and state synchronization is verified.

由索引模型根据 Issue 内容生成。

描述

Overview

Deploy the LangGraph deep agent (apps/agent) to LangSmith's managed cloud platform (formerly LangGraph Platform) for production hosting, observability, and tracing.

Background

The agent already uses the deepagents SDK (create_deep_agent()) built on LangGraph, and has a langgraph.json config in place. LangSmith Cloud provides managed deployment with built-in tracing, streaming, and persistence — replacing the current self-hosted FastAPI/Uvicorn setup.

Current State

  • Agent framework: LangGraph 1.0.7 + DeepAgents via create_deep_agent()
  • Entry point: apps/agent/main.py → exports graph object
  • Config: apps/agent/langgraph.json already exists with graph sample_agent pointing to ./main.py:graph
  • Dependencies: managed via uv + pyproject.toml
  • Hosting: currently self-hosted via uvicorn on port 8123
  • Checkpointing: in-memory BoundedMemorySaver (200 threads, no persistence across restarts)

What Needs to Happen

1. LangSmith Account & Deployment Setup
  • Ensure LangSmith Plus plan (or higher) is active — required for cloud deployments
  • Connect the GitHub repo to LangSmith via Deployments → + New Deployment
2. Configuration Updates
  • Review langgraph.json — the env path currently points to ../../.env (relative to repo root), which may need adjustment for cloud deployment
  • Add LANGCHAIN_API_KEY, LANGCHAIN_TRACING_V2=true, and LANGCHAIN_PROJECT to environment config
  • Ensure OPENAI_API_KEY is set as a deployment secret in LangSmith
  • Verify deepagents and all dependencies resolve correctly in the cloud build environment
3. Compatibility Considerations
  • CopilotKitMiddleware: Verify it works within LangGraph Platform's execution model (not running inside FastAPI directly)
  • BoundedMemorySaver: Cloud deployments provide managed persistence (Postgres-backed checkpointer) — evaluate whether to replace the custom in-memory saver
  • Skills directory: Confirm skills/ markdown files are included in the deployment bundle (they're loaded via file path at runtime)
  • ag-ui-langgraph endpoint: Determine if the FastAPI wrapper (add_langgraph_fastapi_endpoint) is still needed or if LangSmith handles this natively
4. Frontend Integration
  • Update the frontend CopilotKit API route to point to the LangSmith deployment URL instead of localhost:8123
  • Add deployment URL as an environment variable for the Next.js app
  • Test bidirectional agent state sync (todos) through the cloud-hosted agent
5. Observability
  • Confirm traces appear in LangSmith for all agent runs
  • Set up a LangSmith project for organizing traces
  • Verify tool call traces (query_data, plan_visualization, manage_todos, etc.) are captured

Risks & Open Questions

  • Cold start latency: LangSmith cloud deployments may have cold starts — measure impact on UX
  • Cost: Plus plan is $39/seat/mo + usage-based billing for agent runs and uptime
  • Skills file loading: The agent loads skills from Path(__file__).parent / "skills" — need to verify this resolves correctly in the containerized cloud environment
  • Rate limiting: Current app has optional IP-based rate limiting in FastAPI middleware — this won't carry over to LangSmith; determine if platform-level rate limiting is sufficient

References

主要语言
TypeScript
星标
1.6k
派生
203
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

CopilotKit/OpenGenerativeUI 的其他 Issue

查看 CopilotKit/OpenGenerativeUI 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。