You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set an agent going on something slow, look away, and be able to tell at a glance whether it's still making progress or whether it has died quietly.
How I do it today
In the CLI the token counter next to the spinner is what I read. I don't care about the number itself — I care that it's climbing. If it moves, the model is producing and I leave it alone; if it stops moving, something is wrong. It's a heartbeat, and I've come to rely on it more than I realised.
Where Paseo gets in the way
The working indicator shows a spinner and an elapsed timer. Seconds accumulating tells me time is passing, not that anything is happening — a wedged turn and a hard-thinking turn look identical, and both look "busy".
The practical consequence is that I can't make a good decision about when to interrupt. I sat on one turn for about twelve minutes before concluding it was never coming back, and nothing on screen at any point in those twelve minutes would have told me sooner. Worse, the elapsed timer actively argues against interrupting: the bigger the number gets, the more it feels like cancelling would throw away accumulated work. So I wait longer than I should, and then interrupt on a hunch anyway.
What would the flow look like if it worked for me
Two things, and the first is most of it:
A token count for the in-flight turn alongside the elapsed time, meaning the same thing it means in the CLI so I don't have to learn a second signal. From the outside it looks like the data is already arriving mid-turn — the context meter moves while a turn is running — it just isn't surfaced where I'm looking while waiting.
And when nothing has streamed for a while, say so. Something as plain as "no output for 4m" in place of a rising timer would turn a silent hang into something that announces itself. Idle time is the right trigger rather than total duration, since long turns are normal and shouldn't be flagged just for being long.
Informational only, to be clear — I don't want Paseo cancelling anything on my behalf. I just want to be able to tell the difference.
Originally filed as #2621 before I'd read CONTRIBUTING properly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
What am I trying to do
Set an agent going on something slow, look away, and be able to tell at a glance whether it's still making progress or whether it has died quietly.
How I do it today
In the CLI the token counter next to the spinner is what I read. I don't care about the number itself — I care that it's climbing. If it moves, the model is producing and I leave it alone; if it stops moving, something is wrong. It's a heartbeat, and I've come to rely on it more than I realised.
Where Paseo gets in the way
The working indicator shows a spinner and an elapsed timer. Seconds accumulating tells me time is passing, not that anything is happening — a wedged turn and a hard-thinking turn look identical, and both look "busy".
The practical consequence is that I can't make a good decision about when to interrupt. I sat on one turn for about twelve minutes before concluding it was never coming back, and nothing on screen at any point in those twelve minutes would have told me sooner. Worse, the elapsed timer actively argues against interrupting: the bigger the number gets, the more it feels like cancelling would throw away accumulated work. So I wait longer than I should, and then interrupt on a hunch anyway.
What would the flow look like if it worked for me
Two things, and the first is most of it:
A token count for the in-flight turn alongside the elapsed time, meaning the same thing it means in the CLI so I don't have to learn a second signal. From the outside it looks like the data is already arriving mid-turn — the context meter moves while a turn is running — it just isn't surfaced where I'm looking while waiting.
And when nothing has streamed for a while, say so. Something as plain as "no output for 4m" in place of a rising timer would turn a silent hang into something that announces itself. Idle time is the right trigger rather than total duration, since long turns are normal and shouldn't be flagged just for being long.
Informational only, to be clear — I don't want Paseo cancelling anything on my behalf. I just want to be able to tell the difference.
Originally filed as #2621 before I'd read CONTRIBUTING properly.
All reactions