pi-time-tracker

Private working-hours receipts for Pi, reconciled by a tested Bend accounting policy.

Packages

Package details

extension

Install pi-time-tracker from npm and Pi will load the resources declared by the package manifest.

npm repohome report
$ pi install npm:pi-time-tracker
Package
pi-time-tracker
Version
0.2.3
Published
Sep 29, 2026
Downloads
797/mo · 15/wk
Author
ryanjoserbrosas
License
MIT
Types
extension
Size
212.6 KB
Dependencies
0 dependencies · 3 peers
Pi manifest JSON
{
  "extensions": [
    "./index.ts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

pi-time-tracker

Automatic work tracking for Pi.

Track client work across projects, keep records local, and review your hours.

checks npm version Pi extension License: MIT

Built for working across client repos in Pi without remembering to start and stop a timer. Open Pi in a project's folder and work as usual; the tracker associates activity with that workspace so you can review your hours later.

Run

After installing, tracking starts automatically. In Pi:

/project report

Workspace reports go to exports/work-report.md. Keep exports/ out of Git. Hours are inferred from Pi activity, not confirmed billable time; review them before using them in a timesheet or invoice.

Why pi-time-tracker?

Capability What it unlocks
⏱️ Automatic tracking Infer work windows without managing a timer.
🔀 No double-counting Count overlapping sessions once; long idle gaps stay Unknown.
🔒 Local records Built-in SQLite; no external sync or automatic prompt/transcript capture.
📝 Reviewable reports Markdown drafts, optional outcome notes and a separate manual clock.

How it fits

Pi activity → local SQLite and receipts → Markdown reports.

The extension observes activity inside Pi, including prompts, agent turns and tool events. It joins nearby activity into inferred work windows; long idle gaps stay Unknown. Leaving a session open does not turn its whole lifetime into work, and activity outside Pi is not observed.

Records stay on your machine, with no database server to set up. Workspace reports keep inferred work windows, measured agent activity and the optional manual session clock separate — they are different views, not hours to add together. See the architecture and development guide for details.

Install

Requires Node.js >=22.19.0 and a Pi 0.87.1-compatible host.

pi install npm:pi-time-tracker

Use --local to install for just the current project. Approve project trust when prompted, then use /reload in Pi. If switching from Git or a local checkout, remove the previous install first rather than loading both.

Usage

The folder name is the default client label. Set a name once and future sessions in that workspace inherit it; task labels apply to the current session:

/project set Coral   # optional client name; defaults to the folder name
/project task docs   # optional task for this session
/project report all  # report across tracked workspaces

Use /project status to check the current workspace, task and tracking settings. The all report covers inferred work windows across your tracked projects; manual session clocks and agent receipts stay in their workspace reports.

Documentation

License

MIT. Copyright © 2026 Ryan Brosas.

Powered by Coral Bricks.