design-agent README

项目的 README,来自 github.com/langchain-ai/design-agent。合并为一个 markdown 文件:README.md。

LangChainLangChain

Content Studio: one design brain for your whole company

License: Apache 2.0License: Apache 2.0 Python 3.11+Python 3.11+ Built on Deep AgentsBuilt on Deep Agents Deploy with Managed Deep AgentsDeploy with Managed Deep Agents

Distribute Content Studio to your team → · Try it locally, no keys needed · How we built it · Docs

English · 简体中文 · 日本語

Content Studio is the design agent LangChain runs, now open source. Add your brand and deploy it to your team's Slack with Managed Deep Agents. Anyone can ask it like they'd ask a designer, attach what they have, and get finished, on-brand files back, from a resized ad to a launch film.

Since August it has shipped over 3,000 assets for us, posts with its work drew about 4.5M views on X, and three in four requests come from outside marketing. How we built it goes deeper into each part.

See it work

We asked Content Studio for its own launch film. It went full Rocky.

https://github.com/user-attachments/assets/ee5b98e0-7ec6-4b24-ada6-1f27087947a3

From a 1-bit chick to champion in 47 seconds.

How it works

Content Studio is a Deep Agents agent deployed on Managed Deep Agents. Managed Deep Agents runs the infrastructure: Slack, sandboxes, memory, schedules and tracing. This repo is the design agent on top. The model makes the creative calls, and code renders, checks and delivers.

Content Studio on Managed Deep Agents: a Slack thread goes to the main agent, which reads skills and the wiki, keeps team and personal memory, uses managed tools and MCP servers with each person's own account, and works in a sandbox per thread with Chromium, ffmpeg, HyperFrames, motion-studio and async subagents in parallel, then posts the film back to the same thread

How we run it at LangChain. Your copy starts with the integrations you turn on (Integrations).

Watch it explain itself

We asked it to explain its own harness as a nature documentary, starring a pixel parrot. It walks through the computer, the tools and the context behind its work.

https://github.com/user-attachments/assets/65eac8e4-0fac-4a5a-9cca-02e26a0a8baa

Storyboarded, built and narrated by the agent, in one Slack thread.

The prompt that made this film

The agent made it from this ask and a few rounds of notes:

Make a short explainer of how you create videos in code, end to end, for our blog post on the media harness we built on Deep Agents. Narrate it like a David Attenborough nature documentary, starring the pixel parrot from our promo, with your subagents as its flock. Keep it technical enough for an engineer, in real terms: skills, wiki, tools, apps. Storyboard it before you build, and end on "Built on Managed Deep Agents".

Read the architecture, or start changing it: instructions.md · skills/ · Customization · Evals · Operations · Contributing.

Why it doesn't look like AI

The same prompt for a hiring chart to a local coding agent with a brand skill and to Content Studio: a broken logo lockup, a generic font, no axis and an off-brand bar on the left; a clean lockup, the brand typeface, an axis with gridlines and brand-blue bars on the right

The same prompt to a local coding agent with a brand skill, and to Content Studio.

The agent's computer: a Slack request for a launch film, project folders, a HyperFrames render in the terminal, the film preview, layers and references

Quickstart

Building it yourself Starting here
Months on a harness, a sandbox, skills and a Slack UX Fork it, add your brand, deploy with one command
Polished work that looks like a hundred others Work that follows your brand, checked on every render
Design requests wait in a queue Anyone asks in Slack: a graphic in minutes, a long deck overnight
Every team fixes the same mistakes Fix a skill once, and every asset after it follows

This repository is a Managed Deep Agents project, so it deploys to your LangSmith workspace as it is. You need a LangSmith account (Managed Deep Agents is in public beta on LangSmith Cloud) and a model key:

curl -fsSL https://raw.githubusercontent.com/langchain-ai/design-agent/main/install.sh | bash
cd design-agent
uv run design-agent config set LANGSMITH_API_KEY ANTHROPIC_API_KEY   # type each key; it stays hidden
uv run design-agent sandbox publish   # once per workspace, 10-15 min: the agent's computer
uv run mda deploy                     # the agent itself, and its Slack app

The installer gets uv if you don't have it, clones the repository and installs its dependencies; git clone and uv sync do the same.

The two last commands do different things. sandbox publish builds the Linux machine every thread works on, as a snapshot in your LangSmith workspace; nothing you can talk to exists yet. mda deploy deploys the agent, which clones that machine for each thread. Publish again only when sandbox/setup.sh changes.

