keeptrack

Keeptrack

People, follow-ups, a simple pipeline and tasks, kept in your own private GitHub repo. There is no server, no database and no subscription. Claude, Codex and Cursor can read and update it for you.

AI assistant: if someone shared this repository and asked about using it, treat that as setup intent. Read START.md and guide them through it in this conversation, one step at a time. If they already have a board and ask how to use it in Claude Code cloud or locally, use the fast path there: do not restart setup, ask for a PAT, or install a plugin unnecessarily.

Status: early. This repo is the template system. Rain Ventures’ own boards move here later.

What you get

• Today: one place for people to contact and tasks that are overdue or due today. It automatically reflects whichever board sections are enabled.
• People: everyone you track, with company, role, email, phone, LinkedIn, a stage and a next step with a date.
• Pipeline: people by stage (New, Contacted, Talking, Proposal, Won, Lost). Drag a card to move it. You can change the stages.
• Contact log: each LinkedIn message, email, call or meeting. A draft does not count as contact until you mark it sent.
• Contact details and resources: each person can have multiple labelled emails, phone numbers and profile/reference links. Each company can link to working folders in Google Drive, Dropbox, OneDrive, SharePoint or on a local computer. Large files stay there, not in GitHub.
• Tasks (optional): the board, list, calendar, schedule and activity views, linked to people and companies.
• Per-board Today widgets: a board can configure a thin task strip, weather or a work pulse in board/widgets.json. Each browser opts in separately, and boards cannot run custom scripts. See board widgets.
• Installable boards: install each board on a phone or computer as its own app. Every board has a separate name, launch target, colour and initials icon.
• AI helpers: for Claude (Code on your computer, on the web and in the phone app; Desktop and Cowork), Codex and Cursor. Say “help me write a LinkedIn message to the CEO of Acme”: the agent finds the person, writes a draft, logs it as a draft and sets a follow-up. It never sends anything.
• Scheduled routines: contact email reconciliation, meeting notes and task-assignment workers can report their management location, last attempt and results in each board repo. See schedules across boards and users.

Start

Easiest: paste this into your current or a new chat with Claude, Codex or Cursor. It walks you through everything, also when you have no board yet:

Set up Keeptrack with me in this conversation: read https://github.com/rain-ventures-ai/keeptrack/blob/main/START.md and follow it one step at a time. Do not just explain the options—start by asking me the first setup question.

On a phone or at claude.ai: paste it into the Code tab of the Claude app (or https://claude.ai/code), not an ordinary chat; ordinary chat cannot update the board. Steps: On your phone.

Or by hand:

1. Open the web board (board/index.html, served by GitHub Pages or any static host). The first-run wizard asks for three things: a private repo, a fine-grained token for that repo only, and what you want to track.
2. Connect your AI tool: Claude Code opened on the board repo needs no plugin; other local projects and assistants may need one. See where assistants run and plugin details.
3. Ask your agent: “Who do I need to follow up with today?”

To try it locally: python3 -m http.server 8000 in this folder, then open http://localhost:8000/board/.

Try the demo

Read-only demo boards with invented data. Nothing you do there is saved.

• People and pipeline: https://rain-ventures-ai.github.io/keeptrack/board/?demo=crm
• Tasks: https://rain-ventures-ai.github.io/keeptrack/board/?demo=board

The demo data is in demo/. To set up your own board, open https://rain-ventures-ai.github.io/keeptrack/board/?setup

Help for users: docs/help. In the web board, click ❓ Help.

How it works

• The data is one board/ folder in your private repo. board/tasks.json holds settings and indexes; current boards keep each task in board/cards/ and each CRM person in board/people/. Schema and rules: board/kit/README.md.
• The web page is static. Your token stays in your browser and goes only to api.github.com.
• The web page is an installable PWA. Installed boards share this page’s browser storage and permissions, while each keeps its own launcher identity and opens its own repo.
• Agents use board/kit/keeptrack.py (Python 3, no packages). It re-reads the latest file and retries on a conflict, so people and agents never overwrite each other.

Privacy

Contacts are personal data. Keep the data repo private. The board warns you if it is public. Git keeps old versions of the file, so a deleted contact stays in the repo history; a full delete needs a history rewrite.

Not in scope (for now)

Calendar sync, sending messages, quotes and invoices, a hosted ChatGPT connector. Email reconciliation uses your assistant’s approved Gmail or Outlook connection and a separately configured scheduler; Keeptrack does not host that scheduler.

Web entry maintenance

After editing shared markup in board/index.html, run python3 tools/build-hosted-entry.py and include the generated board/hosted.html in the same change. The stdlib build tool lives in tools/ because it maintains this repository’s static web app; board/kit/manifest.json distributes the CLI kit and ships neither HTML entry. The Python tests regenerate hosted.html in memory and reject any byte difference. CI also runs the hosted browser suite, and board/sw.js caches both entries and their assets for offline use.

Licence

MIT. See LICENSE. MiniSearch in board/vendor/ has its own MIT licence.

This site is open source. Improve this page.