Skip to content

PolyCodeGraph v0.7.0 — Ten semantic intents for AI coding agents

Choose a tag to compare

@RolandDumit RolandDumit released this 02 Oct 17:24
· 32 commits to main since this release

PolyCodeGraph 0.7.0 adds ten semantic context intents across Dart/Flutter, TypeScript, JavaScript, Java, Go, Python, Rust, Swift, Objective-C and Kotlin.

  • inspect_change now supports rename, change_signature, find_tests, review_change, explain_symbol, trace_flow, move_symbol, remove_symbol, replace_dependency and extract_symbol.
  • Shared evidence tables, merged source windows, bounded budgets and opaque cursors collect context from one coherent generation. Existing calls without an intent preserve the 0.6 contract and stable IDs.
  • Explicit review baselines compare source hashes, symbols, relations and diagnostics. Body-only changes retain conservative file/consumer context; baselines and cursors have bounded session lifetimes.
  • Compiler-backed AST bindings and control events provide extraction constraints across all ten providers. These remain partial: no generated patch/signature, complete dataflow, runtime dispatch proof or correctness approval.

Native downloads

Rust is not required to run the four native packages. Keep the executable beside providers/; selected semantic providers still require their documented runtimes/SDKs. Packages include compiled Dart/Go workers. Verify the attached archives using SHA256SUMS.

Platform Archive
Linux x64 polycodegraph-0.7.0-linux-x64.tar.gz
Windows x64 polycodegraph-0.7.0-windows-x64.zip
macOS Intel polycodegraph-0.7.0-macos-x64.tar.gz
macOS Apple Silicon polycodegraph-0.7.0-macos-arm64.tar.gz

Upgrade

Replace the executable and matching providers, prepare selected adapters with setup --languages ..., and restart MCP. Updating only the core while keeping old adapter assets can leave intent capabilities unavailable. Public symbol IDs, primitive APIs, graph configuration, SQLite schema and watcher behavior remain compatible. Compact primitive responses remain opt-in; intent budgets are independent of the profile.

Read the intent API and language capability matrix, migration guide and consumer harness template. Follow pertinent pages and omitted snippets; explicitly reconcile before sensitive changes.

Validation and measured limits

Local Linux checks passed: formatting, Clippy, 52 Rust tests, Dart analysis/provider tests, native MCP for ten intents across ten languages, primitive differential checks against 0.6, real Flutter, Android SDK and relocated packages. Local cached Dart test tooling differed from the committed lock; exact locked versions are checked in host CI.

All 20 cross-platform CI jobs passed, including Linux/macOS/Windows core checks, ten-intent provider fixtures, exact locked Dart tests, Flutter, Android SDK, macOS UIKit and relocated-package checks for all four targets. Validated release commit and CI run.

The deterministic Flutter rename replay collects equivalent evidence in 3 calls instead of 13, with 41.81% fewer result characters/UTF-8 bytes and all 19 resolved reference edges retained. It includes both pages and one explicit DTO expansion. Tool schema size increases by 4,942 characters; startup calls are counted separately. Warm scan/extraction/graph-build deltas are zero. These are response measurements, not measured AI token/quota savings or total-task speedups. No new AI executor runs were performed.

See the aggregate replay and validation report. Static/dynamic and cross-language limitations remain; extraction, test discovery and hypothetical signature compatibility are qualified by the provider evidence.