Get bridge logs and cook errors
get_bridge_logsCollect recent cook errors and warnings from a running TouchDesigner project to debug script or cook failures. Surfaces the real Python traceback or operator cook errors without requiring a new REST endpoint.
Instructions
Read-only: collect recent cook errors and warnings from the running TouchDesigner project for debugging. Walks the operator tree under scope and gathers each operator's current cook errors and warnings (guaranteed). Also attempts a best-effort probe of textport/log DATs if they exist in the project. Use this when a script or cook fails and you need more context than the immediate error string — it surfaces the real Python traceback or operator cook errors without requiring a new REST endpoint. Returns {lines[], count, probe} where probe reports which log sources were reachable in this TD build.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Network path to collect cook errors/warnings from (default whole project). Must be an existing operator path. | / |
| max_lines | No | Cap how many log lines to return (1–500). | |
| include_cook_errors | No | Include current operator cook errors/warnings across the scope. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | Yes | The network path that was scanned, echoing the request. | |
| lines | Yes | Collected log lines, newest-first within each source. | |
| count | Yes | Total number of lines returned (after capping at max_lines). | |
| probe | No | Diagnostic info about which log sources were reachable in this TD build (cook_errors always present; textport availability varies by build). | |
| warnings | Yes | Non-fatal issues during collection (e.g. truncation notes). |