Agent loop pressure
More turns are using five or more tools
97.8% now vs 94.7% previously (133 turns).
Inspect the affected turn sequences for repeated or avoidable tool selection.
InvestigateBidlo Status Frontend
Chat tool telemetry
Find slow, failing, and repetitive agent tools without exposing prompts, arguments, or outputs.
Detailed production timing active
6101 of 6166 saved tool calls include execution duration.
Tool calls
192
+27% vs previous 7d136 saved production turns
p50 latency
130 ms
+2% vs previous 7d192 timed calls
p95 latency
837 ms
-10% vs previous 7d192 timed calls
Tool failures
0.0%
No change vs previous 7d0 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
1.4
+6% vs previous 7d97.8% of turns at 5+ calls
What changed
Material regressions ranked by severity and affected call volume.
Regression checks require at least 3 calls in both windows. Latency is flagged at +20%; failure and no-result rates are flagged at +1 and +3 points respectively.
Execution volume
Successful calls, no-results, and failures combined.
Calls
Oct 1Oct 4Oct 7
Payload pressure
How often results exceed the 20 KB inline cap.
5.0%
handle rows / all calls
309 stored handles in this period. This is a payload-size proxy, not a one-to-one call classification.
Tool comparison
Each change is measured against the previous equal window; latency appears only where detailed timing exists.
| Tool | Calls | p50 | p95 | Failures | No result |
|---|---|---|---|---|---|
| app_dev_server_log | 192+27% vs prior | 130 ms+2% vs prior | 837 ms-10% vs prior | 0.0%No change vs prior | 0.0%No change vs prior |
Failure codes
Operational failures only; NoResults is excluded.
No operational failures
in the selected view
Interpretation notes
The data has known edges that change what a chart means.
- Blocked loops are invisible
- Rate-limited and identical-argument calls are rejected before telemetry fires.
- NoResults is not downtime
- It remains a failed tool outcome, but is separated from runtime reliability here.
- Preview volume lives elsewhere
- Preview and threadless chats reach PostHog but are intentionally absent from Postgres.
- Latency is partially instrumented
- Saved tool parts provide production outcomes and volume; duration appears only on calls with detailed telemetry.
- Partial turns are retained
- They remain in volume counts but are excluded from failures and latency percentiles.
- Comparisons use equal windows
- Every delta compares the selected period with the immediately preceding period under the same tool and team filters.
Recent sanitized calls
Arguments, outputs, user IDs, and message content are never rendered.
app_dev_server_logHJC125 msOct 6, 8:12 PM UTC
Outcome
Success
Thread
ed7becf5…
Tool call
call_iWk…
Turn sequence
28 of 29
Turn state
Completed
app_dev_server_logHJC207 msOct 6, 8:04 PM UTC
Outcome
Success
Thread
ed7becf5…
Tool call
call_7QA…
Turn sequence
25 of 27
Turn state
Completed
app_dev_server_logHJC136 msOct 6, 7:36 PM UTC
Outcome
Success
Thread
b612fa70…
Tool call
call_YF0…
Turn sequence
27 of 41
Turn state
Completed
app_dev_server_logHJC111 msOct 6, 7:38 PM UTC
Outcome
Success
Thread
b612fa70…
Tool call
call_0kI…
Turn sequence
39 of 41
Turn state
Completed
app_dev_server_logHJC328 msOct 6, 7:10 PM UTC
Outcome
Success
Thread
dae0a154…
Tool call
call_VCQ…
Turn sequence
29 of 36
Turn state
Completed
app_dev_server_logHJC326 msOct 6, 7:10 PM UTC
Outcome
Success
Thread
dae0a154…
Tool call
call_Dhl…
Turn sequence
33 of 36
Turn state
Completed
app_dev_server_logHJC163 msOct 6, 6:46 PM UTC
Outcome
Success
Thread
d41e378a…
Tool call
call_JaX…
Turn sequence
27 of 29
Turn state
Completed
app_dev_server_logHJC305 msOct 6, 5:21 PM UTC
Outcome
Success
Thread
b9ce5727…
Tool call
chatcmpl…
Turn sequence
14 of 24
Turn state
Completed
app_dev_server_logHJC108 msOct 6, 5:11 PM UTC
Outcome
Success
Thread
b9ce5727…
Tool call
call_95l…
Turn sequence
36 of 39
Turn state
Completed
app_dev_server_logBidlo128 msOct 6, 4:25 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_y2g…
Turn sequence
33 of 40
Turn state
Completed
app_dev_server_logHJC144 msOct 6, 4:18 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_gvo…
Turn sequence
17 of 28
Turn state
Completed
app_dev_server_logHJC96 msOct 6, 4:19 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_Rpx…
Turn sequence
25 of 28
Turn state
Completed
app_dev_server_logBidlo103 msOct 6, 4:12 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_v6a…
Turn sequence
20 of 23
Turn state
Completed
app_dev_server_logHJC116 msOct 6, 4:07 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_wOL…
Turn sequence
19 of 20
Turn state
Completed
app_dev_server_logHJC948 msOct 6, 4:02 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_5Ii…
Turn sequence
5 of 24
Turn state
Completed
app_dev_server_logHJC104 msOct 6, 4:02 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_ysE…
Turn sequence
15 of 24
Turn state
Completed
app_dev_server_logHJC154 msOct 6, 4:03 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_zGE…
Turn sequence
20 of 24
Turn state
Completed
app_dev_server_logHJC624 msOct 6, 4:00 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_hXm…
Turn sequence
4 of 13
Turn state
Completed
app_dev_server_logHJC144 msOct 6, 4:00 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_Mio…
Turn sequence
8 of 13
Turn state
Completed
app_dev_server_logHJC290 msOct 6, 4:00 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_ZrZ…
Turn sequence
12 of 13
Turn state
Completed
app_dev_server_logHJC115 msOct 6, 3:55 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_PZO…
Turn sequence
24 of 26
Turn state
Completed
app_dev_server_logBidlo119 msOct 6, 3:55 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_296…
Turn sequence
23 of 28
Turn state
Completed
app_dev_server_logHJC107 msOct 6, 3:51 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_AMC…
Turn sequence
16 of 18
Turn state
Completed
app_dev_server_logHJC111 msOct 6, 3:49 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
call_R41…
Turn sequence
6 of 7
Turn state
Completed