Skip to main content

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.

A GitTok feed on a phone, swiping up through five posts: a comic about garbage collection, a meme about a file deleted the day it was born, a group chat between two files, a spot-the-bug quiz, and a tier list of load-bearing files.

Quick start

macOS, uv, git and Claude Code or Codex:

uv tool install --python 3.13 'gittok[images]'
mkdir ~/gittok && cd ~/gittok
gittok init .
claude

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/

Metadata

Release files for gittok 1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gittok 1.2.0
File Size Uploaded Provenance Actions
gittok-1.2.0.tar.gz 29.6 MB With provenance Details for gittok-1.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for gittok 1.2.0
File Interpreter ABI Platform Actions
gittok-1.2.0-py3-none-any.whl Python 3 none any Details for gittok-1.2.0-py3-none-any.whl

Total release size: 56.8 MB

Release files / gittok-1.2.0.tar.gz

Download URL gittok-1.2.0.tar.gz
Size 29.6 MB
Tags Source
SHA-256 checksum
How to use checksums
f7325981d0b100b759f710c56f15df0d9819d38e90ed16851712f52e495b1d1d
BLAKE2b-256 checksum
How to use checksums
0c490601343e8fd5fabbe0293418b4b21e5e7d450dc2f494c10e951df3187caa
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 13, 2026.

Transparency log

Release files / gittok-1.2.0-py3-none-any.whl

Download URL gittok-1.2.0-py3-none-any.whl
Size 27.3 MB
Tags Python 3
SHA-256 checksum
How to use checksums
844d1b285383a8c8a370eb42d6dd3d0843f91dbaa67584405fb8762668f31013
BLAKE2b-256 checksum
How to use checksums
2fa032c68989864fede7427bdf039d670992745ac958ded412916de3d301baf5
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 13, 2026.

Transparency log

Security for gittok 1.2.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.

Select from 2 files

Attestation for gittok-1.2.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 13, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page