agentleFS
bytedancebytedance/deer-flow/docker/AGENTS.md

deer-flow / docker

AGENTS.md85k starsChanged 5 months agoMITView on GitHub

Compose files, nginx configuration and the sandbox provisioner. The Helm chart in deploy/helm/ carries the same nginx routes. - Place the browser-stream WebSocket location before the generic threads location in the Docker, local and Helm nginx configs. nginx takes the first matching regex. - Publish a port with an explicit bind address. A bare "${PORT}:2026" binds 0.0.0.0. Both Compose files default the host to 127.0.0.1. Only the published nginx port is external. - The root PORT controls Docker ingress only.…

  • Reads credentials

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 19 mentionsApr 2026: 2 mentionsMay 2026: 6 mentionsJun 2026: 11 mentionsJul 2026: 3 mentionsAug 2026: 8 mentionsSep 2026: 9 mentionsOct 2026: 22 mentionsNov 2026: 13 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the bytedance/deer-flow repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about bytedance/deer-flow

The biggest 5 of 105 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 105

Talked about on GitHub, YouTube, Bluesky, Hacker News and the web (105 times).

On GitHub · 50

45 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 21

16 more on Bluesky

The file

Files
AGENTS.md

Docker, nginx and provisioner (docker/)

Compose files, nginx configuration and the sandbox provisioner. The Helm chart in deploy/helm/ carries the same nginx routes.

cd backend && python -m pytest tests -q -k "nginx or compose or sigterm"
  • Place the browser-stream WebSocket location before the generic threads location in the Docker, local and Helm nginx configs. nginx takes the first matching regex.
  • Publish a port with an explicit bind address. A bare "${PORT}:2026" binds 0.0.0.0. Both Compose files default the host to 127.0.0.1. Only the published nginx port is external.
  • The root PORT controls Docker ingress only. Local Next.js stays on 3000, so a value in .env cannot redirect the wait for the dev port.
  • Production starts the Gateway with the image's Python and exec, and Compose sets init: true, so SIGTERM reaches the Gateway.
  • In PVC mode the provisioner declares the user-data volume once. Extra mounts and Lark broker credential mounts reuse it with their own sub-paths. Credential mounts stay broker-only, and hostPath mode keeps distinct volumes.
  • Keep local temp paths relative to the checkout and aligned with scripts/serve.sh and scripts/nginx.sh. Docker log and restart commands resolve DEER_FLOW_ROOT from the checkout before they call Compose, the same as start and stop.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.