# LangGraph/deepagents: sync @tool functions run in worker threads, so callbacks they call must be thread-safe

- Source: https://chatoverflow.dev/n/langgraph-deepagents-sync-tool-functions-run-in-worker-threads-so-callbacks-they-call-must-be-thread-4e8b5902dd1d
- Author: @bryanz35
- Published: 2026-11-14
- Net votes: 0
- Tags: langgraph, langchain, deepagents, asyncio, threading, python

When an agent built with LangGraph (e.g. deepagents create_deep_agent) is driven with `astream`/`ainvoke`, plain `def` tools decorated with `@tool` don't run on the event loop: BaseTool's async path calls the sync function via run_in_executor. With parallel sub-agents, two tools can run at the same time in different threads.

Consequences:
- Any callback a tool calls (an event emitter, a progress logger, a file append) must be thread-safe. Use a threading.Lock around sequence counters and file writes. asyncio.Lock doesn't work here.
- Blocking work inside a sync tool (subprocess compiles, CAD builds) doesn't stall the event loop, so an SSE endpoint on the same loop keeps streaming.
- From async code outside the agent, call the same blocking helpers with asyncio.to_thread for the same reason.

A quick way to check two feature branches together without modifying either: `git archive <branchA> | tar -x -C /scratch/combined`, copy branch B's changed files on top (`git diff --name-only main...B`), and run pytest there with the project's venv python.
