Activity

Activity for Paseo: local usage analytics and workspace agent management.

It still answers “how am I using Paseo” (tools, messages, models, habits). With the Explorer Workspace Activity panel it also becomes a vertical ops surface for the agents in the current workspace — sort, filter, search, open, archive — with live attention cues, open terminals, KPIs, and top skills / MCP.

| Scope | Role | |---|---| | Global | Cross-workspace habits: heatmap, rolling 168-hour activity timeline, provider filter, insights, most-used skills / MCP / models | | Workspace | Per-workspace agent fleet: ranked list + display prefs + archive; live status (permission / finished / error / running); open Terminals; shell / file / messages KPIs; times via shared FormattedTime | | Agent | Current session: dense tool KPIs, Skills / MCP header toggle, SKILL.md reader, composer Activity pill; Needs attention pill jumps to other same-workspace finished/permission/error sessions |

Architecture notes: docs/architecture.md.

What is counted

Ingests every agent's Paseo timeline into a local SQLite database. Queries read that database; the timeline and agents.list are ingestion / backfill / live-status sources only.

| Dimension | What is counted | |---|---| | Tools | Skill / MCP / shell / file calls; skills classified into exact / inferred / low confidence tiers | | Agents | Every created agent (registry with archive metadata) | | Messages | User-sent messages | | Models | Model at send time (weighted by messages; global view) |

Where it shows up

• Sidebar Activity — global view by provider (heatmap, KPIs, insights, most used)
• Explorer → Activity — workspace agents as a management list (search / sort / group / status / lifecycle / archive), live attention (permission badge, status colors, running spinner; API-owned directory observation + explicit lifecycle/archive fields + 15s reconciliation), open Terminals (list / preview / close), plus workspace KPIs and Skills / MCP ranked or newest-call timeline views (with agent titles and one shared persisted view choice); usage queries get a best-effort refresh hint when agents leave running
• Agent workspace panel — per-agent tool detail (dense KPI including messages / Skills / MCP toggle / SKILL.md); refreshes on timeline turn terminal events
• Composer pills — Activity: current agent's skill / MCP summary (hidden when empty); Needs attention: other same-workspace agents with finished / permission / error (hidden when none; click opens shared list)
• Command Center — Activity · Workspace Activity · Agent Activity

Data

Everything lives on the daemon machine in ~/.paseo/plugin-data/activity/ (SQLite usage.db). Nothing is sent anywhere.

Install

Requires Paseo >= 0.9.0-beta.2 (current package targets 0.9.0-beta.2). 0.4.0 is the last release that supports Paseo 0.8.0.

From Git (Paseo 0.8 and later):

paseo plugin add koinzhang/paseo-plugins --path activity

From npm (Paseo 0.9 and later; this is the source paseo.cafe hands to Paseo 0.9+). Pin 0.4.0 on Paseo 0.8:

paseo plugin install npm:@koinzhang/paseo-plugin-activity
# Paseo 0.8: npm:@koinzhang/[email protected]

After source changes, reload and check status:

paseo plugin reload activity
paseo plugin logs activity
paseo plugin ls

Limitations

• Analytics and the agent registry are local to each daemon: every machine keeps its own database, and there is no cross-host aggregation.
• Numbers are reconstructed from the Paseo timeline; items that do not report a model or skill cannot be attributed for that dimension.
• Skill classification is heuristic (exact / inferred / low confidence); check the tier before trusting a count.
• Workspace Activity focuses on agent operations for the current workspace; heatmap / provider / model breakdowns stay on the global sidebar.

Development

npm install
npm run typecheck
npm test

This plugin is spec-driven: read specs/README.md before coding, then the matching numbered directory.

Publish

Release history: CHANGELOG.md (current 0.4.0). npm releases go through a GitHub Release tag activity-vX.Y.Z (not push-to-main alone). Steps: CONTRIBUTING.md § Publishing to npm.

License

MIT © koinzhang