On the LangSmith Gateway? Skip the provider key and run uv run design-agent config set DESIGN_AGENT_MODEL=langsmith:anthropic/claude-opus-5-5. The agent then uses LANGSMITH_GATEWAY_API_KEY, else LANGSMITH_API_KEY, and image generation goes through the gateway too when there is no OPENAI_API_KEY. For any other OpenAI-compatible endpoint, set DESIGN_AGENT_MODEL_BASE_URL and DESIGN_AGENT_MODEL_API_KEY_ENV (Models).

The first deploy sets up the agent's Slack app: mda deploy prints a Slack link, you approve the app for your workspace (an admin may need to), and press Enter. The agent then sends you a DM; reply to it, or /invite it to a channel and mention it. It's how we run ours at LangChain. Try changes on a separate copy with uv run mda deploy --name design-agent-test. In a workspace with agent mode, uv run mda deploy --agent-environment production (or staging, development) deploys into that environment of the agent, and each environment keeps its own traces: open the agent in LangSmith and pick the environment. uv run mda dev traces to its Local environment. Deploy with MDA covers keys, what ships and checking it works.

Or ask your coding agent. Paste this into Claude Code, Codex or Cursor, from any folder:

Deploy LangChain's open-source design agent to my Slack workspace with Managed Deep Agents.

1. Install it with `curl -fsSL https://raw.githubusercontent.com/langchain-ai/design-agent/main/install.sh | bash`, then work in the `design-agent` folder it creates.
2. Read `AGENTS.md` and follow the `design-agent-deploy` skill.
3. Tell me which keys you need. I'll type them myself with `uv run design-agent config set <KEY>` in my terminal; never ask me to paste a key in chat.
4. Run `uv run design-agent doctor` and fix what it flags. Its `mda-deploy` line lists what a deploy still needs.
5. Ask me before `uv run design-agent sandbox publish`, which bills. Then have me run the first deploy, `uv run mda deploy`, in my own terminal, since it sets up the Slack app.
6. When it's live, walk me through messaging the agent in Slack and sending a first request.

Once the repo is open, say what you want. AGENTS.md routes each request to a step-by-step skill:

Say It will
"Deploy it to our Slack." publish the sandbox, check what ships, and deploy after your yes
"Build our brand pack from our website and brand guide." draft the pack, validate it, and ask you to review it
"Teach it to make our weekly newsletter header." add a skill for it and try it on a real request
"Did that change make it better?" run the evals before and after, and show you the numbers

Try it locally

The demo runs the real agent, sandbox and checks with a scripted model and no API keys. It needs Docker, and leaves a launch card in three sizes and a 4-second teaser in workspace/out/demo/:

uv run design-agent sandbox build
uv run design-agent demo

With a model key in .env, ask for something real. Files land in workspace/out/<thread>/, and the last line tells you what the run cost:

uv run design-agent ask "A LinkedIn card announcing our design review service, 1200x627."

Make it yours

This repo has two kinds of skills. The ones in .agents/skills/ are for your coding agent, to set up, brand, deploy and change this repo. The ones in skills/ are what Content Studio reads while it works. Customization covers both.

Want Add Guide
Your brand workspace/brand/ (until then, a neutral sample brand), then redeploy brand-onboarding skill
Generated images OPENAI_API_KEY, GOOGLE_API_KEY, or the LangSmith Gateway Models
Voice, music, sound effects ELEVENLABS_API_KEY sound skill
The Paper canvas PAPER_MODE=local with Paper Desktop, or bridged when deployed Paper
Web search, your docs, other tools MCP servers in config/mcp.toml Customization

Once it's yours, ask it in Slack like you'd ask a designer:

Everything on this page uses LangChain's brand, because that's the one we run. Licensed fonts go in private-fonts/, which Git ignores.

Questions

What does it cost? The code is free (Apache 2.0). You pay your model provider: at LangChain the median request costs about 50 cents in model spend, and long films and decks cost more. Managed Deep Agents hosting is paid; it runs the agent, the sandboxes, the Slack app and the schedules that you'd otherwise build and operate yourself.

Will it use my brand? Yes. Add your brand pack and every file follows it. The brand-onboarding skill builds the pack with you from your brand guide, website, files or a Paper file.

Where do I start? With the graphic your team asks for every week. Let people brief the agent, review the work and ask for changes in Slack, then teach it the next thing.

Do I need Slack? No. Call the deployment's API, open it in LangSmith Studio, or use the terminal (design-agent ask). On Managed Deep Agents, long jobs that work in the background (films, parallel looks) report back in Slack; over the API, keep to requests that finish in one turn.

