AgriciDaniel/claude-obsidian

> `mkdir -p .claude && ln -s ../skills ../agents ../hooks ../commands .claude`

excellent

Adding a downstream-impact data point to escalate the severity of this bug from "cosmetic but noisy" to "triggers user-visible breakage in adjacent Claude Code features."

**Setup**
- Claude Code 2.1.123 on macOS 15.7 (Darwin 25.5.0)
- claude-obsidian v1.4.3 (vendored `hooks/hooks.json` unchanged)
- Non-vault session (no `wiki/hot.md` present)

**Symptom chain**
1. New session starts → `SessionStart:startup` fires → `type: "prompt"` hook errors with `ToolUseContext is required for prompt hooks. This is a bug.`
2. The `hook_non_blocking_error` attachment is recorded into the session's local transcript (8 attachments / ~64 KB total in my repro).
3. User runs `/remote-control` ~8 s after session start. Claude Code attempts to export the session state to the Anthropic backend for remote-control session creation.
4. Backend stalls on the dirty state. Internal timeout fires after **27.8 s** with `Remote Control failed to connect: Session creation failed`.
5. Retrying the same `/remote-contro...

Bumping — bug persists on claude-obsidian v1.6.0 (just released). `hooks/hooks.json` in 1.6.0 still ships the same `type: "prompt"` hook in `SessionStart:startup|resume` and `PostCompact`, so the `Failed to run: ToolUseContext is required for prompt hooks` banner still fires on every session start. PR #13 looks good and would close this — any chance of a review/merge?

I created an alternative installer fixing some of these issues.
1. It sets up a blank folder as a new vault
2. takes this repo as base but wipes the `wiki/`
3. creates the necessary symlinks
4. sets up the vault as per `bin/setup-vault.sh`

Shared here:
https://gist.github.com/tilusnet/2a6113adb4302b6cdbe7501c82bb3229

re symlinking:
`skills` is superseeding `commands`, so probably only `skills/`, `agents/`, `hooks/` need symlinked, without `command/`.

otherwise you'll get doubled slash commands for eg. `/wiki`

which PR fixes this @vvlisn ?

> Fixed. `bin/setup-vault.sh` now creates symlinks from `.claude/` to the original directories (`skills/`, `commands/`, `agents/`, `hooks/`). Claude Code discovers project-level skills via `.claude/skills/`, plugin mode uses `skills/` directly. Both install methods work without manual copying.

`mkdir -p .claude && ln -s ../skills ../agents ../hooks ../commands .claude`

Confirming from another Claude Code user — hit this exact error today on v2.1.108 with claude-obsidian v1.4.3. Thanks for the thorough writeup.

One technical clarification on the proposed fix: plain `command` hook stdout (e.g. `cat wiki/hot.md`) prints to the terminal transcript but is **not** injected into the model's context. Context injection from a non-tool event requires the hook to emit JSON on stdout:

```json
{
"hookSpecificOutput": {
"hookEventName": "SessionStart",
"additionalContext": ""
}
}
```

Claude Code reads `additionalContext` and feeds it to the model. This is the correct non-tool-event equivalent of the removed `prompt` hook, and matches the schema field `HookJSONOutput.hookSpecificOutput.additionalContext`.

Minimal command-hook implementation that works correctly (tested locally):

```bash
#!/bin/bash
EVENT="${1:-SessionStart}"
HOT="$PWD/wiki/hot.md"
cat >/dev/null 2>&1 || true # drain stdin
[ -f "$HOT" ] || exit 0
jq -n --arg evt ...