Your comment will be posted, then your Claude routine will be started to work on task . It will report back on this task with comments, and hand it back to you when it is done. It starts in about one to two minutes.
The repository is public. Anyone on the internet can read every card: titles, descriptions, comments, contacts, links and history.
Unless that is what you want, make the repository private now: GitHub → the repo → Settings → General → Danger Zone → Change visibility → Make private.
This warning shows on every page load while the repository is public.
Pull requests linked on cards, read live from GitHub with your board login. Nothing here changes a card.
Choose how you want to use the cards in the current view. Active filters are included.
Show me around A one-minute tour of Today, Kanban, People and the menus.
One place for people to contact and tasks that are overdue or due today. It shows whichever board sections you have enabled.
Everyone you keep track of. Press Add… for a simple form, or type Name | Client | Role and press Enter for a quick add.
People by stage. Drag a card to change the stage. Logging a sent message moves a new person to the second stage.
In a person's card, write what you sent or said, pick the channel, then Log. Tick Draft to keep a message you have not sent yet. Mark sent when you send it.
Keep big files in Google Drive, Dropbox or OneDrive. Add the folder links in the Files part of a person's card.
Board, List, Calendar and Schedule show the same tasks. Click or tap a card to open it. A task can be linked to a person. To add one, type a title in a lane's box and press Enter, or press Add (or Shift+Enter, or the lane's ＋) to add it and open it at once, ready for details, client, project, priority, due date, labels, checklist and links.
Claude Code in this board repo: the repo already contains Keeptrack's skills and tool, so no plugin is needed. On a phone or at claude.ai: use the Code tab of the Claude app (or claude.ai/code) in a session on this board repo; ordinary chat cannot update the board. Claude or Codex in another project, Cowork, or Cursor: install the Keeptrack plugin so the same skills and tool are available there.
Open Settings → Agents & integrationsWhich setup should I use?Plugin guideKeeptrack skills
Copy for AI still works with any ordinary chat. Assistants draft messages; they never send them.
Press / or click to search everything. Old done tasks and Lost people can be moved to the archive (Settings → Board → Archive). Search finds them, and you can put them back.
This browser remembers the last screen and open task for each board. Unfinished title and description edits are kept here too; if GitHub changed the same text, Keeptrack asks which version to use when you save. Tap Undo after a change, or use Menu → Undo last change on a phone. The five latest Undo actions survive a reload. Keeptrack asks before deleting important items.
The demo board, a public board with no token, and a token without write access are read-only. A banner at the top tells you why.
Keeptrack repository · Full help: all topics · getting started · people · board widgets · AI assistants · privacy · problems · demo boards: people, tasks
Import a DESIGN.md file. Keeptrack reads its colours only.
When enabled, theme, card style and imported colours apply only to this board in this browser. Turn off to return to your browser’s usual appearance; your board preference is kept.
Off by default. Turn on to use the widgets configured in this board’s widgets.json. Turning off hides them and stops their requests; it does not delete the configuration. Supported widgets can adjust their own layout, but cannot run custom scripts. Weather widgets contact Open-Meteo using their configured location.
“My cards” are cards assigned to you. Your agents write as claude@you or codex@you. The page checks about every 30 seconds.
claude@you
codex@you
To do, In progress and Done stay, because agents use them. A new column goes before Done.
Sign in to a local hosted board
One token per board, kept in this browser and sent only to api.github.com. Make a token with the right permissions →
The link fills in the Resource owner and the Contents and Issues permissions. You still choose Only select repositories and pick this board repo.
One token can serve every board it can access. Boards owned by different GitHub organisations may need different tokens.
Dots in the box but “not saved” in the status? Your password manager filled it. Select Save & connect to keep that value.
The report never contains your token. Paste it to Claude or a teammate if you need help.
You make the repo and the token; Claude adds the board files and checks them, following NEW-BOARD.md.
…
The board checks for a new version about every 10 minutes. Update forces a full refresh that skips every cache.
Copies every board and setting saved in this browser, unencrypted. Tokens and keys are left out unless you tick the box; with them, treat it like a password and delete the message you send it in.
Removes this board's token, and the copy of the board kept for a fast start, from this browser.
An assistant will help verify your sources, permissions and existing schedules before setting anything up. You choose the actual scheduler: Claude, Codex or another supported runner. A local runner needs its computer available.
Paste into your board-aware assistant. Approve scope and schedule before provisioning. Cleanup and briefings propose changes first; they do not delete, archive or change tasks without approval.
Each routine has a board, owner, workflow and approved sources. Reuse an existing matching schedule instead of creating a duplicate. Shared boards keep owner-specific checkpoints and deduplicate imported source events; a register alone is not a cross-user lock.
The worker reports its start, completion, summary and counts into automation/routines/<id>.json using Keeptrack's routine commands. Keep secrets and private email content out of reports.
automation/routines/<id>.json
You need a Claude plan with routines, a GitHub token for the routine and a free cron-job.org account. About ten minutes.
A routine is Claude working in the cloud for you. It uses your own Claude plan.
Click New routine and fill in:
The routine needs its own GitHub token for this board.
BOARD_TOKEN
This token stays in your routine. This page never sees it.
An API trigger lets something outside Claude start your routine with a web address and a token.
A web page cannot start a routine by itself. A free cron-job.org account does it for the page, in about one minute.
The page makes a small test task and asks Claude to say hello on it. This takes about two minutes.
Test cron-job.org on its own: it opens this page one time and does not start Claude. Takes about two minutes.
The report has no tokens or keys. Paste it to Claude or to a teammate to get help.
Claude explains each step, or does the clicking in your browser. It never handles your secrets: you paste those yourself. Full guide: ROUTINE-SETUP.md.
When a card's newest request is for @codex, the card's top button becomes Copy for Codex. Paste that into Codex; it claims the card and reports back.
This browser marker does not create, enable or pause a schedule. Check the routine's saved report above and manage the actual job in its scheduler.
It matches exact addresses on your people and records short contact facts. It never stores full email text or attachments, and never sends, drafts, deletes or marks mail as read.
It keeps a last-run checkpoint in the board repo, separate from the @claude routine. Open the guide →