GitTok
Doomscrolling Your Code
GitTok turns your git repos into a TikTok-style feed. Swipe through short posts about the code you work in every day: the function everything depends on, the commit that got reverted twice, the TODO that has been waiting for six years, the two files that always change together.
Some posts teach. Some are quizzes: spot the bug, guess who wrote it, guess when. Some are memes, comics, tier lists, group chats and horoscopes about your own code, with a cast of regulars arguing in the comments. Swipe up for the next post. Swipe sideways to go deeper, from the hook down to the real code and the real diff.
- Every post is checked against git. Your coding agent (Claude Code or Codex) writes the posts, and GitTok verifies each cited commit, file and line before a post reaches your feed.
- It learns what you like. What you read, like and skip shapes the posts that get made next. You can also just say it: "less memes, more of the sync engine."
- It helps things stick. A quiz you got wrong comes back a day later, then after three days, then a week, until you have it.
- It is private. Everything runs on your own machine. GitTok never writes to your repos and calls no model API of its own.
Quick start
macOS, uv, git and Claude Code or Codex:
uv tool install --python 3.13 gittok # Claude Code: see "Better images" below
mkdir ~/gittok && cd ~/gittok
gittok init .
claude
Better images in Claude Code. Claude Code has no image tool, so without extras Claude draws the illustration and comic posts as simple flat SVG pictures. On Apple silicon, install with the
imagesextra for real illustrations:uv tool install --python 3.13 'gittok[images]'(add--forceif GitTok is already installed, then start a new session). On other Macs the extra adds nothing. It adds mflux (about 1 GB) and a 6 GB model that GitTok downloads by itself. Codex uses its own image tool by default. To use mflux in Codex instead, install with the extra and ask Codex: "Use local image generation." Or set it yourself inlocal/settings.yamlof your GitTok directory:render: image_backend: local
Approve the gittok MCP server, then ask Claude: "Add the repo at ~/src/myapp to GitTok." When the first posts are made, open the feed address that Claude gives you on your phone (or ask "what is the feed address?"), tap "Pair with a code", tell Claude the code, and start scrolling.
For Codex, run codex in the same directory, trust the project configuration and review /hooks. Ask Codex to add a repo, or use $gittok-generate to make cards. Both agents share the same workflows and MCP server.
Documentation
https://nvoxland.github.io/gittok/
- Install and your first feed
- Guide: repos, cards, steering, how the feed learns, privacy, configuration, the feed API
- Blog: what is new in each release
Metadata
Release files for gittok 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gittok-1.3.0.tar.gz | 29.6 MB | With provenance | Details for gittok-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gittok-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for gittok-1.3.0-py3-none-any.whl |
Total release size: 56.9 MB
Release files / gittok-1.3.0.tar.gz
| Download URL | gittok-1.3.0.tar.gz |
|---|---|
| Size | 29.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67c218ba40989dba3acc6fc4769fdcc32b581c14e8c8932cdd06c4b729d18eff
|
|
BLAKE2b-256 checksum How to use checksums |
bf9975965b515e3e5dbd2f88831242fcdbcf77735e19252a3eaa5913bf3d9f53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logRelease files / gittok-1.3.0-py3-none-any.whl
| Download URL | gittok-1.3.0-py3-none-any.whl |
|---|---|
| Size | 27.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f3428f80e9907bac493412714ef590cfa217d4d49d2435b87d766127625c56b
|
|
BLAKE2b-256 checksum How to use checksums |
9593cb212af19c6b5e4434b1ed6bdd9b1a11d55f25d7b7387ca7963fc448d164
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logSecurity for gittok 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for gittok-1.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.