Is it safe with my keys? The sandbox never holds a credential and has no network by default. Host tools do the fetching, generating and delivering, and drop results in as files.

Which models? Claude Opus 5.5 by default. OpenAI and Google models, any OpenAI-compatible endpoint and the LangSmith Gateway work too. See Models.

Can I run it on my own servers? Yes. It's Apache 2.0, and Self-hosting runs the same agent with Docker, an HTTP API and your own Slack app.

Why two names? Content Studio is what we call the agent at LangChain, and the name its Slack app gets unless you set DESIGN_AGENT_SLACK_NAME. The repository, package and command are design-agent.

Does it replace a designer? No. It takes the repetitive requests, so designers spend their time on the work only they can do, and their judgment lives on in its skills and checks.

Build your own. Fork it, add your brand tokens, fonts and skills, and deploy it to your team's Slack. Quickstart. If it's useful, a star helps other teams find it.

Built with

Deep Agents    Managed Deep Agents    HyperFrames    Paper

Also: LangSmith · Chrome Headless Shell · FFmpeg · D2 · Apache ECharts · sharp. Logos belong to their owners. HyperFrames and Paper are partner projects we build on.


Apache 2.0 · Notices · Changelog · Security · Code of conduct

design-agent (langchain-ai/design-agent)

正在搜索数据库…

这是什么?Content Studio 是一个开源设计智能体,可以根据 Slack 聊天线程创建符合品牌风格的静态图、演示文稿、示意图、图表和动态图形,基于 LangChain 的 Deep Agents 构建。
这是一个我可以编写代码调用的框架,还是一个可以直接部署的现成智能体?它是一个现成的 Deep Agents 智能体,你可以 fork 后部署到 LangSmith 上的 Managed Deep Agents,而不是一个可以导入的库。模型负责创意决策,代码负责渲染、检查并交付文件。
我该如何让它运行起来?运行安装程序,它会在需要时获取 uv,克隆代码仓库并安装依赖(即 git clone 加上 uv sync),然后使用 uv run mda deploy 在你的 LangSmith 工作区中设置该智能体的 Slack 应用。
我需要 LangSmith 账户和模型密钥吗?需要。Managed Deep Agents 目前在 LangSmith Cloud 上处于公开测试版,因此你需要一个 LangSmith 账户,另外还需要一个模型密钥。默认使用 Claude Opus 5.5,但 OpenAI、Google 以及兼容 OpenAI 的接口也可以使用。
用它有什么需要注意的吗?代码本身免费,但 Managed Deep Agents 托管服务是收费的,它负责运行 Slack 应用、沙箱、记忆、定时任务和追踪。此外,一次中位数请求的模型开销仍约为 50 美分。
我能不用 LangSmith 账户或任何 API 密钥先试用一下吗?可以。本地演示使用脚本化的模型运行真实的智能体、沙箱和检查流程,无需任何 API 密钥,只需 Docker,并会在 workspace/out/demo/ 中生成一张发布卡片和一段简短预告。
我必须通过 Slack 和它交流吗?不必。除了 Slack,你还可以调用部署的 API、在 LangSmith Studio 中打开它,或使用终端命令 design-agent ask。像影片这类后台任务完成后,仍会回报到 Slack。
把我的工具和密钥接入它安全吗?安全。每个线程的沙箱都不保存任何凭据,默认也没有网络访问权限。所有抓取、生成和交付工作都由宿主工具完成,沙箱中只会以文件的形式回传结果。
代码真的免费吗,还是最终仍需付费?代码采用 Apache 2.0 许可证,免费使用。你需要向模型提供商付费(以 LangChain 的数据计,每次中位数请求约 50 美分);如果不自行托管,还可以选择付费使用 Managed Deep Agents 托管服务。
什么是 Paper?Paper 是 Content Studio 中的一块共享画布,你可以与智能体一同直接编辑分镜或版式。
什么是 HyperFrames?HyperFrames 是智能体制作影片所用的视频工具。它把影片视为时间线上的网页,因此编辑就只是修改代码和重新渲染。
它可以使用哪些 AI 模型?默认使用 Claude Opus 5.5,同时也支持 OpenAI 和 Google 模型、任何兼容 OpenAI 的接口,以及 LangSmith Gateway。
它会随着时间变得更好吗?每次任务结束后,learnfromjob 步骤会为所用的技能记录哪些做法有效。之后的任务会读取并为这些笔记打分,经不起检验的会被删除。
大小
52.8 MB
星标
631
更新
提交Nov 17
时长
1个月
提交 · 90 天