Paseo 0.11 or later. Enable plugins in Settings → Plugins, then:
\npaseo plugin add npm:@stevecastaneda/paseo-time-since\nOr from Paseo's plugin registry: paseo plugin add stevecastaneda/time-since.
![\"\"](\"https://raw.githubusercontent.com/stevecastaneda/paseo-plugins/main/time-since/icon.png\"){kind=icon}
\n\n# time-since\n\nPaseo 0.11 composer pill that ticks elapsed time since the last `user_message` or `assistant_message` in the agent thread.\n\nIt 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.\n\nShows `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.\n\n![\"The](\"images/composer-pill.png\")
\n\n![\"The](\"images/popover.png\")
\n\nOpen **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.\n\n![\"Time](\"images/options.png\")
\n\n## Install\n\nPaseo 0.11 or later. Enable plugins in **Settings → Plugins**, then:\n\n```bash\npaseo plugin add npm:@stevecastaneda/paseo-time-since\n```\n\nOr from Paseo's plugin registry: `paseo plugin add stevecastaneda/time-since`.\n\n## Updates\n\nAgent changes arrive through a subscription rather than repeated list requests.\nElapsed time is calculated locally; the clock does not request settings from\nthe daemon every second, and it never reads an agent timeline, which would\nstart that agent's provider process. At launch it makes one request for the\nrecorded turn ends of every agent. Labels update only when their displayed\nvalue changes.\n\nSaved options apply immediately in the current client. Other connected clients\npick them up when they next load the options or reload the plugin.\n\n## Changelog\n\n### 1.0.0\n\n- Version 1.0. Nothing you use changes. From now on, a new first number means an update breaks something, a new middle number means a new feature, and a new last number means a fix.\n- The preview in Time Since Options is the same size and shape as the real pill above the message box. It used to be a smaller pill.\n- Time Since Options no longer starts with a faint \"Time Since\" heading. The tab already names the panel.\n- While the options load, the spinner no longer touches the tab bar. If they fail to load, the error lines up with its Retry button.\n- New screenshot of Time Since Options in this README.\n\n### 0.4.0\n\n- Needs Paseo 0.11 or later. The plugin now carries its own icon and screenshots, and Paseo 0.9 and 0.10 refuse to load a plugin that does. On an older Paseo, the version you already have keeps working.\n- The plugin store now takes the icon and screenshots from each release, so they match the version you install.\n- New screenshots in this README.\n\n### 0.3.3\n\n- Installing the plugin no longer downloads any other npm packages. The plugin used to install `@getpaseo/client` just for its types; it now gets them from the plugin SDK that Paseo already provides.\n\n### 0.3.2\n\n- The plugin's page in Paseo's plugin store now uses the plugin's own description instead of text the store copied from paseo.cafe.\n\n### 0.3.1\n\n- Installs again with npm 12. Installing failed with `npm ci` asking for a `package-lock.json`, because npm 12 no longer reads the lockfile this plugin shipped ([#53](https://github.com/stevecastaneda/paseo-plugins/issues/53)). The plugin no longer runs its own install step; Paseo's npm install already brings in what it needs.\n- Install from npm or Paseo's plugin registry. Installing straight from GitHub no longer works.\n"}