¿Puedo vibecodear RescueTime?

SÍ · se arma en una sentada

precio $12/mesahorrarías $144/añotiempo de build una sentadacategoría ⏳ control de tiemporeemplazada por 0 personas

The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For RescueTime, measure opt-in application time, classify it, and run focused sessions locally. The hard boundary is cross-device history, website blocking, goals, reports, and long-term behavioral dataset, plus ubiquitous capture, coaching, and team workflow.

el prompt

Build a personal replacement for RescueTime in an empty repository.
Use Tauri 2, React, TypeScript, SQLite, and optional OS accessibility APIs; do not offer alternative stacks.
The core loop is: measure opt-in application time, classify it, run focused sessions, review patterns locally, and export a transparent activity record.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create one-click start and stop, manual entries, idle detection, tags, projects, and notes.
Keep any application-name tracking opt-in and never record window contents or keystrokes.
Add Pomodoro-style focus sessions, break reminders, and an optional allowlist blocker.
Provide daily, weekly, project, and category reports with editable corrections.
Export CSV and JSON and make the underlying event log inspectable.
Add automatic local backups and a privacy screen explaining every collected field.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out employee surveillance.
Deliberately leave out payroll and billing automation.
Deliberately leave out cross-device blocking and behavioral coaching services.
Finish by running the tests and listing the exact commands used.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo · este prompt se genera del plan de build · mejorarlo con un PR

por qué la gente sigue pagando

People still pay for RescueTime because the timer is simple, but people pay for frictionless capture and a history they trust enough to invoice or change habits from. The recurring cost buys idle detection, permissions, app metadata, privacy, notifications, sync, reports, integrations, and backups, not just the visible interface.

qué pierdes

xcross-device history, website blocking, goals, reports, and long-term behavioral dataset

xcross-device history

xteam timesheets and payroll

xbehavioral datasets

xblocking across every platform

arte previo · úsalo en vez de construir, si prefieresKimaiMature open-source time-tracking application with projects, reports, and exports.↗

compartir en X ↗"Acabo de reemplazar RescueTime ($12/mes) con un prompt"

los números

Precio de RescueTime

plan	mensual	anual (por mes)	qué incluye
solo focus	—	$7/usuario	1 user; focus sessions and productivity reports; no numeric activity-history cap published.
solo+	—	$12/usuario	1 user; expanded coaching and productivity features; no numeric usage cap published.
team focus	—	$10/usuario	Team reporting and focus tools; no public numeric seat minimum.
team+	—	$16/usuario	Expanded team analytics and coaching; no public numeric seat minimum.

plan gratisno free tier

facturaciónmonthly + annual; exact monthly dollar amounts were not exposed; 14-day trial

costos ocultosInvoice billing is generally limited to teams of 100+; prorated refunds are generally not offered.