Unclear The finding doesn't say what triggers a speculative run to start or how often predictions are expected to match.
The classifier that decides whether a remote tool call is automatically allowed can now run ahead of time, speculatively predicting the answer before the actual permission request arrives. If the real request matches the prediction, the pre-computed result is reused; if it doesn't match, the speculative work is discarded and the classifier runs normally.
New internal helper functions handle building, checking, and abandoning these speculative runs. The tengu_remote_tool_classifier telemetry event, which tracks this classifier's behavior, now also records speculative_* and queue_* fields, including a speculative_discard_reason for when a prediction doesn't pan out.
Running the classification speculatively can let the permission decision be ready sooner when the prediction is correct, since the work happens ahead of the actual ask instead of starting after it.
The finding doesn't say what triggers a speculative run to start or how often predictions are expected to match.