Agent loop pressure
More turns are using five or more tools
97.7% now vs 90.0% previously (43 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
151
+278% vs previous 7d44 saved production turns
p50 latency
107 ms
-15% vs previous 7d151 timed calls
p95 latency
2.0 s
-13% vs previous 7d151 timed calls
Tool failures
0.7%
+0.7 pts vs previous 7d1 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
3.4
+72% vs previous 7d97.7% 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 |
|---|---|---|---|---|---|
| read_file | 151+278% vs prior | 107 ms-15% vs prior | 2.0 s-13% vs prior | 0.7%+0.7 pts vs prior | 0.0%No change vs prior |
Failure codes
Operational failures only; NoResults is excluded.
NotFound1
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.
read_fileHJC106 msOct 6, 6:08 PM UTC
Outcome
Success
Thread
50ac87df…
Tool call
call_QPH…
Turn sequence
1 of 28
Turn state
Completed
read_fileHJC502 msOct 6, 6:08 PM UTC
Outcome
Success
Thread
50ac87df…
Tool call
call_ZDp…
Turn sequence
4 of 28
Turn state
Completed
read_fileHJC112 msOct 6, 6:09 PM UTC
Outcome
Success
Thread
50ac87df…
Tool call
call_HET…
Turn sequence
22 of 28
Turn state
Completed
read_fileHJC473 msOct 6, 6:04 PM UTC
Outcome
Success
Thread
50ac87df…
Tool call
call_6Rj…
Turn sequence
3 of 13
Turn state
Completed
read_fileHJC99 msOct 6, 6:04 PM UTC
Outcome
Success
Thread
50ac87df…
Tool call
call_vcF…
Turn sequence
4 of 13
Turn state
Completed
read_fileHJC191 msOct 6, 5:58 PM UTC
Outcome
Success
Thread
7839e632…
Tool call
call_E1V…
Turn sequence
1 of 15
Turn state
Completed
read_fileHJC106 msOct 6, 5:58 PM UTC
Outcome
Success
Thread
7839e632…
Tool call
call_GGA…
Turn sequence
2 of 15
Turn state
Completed
read_fileHJC130 msOct 6, 5:58 PM UTC
Outcome
Success
Thread
7839e632…
Tool call
call_qHa…
Turn sequence
3 of 15
Turn state
Completed
read_fileTRP 2165 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_i4X…
Turn sequence
1 of 58
Turn state
Completed
read_fileTRP 2106 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_CpF…
Turn sequence
5 of 58
Turn state
Completed
read_fileTRP 2319 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_qaj…
Turn sequence
6 of 58
Turn state
Completed
read_fileTRP 2199 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_aFE…
Turn sequence
10 of 58
Turn state
Completed
read_fileTRP 2207 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_flG…
Turn sequence
11 of 58
Turn state
Completed
read_fileTRP 295 msOct 6, 1:59 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_KEj…
Turn sequence
21 of 58
Turn state
Completed
read_fileTRP 2103 msOct 6, 1:59 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_CxS…
Turn sequence
22 of 58
Turn state
Completed
read_fileTRP 2109 msOct 6, 1:59 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_ACn…
Turn sequence
23 of 58
Turn state
Completed
read_fileTRP 282 msOct 6, 2:01 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_YKY…
Turn sequence
40 of 58
Turn state
Completed
read_fileTRP 299 msOct 6, 2:01 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_iVY…
Turn sequence
41 of 58
Turn state
Completed
read_fileTRP 276 msOct 6, 2:01 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_JKr…
Turn sequence
42 of 58
Turn state
Completed
read_fileTRP 284 msOct 6, 2:01 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_1Ae…
Turn sequence
43 of 58
Turn state
Completed
read_fileTRP 287 msOct 6, 2:03 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_nda…
Turn sequence
47 of 58
Turn state
Completed
read_fileTRP 292 msOct 6, 2:03 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_fM0…
Turn sequence
48 of 58
Turn state
Completed
read_fileTRP 2105 msOct 6, 2:03 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_6SI…
Turn sequence
49 of 58
Turn state
Completed
read_fileTRP 292 msOct 6, 2:04 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_8ld…
Turn sequence
51 of 58
Turn state
Completed