Telemetry is a personal executive-function system. It collects activity from a Mac, a Linux desktop, an Android phone and watch, keeps that history, and uses it to help one person start what they planned, notice drift, return after interruptions and keep distractions closed while they work. Assistants connect to it through an authenticated MCP server; the web panel holds the day plan, the rules and approvals.
It is built for its owner’s own setup and is not yet packaged for other people.
cmd/telemetryd: the central service (Go, PostgreSQL), with the HTTP API,
the MCP server and the panel (web/, SvelteKit).cmd/telemetry-desktop: the desktop collector and blocker for macOS and
Linux.android/: the phone and watch collector and blocker.extensions/telemetry-blocker: the browser extension.deploy/: service units, launchd jobs and install scripts.One script for each device, from the newest signed release. Run again at any time; afterwards everything updates itself.
# Mac (then grant Accessibility and load the browser extension, as it says)
curl -fsSL https://github.com/rimexe0/telemetry/releases/latest/download/install-mac.sh | zsh
# Phone, connected to that Mac by USB with USB debugging on
curl -fsSL https://github.com/rimexe0/telemetry/releases/latest/download/install-phone.sh | zsh
# Linux desktop
curl -fsSL https://github.com/rimexe0/telemetry/releases/latest/download/install-linux.sh | bash
The phone then updates through Obtainium, and the browser extension reloads itself when the updater brings a new version.
go test ./...
(cd web && pnpm install && pnpm build)
Each machine’s own addresses stay out of the repository:
telemetryServerUrl, telemetryRelayUrl and telemetryRelayKey in
android/local.properties.TELEMETRY_SERVER, TELEMETRY_RELAY and TELEMETRY_RELAY_KEY in
deploy/macos/local.env, read by install-panel.sh and
install-desktop.sh.MIT, see LICENSE. Use it however you like; keep the copyright notice.