Issue #34 made the hooks honor CLAUDE_CONFIG_DIR when writing the mode flag ($CLAUDE_CONFIG_DIR/.ponytail-active), enforced by tests/hooks.test.js. But both statusline scripts still hardcoded $HOME/.claude/.ponytail-active, so any user with CLAUDE_CONFIG_DIR set gets no badge — or a stale mode from a pre-migration ~/.claude flag that never updates again. Make both scripts resolve the flag the same way getClaudeDir() does: prefer CLAUDE_CONFIG_DIR, fall back to ~/.claude. The fallback branch is identical to the previous behavior, so unset-env users are unaffected. Also corrects the now-inaccurate path comment in the activation hook header.
79 lines
2.7 KiB
JavaScript
79 lines
2.7 KiB
JavaScript
#!/usr/bin/env node
|
|
// ponytail — Claude Code SessionStart activation hook
|
|
//
|
|
// Runs on every session start:
|
|
// 1. Writes flag file at $CLAUDE_CONFIG_DIR/.ponytail-active (defaults to ~/.claude; statusline reads this)
|
|
// 2. Emits ponytail ruleset as hidden SessionStart context
|
|
// 3. Detects missing statusline config and emits setup nudge
|
|
|
|
const fs = require('fs');
|
|
const path = require('path');
|
|
const { getDefaultMode, getClaudeDir } = require('./ponytail-config');
|
|
const { getPonytailInstructions } = require('./ponytail-instructions');
|
|
const {
|
|
clearMode,
|
|
isCodex,
|
|
setMode,
|
|
writeHookOutput,
|
|
} = require('./ponytail-runtime');
|
|
|
|
const claudeDir = getClaudeDir();
|
|
const settingsPath = path.join(claudeDir, 'settings.json');
|
|
|
|
const mode = getDefaultMode();
|
|
|
|
// "off" mode — skip activation entirely, don't write flag or emit rules
|
|
if (mode === 'off') {
|
|
clearMode();
|
|
writeHookOutput('SessionStart', 'off', isCodex ? '' : 'OK');
|
|
process.exit(0);
|
|
}
|
|
|
|
// 1. Write flag file
|
|
try {
|
|
setMode(mode);
|
|
} catch (e) {
|
|
// Silent fail -- flag is best-effort, don't block the hook
|
|
}
|
|
|
|
// 2. Emit the ponytail ruleset, filtered to the active intensity level.
|
|
let output = getPonytailInstructions(mode);
|
|
|
|
// 3. Detect missing statusline config — nudge Claude to help set it up
|
|
if (!isCodex) try {
|
|
let hasStatusline = false;
|
|
if (fs.existsSync(settingsPath)) {
|
|
// Strip UTF-8 BOM some editors prepend on Windows (breaks JSON.parse)
|
|
const raw = fs.readFileSync(settingsPath, 'utf8').replace(/^\uFEFF/, '');
|
|
const settings = JSON.parse(raw);
|
|
if (settings.statusLine) {
|
|
hasStatusline = true;
|
|
}
|
|
}
|
|
|
|
if (!hasStatusline) {
|
|
const isWindows = process.platform === 'win32';
|
|
const scriptName = isWindows ? 'ponytail-statusline.ps1' : 'ponytail-statusline.sh';
|
|
const scriptPath = path.join(__dirname, scriptName);
|
|
const command = isWindows
|
|
? `powershell -ExecutionPolicy Bypass -File "${scriptPath}"`
|
|
: `bash "${scriptPath}"`;
|
|
const statusLineSnippet =
|
|
'"statusLine": { "type": "command", "command": ' + JSON.stringify(command) + ' }';
|
|
output += "\n\n" +
|
|
"STATUSLINE SETUP NEEDED: The ponytail plugin includes a statusline badge showing active mode " +
|
|
"(e.g. [PONYTAIL], [PONYTAIL:ULTRA]). It is not configured yet. " +
|
|
"To enable, add this to ~/.claude/settings.json: " +
|
|
statusLineSnippet + " " +
|
|
"Proactively offer to set this up for the user on first interaction.";
|
|
}
|
|
} catch (e) {
|
|
// Silent fail — don't block session start over statusline detection
|
|
}
|
|
|
|
try {
|
|
writeHookOutput('SessionStart', mode, output);
|
|
} catch (e) {
|
|
// Silent fail — stdout closed/EPIPE at hook exit must not surface as a hook failure
|
|
}
|