fastmcp/tests/tasks/client
Jeremiah Lowin 19c5c507cc
Address review feedback on SEP-2663 tasks
- Client task support is opt-in via importing fastmcp_tasks (drop the core
  auto-load of companion packages); a plain Client never advertises tasks.
- A worker restores the submitting caller's auth token and headers from the
  task snapshot into the standard ambient context, so get_access_token() /
  get_http_headers() work in a distributed worker with no new core hooks.
- worker_cli validates the loaded extension's resolved backend, not env defaults,
  so a constructor-configured Redis worker starts.
- Thread the per-call read timeout through task polling; bound ToolTask.wait by
  its deadline; set_elicitation_callback rebuilds internal extensions so a
  later-set handler answers in-task input.
- README imports TaskConfig from fastmcp.utilities.tasks.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-07-22 19:14:16 -04:00
..
__init__.py Move task subsystem to fastmcp-tasks package, disconnect SEP-1686 wire from core 2026-07-21 21:51:45 -04:00
conftest.py Move task subsystem to fastmcp-tasks package, disconnect SEP-1686 wire from core 2026-07-21 21:51:45 -04:00
test_client_tool_tasks.py Add SEP-2663 client half: transparent call_tool, ResultClaim, Task handle 2026-07-22 15:21:10 -04:00
test_poll_interval.py Add SEP-2663 client half: transparent call_tool, ResultClaim, Task handle 2026-07-22 15:21:10 -04:00
test_transparent_tasks.py Address review feedback on SEP-2663 tasks 2026-07-22 19:14:16 -04:00