Agent loop pressure
More turns are using five or more tools
96.2% now vs — previously (25 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
34
New activity vs previous 7d26 saved production turns
p50 latency
319 ms
Timing not instrumented34 timed calls
p95 latency
390 ms
Timing not instrumented34 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.3
New activity vs previous 7d96.2% 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 |
|---|---|---|---|---|---|
| get_flow | 34No prior data | 319 msNo prior timing | 390 msNo prior timing | 0.0%No prior data | 0.0%No prior data |
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.
get_flowHJC280 msOct 6, 7:58 PM UTC
Outcome
Success
Thread
ed7becf5…
Tool call
call_D7o…
Turn sequence
29 of 31
Turn state
Completed
get_flowBidlo374 msOct 6, 4:50 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_tnN…
Turn sequence
2 of 9
Turn state
Completed
get_flowBidlo352 msOct 6, 4:51 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_bgS…
Turn sequence
7 of 9
Turn state
Completed
get_flowBidlo342 msOct 6, 4:30 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_2CY…
Turn sequence
3 of 8
Turn state
Completed
get_flowBidlo307 msOct 6, 4:19 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_dCd…
Turn sequence
11 of 40
Turn state
Completed
get_flowBidlo297 msOct 6, 4:26 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_zAS…
Turn sequence
37 of 40
Turn state
Completed
get_flowHJC311 msOct 5, 11:34 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_Tkf…
Turn sequence
4 of 34
Turn state
Completed
get_flowHJC383 msOct 5, 11:34 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_BxW…
Turn sequence
15 of 34
Turn state
Completed
get_flowHJC298 msOct 5, 11:35 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_Pq9…
Turn sequence
22 of 34
Turn state
Completed
get_flowHJC380 msOct 5, 11:19 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_t4Q…
Turn sequence
6 of 23
Turn state
Completed
get_flowHJC371 msOct 5, 10:48 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_bQk…
Turn sequence
7 of 12
Turn state
Completed
get_flowHJC231 msOct 5, 10:48 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_u4K…
Turn sequence
11 of 12
Turn state
Completed
get_flowHJC219 msOct 5, 9:52 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_Epq…
Turn sequence
8 of 26
Turn state
Completed
get_flowHJC253 msOct 5, 9:47 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_sK8…
Turn sequence
2 of 6
Turn state
Completed
get_flowHJC373 msOct 5, 9:39 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_0SL…
Turn sequence
4 of 24
Turn state
Completed
get_flowHJC320 msOct 5, 9:40 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_cRX…
Turn sequence
22 of 24
Turn state
Completed
get_flowHJC352 msOct 5, 9:32 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_YBA…
Turn sequence
10 of 14
Turn state
Completed
get_flowHJC306 msOct 5, 8:21 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_8Ew…
Turn sequence
4 of 9
Turn state
Completed
get_flowHJC255 msOct 5, 8:15 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_2Y3…
Turn sequence
7 of 22
Turn state
Completed
get_flowHJC285 msOct 5, 8:11 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_POR…
Turn sequence
3 of 28
Turn state
Completed
get_flowHJC422 msOct 5, 8:05 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_c3j…
Turn sequence
4 of 25
Turn state
Completed
get_flowHJC374 msOct 5, 7:44 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_v3r…
Turn sequence
3 of 31
Turn state
Completed
get_flowHJC230 msOct 5, 7:33 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_vIf…
Turn sequence
32 of 48
Turn state
Completed
get_flowBidlo330 msOct 4, 5:30 AM UTC
Outcome
Success
Thread
3ed32d55…
Tool call
call_PZT…
Turn sequence
29 of 29
Turn state
Completed