From 473ab205ac8f77b51b7b25c547f8445310d4ed8e Mon Sep 17 00:00:00 2001 From: Yangze Luo Date: Tue, 22 Sep 2026 14:41:22 +0800 Subject: [PATCH 1/2] docs: say that taskcut is silent without the function-hooks flag, and how to check Without CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 the plugin is listed as installed and never runs, and neither it nor Claude Code says so. The debug log names the module when it loads, before any login is needed. Co-Authored-By: Claude Opus 5 (1M context) --- README.md | 11 +++++++++++ docs/troubleshooting.md | 11 +++++++++++ 2 files changed, 22 insertions(+) diff --git a/README.md b/README.md index b4a7cd5..179abdc 100644 --- a/README.md +++ b/README.md @@ -41,6 +41,17 @@ CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 claude The install notes that options are "not yet set". That is fine: unset, each takes its default. +`CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1` is needed on every launch while function +hooks are in early access. Without it the plugin is listed as installed but never +runs, and nothing says so. To set it once, put +`"CLAUDE_CODE_ENABLE_FUNCTION_HOOKS": "1"` under `env` in +`~/.claude/settings.json`. To check that taskcut loads: + +```bash +CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 claude -p ok --debug-file /tmp/taskcut.log >/dev/null +grep 'taskcut@taskcut loaded' /tmp/taskcut.log +``` + Then work as usual. Nothing happens until the context passes 35% — the `ctx` figure in the status line. From then on, when a piece of work is finished, a dim line says so and Claude Code compacts exactly as `/compact` would: diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 9d9026f..694cf55 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -26,6 +26,17 @@ is not loaded at all — the plugin still appears in `claude plugin list`, and n of its hooks run. This is Claude Code's flag, not taskcut's, and it will stop being needed when the feature graduates. +Whether the module loaded is in Claude Code's debug log, whatever the context +fill: + +```bash +claude -p ok --debug-file /tmp/taskcut.log >/dev/null +grep 'taskcut@taskcut' /tmp/taskcut.log +``` + +`hooks module taskcut@taskcut loaded` means it is running; no line at all means +the flag was not set for that launch. + ### 2. Is the plugin loaded? ```bash From 4d238e8fe8e88b019c41d6351a7be0ae08b5e20e Mon Sep 17 00:00:00 2001 From: Yangze Luo Date: Tue, 22 Sep 2026 14:41:57 +0800 Subject: [PATCH 2/2] docs: the debug log says why the module did not load Co-Authored-By: Claude Opus 5 (1M context) --- docs/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 694cf55..adc4561 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -34,8 +34,8 @@ claude -p ok --debug-file /tmp/taskcut.log >/dev/null grep 'taskcut@taskcut' /tmp/taskcut.log ``` -`hooks module taskcut@taskcut loaded` means it is running; no line at all means -the flag was not set for that launch. +`hooks module taskcut@taskcut loaded` means it is running. `not loaded:` is +followed by the reason; without the flag, it says the rollout flag is off. ### 2. Is the plugin loaded?