mirror of https://github.com/glittercowboy/get-shit-done synced 2026-04-26 01:35:29 +02:00

Files

Tibsfox 630a705bdc fix(gemini): use AfterTool instead of PostToolUse for Gemini CLI hooks

Gemini CLI uses AfterTool as the post-tool hook event name, not
PostToolUse (which is Claude Code's event name). The installer was
registering the context monitor under PostToolUse for all runtimes,
causing Gemini to print "Invalid hook event name" warnings on every
run and silently disabling the context monitor.

Changes:
- install.js: use runtime-aware event name (AfterTool for Gemini,
  PostToolUse for others) when registering context monitor hook
- install.js: uninstall cleans up both PostToolUse and AfterTool
  entries for backward compatibility with existing installs
- gsd-context-monitor.js: runtime-aware hookEventName in output
- docs/context-monitor.md: document both event names with Gemini
  example

Closes #750

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-28 05:38:11 -08:00

3.1 KiB

Raw Blame History

Context Window Monitor

A post-tool hook (PostToolUse for Claude Code, AfterTool for Gemini CLI) that warns the agent when context window usage is high.

Problem

The statusline shows context usage to the user, but the agent has no awareness of context limits. When context runs low, the agent continues working until it hits the wall — potentially mid-task with no state saved.

How It Works

The statusline hook writes context metrics to /tmp/claude-ctx-{session_id}.json
After each tool use, the context monitor reads these metrics
When remaining context drops below thresholds, it injects a warning as additionalContext
The agent receives the warning in its conversation and can act accordingly

Thresholds

Level	Remaining	Agent Behavior
Normal	> 35%	No warning
WARNING	<= 35%	Wrap up current task, avoid starting new complex work
CRITICAL	<= 25%	Stop immediately, save state (`/gsd:pause-work`)

Debounce

To avoid spamming the agent with repeated warnings:

First warning always fires immediately
Subsequent warnings require 5 tool uses between them
Severity escalation (WARNING -> CRITICAL) bypasses debounce

Architecture

Statusline Hook (gsd-statusline.js)
    | writes
    v
/tmp/claude-ctx-{session_id}.json
    ^ reads
    |
Context Monitor (gsd-context-monitor.js, PostToolUse/AfterTool)
    | injects
    v
additionalContext -> Agent sees warning

The bridge file is a simple JSON object:

{
  "session_id": "abc123",
  "remaining_percentage": 28.5,
  "used_pct": 71,
  "timestamp": 1708200000
}

Integration with GSD

GSD's /gsd:pause-work command saves execution state. The WARNING message suggests using it. The CRITICAL message instructs immediate state save.

Setup

Both hooks are automatically registered during npx get-shit-done-cc installation:

Statusline (writes bridge file): Registered as statusLine in settings.json
Context Monitor (reads bridge file): Registered as PostToolUse hook in settings.json (AfterTool for Gemini)

Manual registration in ~/.claude/settings.json (Claude Code):

{
  "statusLine": {
    "type": "command",
    "command": "node ~/.claude/hooks/gsd-statusline.js"
  },
  "hooks": {
    "PostToolUse": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node ~/.claude/hooks/gsd-context-monitor.js"
          }
        ]
      }
    ]
  }
}

For Gemini CLI (~/.gemini/settings.json), use AfterTool instead of PostToolUse:

{
  "hooks": {
    "AfterTool": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node ~/.gemini/hooks/gsd-context-monitor.js"
          }
        ]
      }
    ]
  }
}

Safety

The hook wraps everything in try/catch and exits silently on error
It never blocks tool execution — a broken monitor should not break the agent's workflow
Stale metrics (older than 60s) are ignored
Missing bridge files are handled gracefully (subagents, fresh sessions)

3.1 KiB Raw Blame History