jitters-cli

Jitters the VibeCoder, an anxious monkey who codes, in the state of your week of commits. Groggy after your 2 am commits, fit after a week of daytime ones, on the sofa after a week of none.

uvx jitters-cli

(or pipx run jitters-cli; with Node: npx -y https://vibeoverflow.lol/dl/jitters-cli.tgz)

        .-"""-.   3am
   .-. / .---. \ .-.
  ( (_|  @   -  |_) )
   '-.|    v    |.-'
      \   ~~~   /
       '-.___.-'
  c[_] c[_] c[_] c[_] c[_]

Jitters, your week: groggy
You commit after midnight. He is groggy and on his fifth coffee.

It prints one link to see him drawn in that mood, with a picture to save: vibeoverflow.lol/week.

What it reads

Only the dates and hours of your own commits (your git config user.email) of the last 7 days in the folder it runs in. No network call, no telemetry, no dependency. The link carries the mood word, nothing else. --all counts every author.

The rules, first that holds

1. seven days with nothing committed: sofa
2. a third or more of your commits between midnight and 5 am: groggy
3. ten or more a day: wired
4. five days or more of daytime commits, none after midnight: fit
5. one or more a day: steady
6. less than one a day: sleepy

For your coding agent (MCP)

One tool, jitters_week: "how wrecked is my monkey?"

{ "mcpServers": { "jitters": { "command": "uvx", "args": ["jitters-cli", "--mcp"] } } }

Claude Code: claude mcp add jitters -- uvx jitters-cli --mcp

Options

--json prints the answer as JSON; --all every author; --mcp runs the stdio server.

Him, on your desk

Jitters at your own commit hour on a mug, and his night as stickers: the shop.

MIT. Made by the Vibeoverflow team, vibeoverflow.lol.