Everhour

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me time tracking that lives inside the tools I already use, replacing Everhour: a timer on my issues, budgets per project, and reports from the same data.

STACK
- Node 20+ with Fastify
- SQLite through better-sqlite3, WAL mode
- A browser extension, Manifest V3, that injects a timer into other web applications
- Caddy in front

THE DATA MODEL
- integrations: id, kind, base_url, credentials_encrypted, is_active, last_sync_at
- external_items: id, integration_id, external_id, kind, key, title, url, project_external_id, status, assignee_external_id, closed_at, synced_at — issues, tasks and cards, mirrored
- projects: id, name, client_id, external_ref, budget_kind, budget_amount, budget_hours, is_billable
- entries: id, user_id, project_id, external_item_id, description, started_at, ended_at, duration_seconds, is_billable, source, created_at
- rates: id, scope, scope_id, user_id, hourly_cents, currency, effective_from
- estimates: id, external_item_id, hours, set_by, set_at
- Time is attached to an external item by its identifier, never by its title. A renamed issue must not orphan a week of tracked hours

THE EXTENSION, WHICH IS THE WHOLE PRODUCT
- Content scripts per host, each one small and independent: find the issue on the page, read its identifier, inject a start button and a running total
- The identifier comes from the URL or from a stable data attribute, and never from scraped text. Write a per-host adapter with a single function: given the document, return the item's identifier, key and title
- When an adapter cannot find the item, the button says so plainly and offers a manual attach. A silent failure means hours land on nothing
- Every adapter has a fixture — a saved copy of the page — and a test against it, so a change to the host application is a failing test rather than a mystery
- The extension talks only to my own server, with a token from a sign-in flow. No third-party requests, and the permissions are per host rather than all sites
- Say this in the README: these adapters break, and maintaining them is the ongoing cost of the tool. Pick three hosts and keep them working rather than twelve that half work

SYNCING
- Pull projects, issues and their status from each integration on a schedule and on demand
- Store the external item so reports work when the source is unreachable, and so a deleted issue still has its hours
- Push nothing by default. Optionally write the tracked total back to the item as a field or a comment, off unless asked
- Respect rate limits with backoff and honour the API's own headers

TIMERS AND ENTRIES
- One running timer per user, enforced with a partial unique index
- An entry is two instants and the duration is derived
- Start from the extension, from the web interface or from the API
- Timer left running overnight is flagged and offered for trimming, never trimmed silently
- Manual entries against any item or against a project directly

BUDGETS
- Per project or per item: hours or money, one-off or recurring monthly
- Progress against estimates per issue, and against the budget per project
- Alerts at thresholds to the project owner, once per threshold, never repeatedly
- Over-budget is visible in the extension too, on the item itself — the warning is useful where the work is happening, not in a dashboard nobody opens

REPORTS AND INVOICING
- Group by client, project, item, person, day or tag, and filter by all of them
- Billable amount from the rate in force when the work happened
- Margin from the cost rate against the billable rate
- Export CSV and a client-facing PDF, and mark entries invoiced with a reference so nothing bills twice
- Everything computed from entries at query time; no stored totals

OPERATIONS
- .env: DATABASE_PATH, BASE_URL, SESSION_SECRET, ENCRYPTION_KEY, SMTP_URL
- Integration credentials encrypted at rest with a key from the environment
- Migrations on boot, each once
- Nightly backup off the machine, restore script
- Health endpoint that reports the age of the last sync per integration

WHAT MATTERS MOST
The adapters. Build one host end to end — find the item, inject the timer, attach the hours, survive a page navigation in a single-page application — and use it for a week before adding a second. The rest of this is a time tracker; the extension is the reason to build it at all.

Give me the repository, the extension, one host adapter with its fixture and test, migrations, .env.example, and a README with deploy steps behind Caddy and instructions for loading the extension unpacked.