Your AI assistant can read and update your board. It uses the Keeptrack skill (instructions) and keeptrack.py (a small tool). It never sends a message for you.
Not sure which assistant to use, or whether you need Python? See Where your assistant runs.
The quickest way: in the web board open ⚙️ Settings → Agents & integrations → Claude or Codex in your chat app, open Set it up by hand, select your tool, and copy the steps. Claude Code does not always need a plugin.
Already installed? Check first: in the Claude app open Customize → Plugins. If keeptrack is listed, make sure it is switched on and skip the steps below. If only the rain-ventures-ai/keeptrack marketplace is listed, install keeptrack from it; do not add the marketplace again.
| Tool | How |
|---|---|
| Claude Desktop or Cowork | Customize → Plugins → Add → Add marketplace, type rain-ventures-ai/keeptrack, then install keeptrack. |
| Claude Code cloud | Start the session on the board repo, or add the board repo as a second repo. No plugin or PAT. |
| Claude phone app or claude.ai in a browser | Use the Code tab (or https://claude.ai/code): it is Claude Code cloud, so start the session on the board repo. Ordinary chat cannot update the board. Steps: On your phone. |
| Claude Code locally in the board repo | Start claude in the repo. No plugin; use your existing gh login. |
| Claude Code locally in another project | claude plugin marketplace add rain-ventures-ai/keeptrack then claude plugin install keeptrack@keeptrack |
| Codex | codex plugin marketplace add rain-ventures-ai/keeptrack, then install keeptrack from /plugins. |
| Cursor | In Agent chat: /add-plugin https://github.com/rain-ventures-ai/keeptrack |
| ChatGPT | ChatGPT cannot update the board yet. Use 🤖 Copy for AI on a person, paste it into ChatGPT, then log the draft on the board yourself. |
The Keeptrack repo is public, so anyone can install the plugin. Full details: board/kit/PLUGIN.md.
The plugin is the package that installs Keeptrack into an assistant when you are not working inside the board repo.
It includes keeptrack.py plus focused skills—instructions the assistant selects for the job:
keeptrack: everyday people, follow-up, pipeline and task work.onboard-keeptrack: guided import of existing contacts and tasks.keeptrack-notes: meeting notes and action items.keeptrack-email: safe mailbox-to-contact reconciliation.Every board repo also carries the board-local versions it needs. That is why Claude Code can work directly in a board repo without installing the plugin. See the plugin and skill layout for Claude, Codex and Cursor, or choose where your assistant runs.
Inside the board repo, Claude gets the board name from the Git remote and does not need a .board setting. In another
local project, the plugin asks for your board repo (for example your-name/my-keeptrack) and GitHub username. It saves
them in a hidden .board folder in that project. It never saves your token.
Locally, it needs access to your repo in one of these ways:
gh auth login), orType @claude in a task comment and your own Claude routine starts work on that task. To set it up, open ⚙️ Settings → Agents & integrations → @claude in task comments and switch Use @claude on. Five steps with a ✓ for each, then a real test. Details: ROUTINE-SETUP.md.
Use a separate scheduled email routine to compare recent Gmail or Outlook messages with the exact email addresses on your Keeptrack people. It can add concise sent/received email facts to contact logs and update an explicit next step, but it never sends, drafts or deletes mail. The routine keeps its last successful run and recent run summaries in its own owner-specific checkpoint, without storing message bodies, subjects, attachments or email addresses there.
Ask Claude Code in the board repo: “Set up my Keeptrack contact email routine.” It follows the
keeptrack-email skill and asks which mailbox and schedule to use. Keep this routine separate from the task-comment
routine so an untrusted board comment never has access to your mailbox.
For setup, last-run reports, multiple email accounts and avoiding duplicate entries from shared threads, see Schedules and shared boards. A personal board can use both work and personal mail to propose project or task updates for your approval; that is a separate workflow from automatically logging existing contacts.