mirror of
https://github.com/runbear-io/beardrive.git
synced 2026-08-25 08:08:08 +02:00
Snow LeeandClaude Fable 5
476113ebdc
Field report: an agent session read a dozen-plus files via Bash (grep/cat/tail/find) and Grep, but read heat showed almost nothing — the read-log hook only matched the native Read tool. - matchers broadened per platform: claude Read|Grep|Bash, codex read_file|shell, gemini +search_file_content|run_shell_command, hermes read_file|grep|bash; plugin hooks.json matches Read|Grep|Bash - read-log is now tool-aware: shell events mine the command line for existing files it names (redirect targets and flags excluded), grep events mine the response for the files the matches came from (content lines and filename lists), and listing tools (Glob, ls) are deliberately ignored — seeing a file's name is not reading it - hooks install upgrades a registered hook's stale matcher in place, so re-running it after a binary upgrade rolls coverage out to existing projects instead of being skipped by the idempotency marker - docs: SKILL.md platform table + read-heat wording, install/init commands, README command table Note from the same report, verified not a bug: read-log resolves the mount via the folder's own .bdrive/config.json (config.ResolveMount), so a stale duplicate registry entry cannot swallow reads. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P5cxPQdSGJnjXCYY9GeWXt
12 lines
561 B
Bash
Executable File
12 lines
561 B
Bash
Executable File
#!/bin/sh
|
|
# Queue agent file reads for the hub's read heatmap: Read tool calls, the
|
|
# files Grep matches came from, and the files a Bash command names.
|
|
# `bdrive read-log` parses the hook's stdin JSON itself and only appends to
|
|
# a local spool (drained on the next sync) — no network, no locking, so this
|
|
# is safe to run on every matched tool call in every project. Fast no-op
|
|
# outside beardrive projects.
|
|
cd "${CLAUDE_PROJECT_DIR:-.}" || exit 0
|
|
[ -d .bdrive ] || exit 0
|
|
command -v bdrive >/dev/null 2>&1 || exit 0
|
|
bdrive read-log . >/dev/null 2>&1 || true
|