Does the observation of Continuous Learning v2 work with VS Code Claude Code?

[csy19960309]

I find that there are some filters to prevent observe.sh from firing on non-human sessions to avoid. Is claude code on VS Code blocked in this way?

[affaan-m]

Short answer: VS Code Claude Code is not blocked by a VS Code-specific filter in the current plugin path.

What happens today:

• The plugin registration in hooks/hooks.json routes PreToolUse/PostToolUse through scripts/hooks/observe-runner.js, not directly through a copied observe.sh entry in ~/.claude/settings.json.
• observe-runner.js derives pre / post from the hook id and invokes skills/continuous-learning-v2/hooks/observe.sh.
• observe.sh allows CLAUDE_CODE_ENTRYPOINT values cli, sdk-ts, and claude-desktop; if the variable is unset, it defaults to cli.
• The non-human guards are aimed at automation/self-observation: ECC_HOOK_PROFILE=minimal, ECC_SKIP_OBSERVE=1, payloads with agent_id, and configured observer-session path exclusions.

So if the VS Code integration emits normal Claude Code hook events and either leaves CLAUDE_CODE_ENTRYPOINT unset or uses one of the allowed values above, observation should run. If that extension sets a different entrypoint value, it would currently be skipped by the entrypoint guard.

A quick local check is to run a simple tool action from VS Code Claude Code and then inspect the project-scoped continuous-learning-v2 observations.jsonl for a new row. If it does not record, the useful data point is the hook environment value for CLAUDE_CODE_ENTRYPOINT; we can add an explicit vscode allowlist entry if that is what the extension uses.

[csy19960309]

It is found at anthropics/claude-code#44466 anthropics/claude-code#40766 anthropics/claude-code#10027 that CLAUDE_CODE_ENTRYPOINT is set to claude-vscode when the vscode extension is being used.