Elapsed time since the last chat message, shown above the Paseo composer.
npmjs · Paseo 0.9+
paseo plugin add npm:@stevecastaneda/paseo-time-since@1.0.0GitHub · Paseo 0.8 fallback
paseo plugin add stevecastaneda/paseo-plugins --ref 764f41794109da5fba12dc33a7533bf80febb8f7 --path time-sinceGit security status and fallback installation are pinned to commit 764f41794109.
From the plugin's README
Paseo 0.11 or later. Enable plugins in Settings → Plugins, then:
paseo plugin add npm:@stevecastaneda/paseo-time-since
Or from Paseo's plugin registry: paseo plugin add stevecastaneda/time-since.
README
Paseo 0.11 composer pill that ticks elapsed time since the last user_message or assistant_message in the agent thread.
It sits in the track above the composer. The plugin's server records when each agent turn ends, so after closing and reopening Paseo the clock still counts from the agent's last reply. Turns that ended before this plugin was installed fall back to the last user message, then the agent's creation time; those read older than the true reply, never newer. Live thread messages advance the clock while Paseo is open. It does not replace Paseo's message renderer.
Shows 4m 12s for the first five minutes, then 12m / 4h 12m with no seconds. Hidden while a turn is running. Press the pill to open a popover with the absolute timestamp.
Open Time Since Options in Command Center to show or hide the clock icon and add an optional ago suffix, such as 4m 12s ago. The panel includes a preview. Changes apply to all workspaces on the connected host and persist across restarts. The icon starts on and the suffix starts off.
Paseo 0.11 or later. Enable plugins in Settings → Plugins, then:
paseo plugin add npm:@stevecastaneda/paseo-time-since
Or from Paseo's plugin registry: paseo plugin add stevecastaneda/time-since.
Agent changes arrive through a subscription rather than repeated list requests. Elapsed time is calculated locally; the clock does not request settings from the daemon every second, and it never reads an agent timeline, which would start that agent's provider process. At launch it makes one request for the recorded turn ends of every agent. Labels update only when their displayed value changes.
Saved options apply immediately in the current client. Other connected clients pick them up when they next load the options or reload the plugin.
@getpaseo/client just for its types; it now gets them from the plugin SDK that Paseo already provides.npm ci asking for a package-lock.json, because npm 12 no longer reads the lockfile this plugin shipped (#53). The plugin no longer runs its own install step; Paseo's npm install already brings in what it needs.Scanned 15 Oct 2026, 12:34 UTC from stevecastaneda/paseo-plugins/time-since.