Download Latest Version v0.7.10 source code.tar.gz (563.6 kB)
Email in envelope

Get an email when there's a new version of graphify

Home / v0.7.6
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2026-05-05 2.0 kB
v0.7.6 source code.tar.gz 2026-05-05 523.9 kB
v0.7.6 source code.zip 2026-05-05 638.6 kB
Totals: 3 Items   1.2 MB 4

Bug Fixes

  • cluster-only --graph flag (#724) — graphify cluster-only now accepts --graph <path> to specify a non-default graph.json location; positional path and flags can appear in any order
  • _is_sensitive() false positives (#718) — word boundaries on the keyword pattern prevent legitimate source files like tokenizer.py, password_verification.py, SecretManager.java from being silently dropped
  • max_tokens truncation cascade (#730) — headless graphify extract --backend claude/kimi now defaults to 16384 output tokens (was 8192), eliminating the recursive split cascade on dense doc corpora; override with GRAPHIFY_MAX_OUTPUT_TOKENS env var
  • Prune message clarity (#539) — --update now clearly distinguishes "N nodes pruned from M deleted files" from "M deletions detected but graph already clean"
  • Svelte stub node source_file (#712) — stub nodes created for imported .svelte files now carry the resolved import path as source_file instead of the importer's path
  • Svelte static imports (#713) — extract_svelte() now catches static import X from './foo.svelte' via a dedicated regex pass over <script> block content; previously tree-sitter's JS parser silently dropped all static imports
  • Manifest on full rebuild (#538) — graphify extract (full rebuild path) now saves manifest.json on every successful run; previously only --update saved it, causing stale-manifest drift
  • Antigravity install paths (#704) — graphify antigravity install now writes to .agent/ (no trailing s) matching Antigravity's actual config paths
  • Pi skill YAML parse error (#737) — Pi skill frontmatter description simplified to avoid "nested mappings" error on Pi startup
  • --dedup-llm wiring — flag now correctly threads LLM backend through to deduplicate_entities in both fresh and incremental extract paths; fresh extract path now also runs dedup (previously bypassed it entirely)
Source: README.md, updated 2026-05-05