safishamsiandClaude Opus 4.8
8595749021
Completes #3742: the Step 1 fix closed the .graphify_root shell line, but the progressive-disclosure add-watch reference still passed the raw, agent-substituted INPUT_PATH placeholder unquoted into a bash command ($(cat .graphify_python) -m graphify.watch INPUT_PATH), the same injection class - a scan root like $(...) / ; rm ... would execute. The watcher targets the folder graphify already extracted, so read the trusted graphify-out/.graphify_root that Step 1 resolves (the same sidecar pattern this reference already uses for .graphify_python) instead of re-substituting the untrusted placeholder. Regenerated all 14 host add-watch artifacts + expected/ snapshots; monolith-roundtrip and always-on-roundtrip stay green (cores untouched). The identical sink in the aider/devin monolith cores is tracked separately (editing a core requires a gen.py sanctioned-diff). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2.6 KiB
graphify reference: add a URL and watch a folder
Load this when the user ran /graphify add <url> or passed --watch. Neither is part of the default build.
For /graphify add
Fetch a URL and add it to the corpus, then update the graph.
$(cat graphify-out/.graphify_python) -c "
import sys
from graphify.ingest import ingest
from pathlib import Path
try:
out = ingest('URL', Path('./raw'), author='AUTHOR', contributor='CONTRIBUTOR')
print(f'Saved to {out}')
except ValueError as e:
print(f'error: {e}', file=sys.stderr)
sys.exit(1)
except RuntimeError as e:
print(f'error: {e}', file=sys.stderr)
sys.exit(1)
"
Replace URL with the actual URL, AUTHOR with the user's name if provided, CONTRIBUTOR likewise. If the command exits with an error, tell the user what went wrong - do not silently continue. After a successful save, automatically run the --update pipeline on ./raw to merge the new file into the existing graph.
Supported URL types (auto-detected):
- YouTube / any video URL → audio downloaded via yt-dlp, transcribed to
.txton next run (requirespip install 'graphifyy[video]') - Twitter/X → fetched via oEmbed, saved as
.mdwith tweet text and author - arXiv → abstract + metadata saved as
.md - PDF → downloaded as
.pdf - Images (.png/.jpg/.webp) → downloaded, Claude vision extracts on next run
- Any webpage → converted to markdown via html2text
For --watch
Start a background watcher that monitors a folder and auto-updates the graph when files change.
$(cat graphify-out/.graphify_python) -m graphify.watch "$(cat graphify-out/.graphify_root)" --debounce 3
This watches the same folder graphify extracted, read from the trusted graphify-out/.graphify_root that Step 1 resolved - there is no path to substitute, so a scan root containing shell metacharacters can never be re-interpreted here. Behavior depends on what changed:
- Code files only (.py, .ts, .go, etc.): re-runs AST extraction + rebuild + cluster immediately, no LLM needed.
graph.jsonandGRAPH_REPORT.mdare updated automatically. - Docs, papers, or images: writes a
graphify-out/needs_updateflag and prints a notification to run/graphify --update(LLM semantic re-extraction required).
Debounce (default 3s): waits until file activity stops before triggering, so a wave of parallel agent writes doesn't trigger a rebuild per file.
Press Ctrl+C to stop.
For agentic workflows: run --watch in a background terminal. Code changes from agent waves are picked up automatically between waves. If agents are also writing docs or notes, you'll need a manual /graphify --update after those waves.