HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Ido-Levi
claude-code-tamagotchi
TypeScript2025–2025
Ido-Levi / claude-code-tamagotchi

claude-code-tamagotchi

Real-time behavioral enforcement for Claude Code. Monitors AI actions, detects violations, and interrupts misbehavior. Also has a cute pet.

2Distinct people
5Mentions
0Explicit recommenders
438GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Real-time behavioral enforcement for Claude Code. Monitors AI actions, detects violations, and interrupts misbehavior. Also has a cute pet.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day5 dated mentions

Observed mentions: 2025-08-14 14:33:39 UTC to 2025-08-22 12:41:52 UTC.

0122025-08-14 00:00:00 UTC to 2025-08-15 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 142025-08-15 00:00:00 UTC to 2025-08-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-16 00:00:00 UTC to 2025-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-17 00:00:00 UTC to 2025-08-18 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-08-18 00:00:00 UTC to 2025-08-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 182025-08-19 00:00:00 UTC to 2025-08-20 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-08-20 00:00:00 UTC to 2025-08-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-21 00:00:00 UTC to 2025-08-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-22 00:00:00 UTC to 2025-08-23 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 22

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 142025-08-14 00:00:00 UTC2025-08-15 00:00:00 UTC110
Aug 152025-08-15 00:00:00 UTC2025-08-16 00:00:00 UTC000
Aug 162025-08-16 00:00:00 UTC2025-08-17 00:00:00 UTC000
Aug 172025-08-17 00:00:00 UTC2025-08-18 00:00:00 UTC110
Aug 182025-08-18 00:00:00 UTC2025-08-19 00:00:00 UTC000
Aug 192025-08-19 00:00:00 UTC2025-08-20 00:00:00 UTC211
Aug 202025-08-20 00:00:00 UTC2025-08-21 00:00:00 UTC000
Aug 212025-08-21 00:00:00 UTC2025-08-22 00:00:00 UTC000
Aug 222025-08-22 00:00:00 UTC2025-08-23 00:00:00 UTC110

What Hacker News says

5 sources
I built a system that actually BLOCKS Claude from doing things you didn't ask for. Real-time violation detection with immediate intervention. How it works: EVERY interaction gets analyzed - every "I'll help you with that", every tool call, every single message. Whether Claude is thinking, reading a file, or trying to edit code - it ALL goes through GPT-OSS (via Groq for near-instant analysis). When you send a message, we extract your intent and add it to the session context. When Claude sends ANY message or tries ANY tool, we analyze if it aligns with your accumulated instructions. Every. Single. Time. The magic happens in the pre-hook: Before Claude can execute ANY operation (Edit, Bash, Read, etc.), our system checks for violations. If Claude is doing something you didn't ask for - BLOCKED. The operation never executes. Claude gets a de
Read the rest
tailed explanation of what went wrong and why. Examples it's caught: - Asked Claude to analyze code → it tried to commit → BLOCKED - Said "don't modify files" → Claude tried to edit → BLOCKED - Requested a backend fix → Claude wandered into frontend → BLOCKED - Asked to run tests → Claude said "I can't execute commands" → BLOCKED The system uses "trajectory thinking" - GPT-OSS analyzes your ENTIRE conversation history to understand context. "Fix this" knows what "this" refers to from 20 messages ago. "Don't use external libraries" from the start stays enforced throughout. It understands multi-step workflows, so normal investigation isn't flagged. Each Claude session maintains its own violation context - no cross-contamination between different conversations. Everything stored in SQLite, analyzed in real-time, blocked before damage. ...and it's also a Tamagotchi that lives in your statusline. Gets increasingly angry when Claude ignores instructions. Needs feeding every few hours. What started as a simple virtual pet somehow evolved into a full behavioral monitoring system. Feature creep at its finest. Install: bun add -g claude-code-tamagotchi Repo: https://github.com/Ido-Levi/claude-code-tamagotchi
In I built real-time course correction for Claude Code and it's also a Tamagotchi

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.