Skip to main content

English | 中文

Vestigraph

Vestigraph is local file and layout history for KLayout users. It stores versions on the user's machine, shows a browser timeline, previews GDS/OASIS content, imports older files, and exports saved versions for recovery.

Vestigraph requires Python 3.10 or newer, KLayout desktop 0.30.x, klayout-klink>=0.6.0,<0.7, and the vestigraph-scan-core scanner package. The normal installation resolves Klink and the scanner as dependencies. Install the Klink KLayout plugin with the Klink command, restart MCP so Vestigraph registers its local companion for the active Python environment, then restart KLayout and open HIST.

What it does

  • Saves file checkpoints and history data in local user storage.
  • Runs a loopback-only browser service for browsing, naming, importing, and exporting history.
  • Previews GDS/OASIS versions with the Python klayout package.
  • Uses Klink's KLayout plugin and companion-service path to record saved GDS/OASIS documents automatically.
  • Exposes local history and skill-refinement tools through the existing Klink MCP extension registry.
  • Keeps history, evidence, drafts, revisions, exports, login links, and control files on the user's machine.

Vestigraph does not provide cloud sync, remote collaboration, hosted storage, a model service, or automatic chat-client configuration.

Install

Vestigraph 0.2.3 is available on PyPI.

python -m pip install vestigraph
klink plugin install
# restart the MCP client that runs klink-mcp
# restart KLayout, open a saved GDS/OASIS layout, then click HIST
python -m vestigraph doctor --integration

pip install vestigraph installs the compatible klayout-klink and vestigraph-scan-core dependencies. Rust scanning is selected automatically when the native module is available; if it cannot be imported, Vestigraph falls back to the Python scanner with a diagnostic reason. Supported Linux, macOS, and Windows wheel platforms do not need a local Rust toolchain.

klink plugin install installs or upgrades the KLayout plugin. Restarting the MCP client lets the existing Klink MCP server discover Vestigraph and register the local companion for that Python environment. No separate MCP server or vestigraph setup step is needed. Installing Python packages does not configure a chat client.

After KLayout restarts, open a saved GDS/OASIS layout and click HIST to open the local history web UI. Confirm that recording is active before editing.

Checkpoints and restore

Vestigraph groups one continuous AI drawing operation into one checkpoint instead of recording every shape separately. Before an AI mutation, pending manual KLayout changes are saved as their own checkpoint. Checkpoint summaries include save and observed modification times, the recorded reason, coverage, and restore provenance.

The agent history tool returns the 30 most recent summaries by default. It retrieves the complete checkpoint list only when the user explicitly asks for all of it; use HIST for detailed events and comparisons.

After the user explicitly selects a checkpoint, vestigraph.restore restores it into the active saved KLayout document. Restore is additive: it appends a new checkpoint with restore_of and the user's reason, and does not delete any earlier or later history. Pending editor changes are checkpointed first. See Recovery and data locations.

Upgrade

Stop the old Vestigraph service if one is running. Upgrade packages, upgrade the Klink plugin, then restart MCP and KLayout:

python -m pip install --upgrade "vestigraph>=0.2,<0.3"
klink plugin install
python -m vestigraph doctor --integration

The underlying storage CLI can still save and export local file versions, but it is not the main product installation path. Full KLayout history, HIST, and local agent tools require Klink.

Local skills and agents

Skill refinement is experimental and disabled by default. When enabled, users can select a history range, save a request, freeze evidence, let a chosen local agent submit a draft, review validation feedback, save revisions, and export files. The package does not include private skills and does not call a model by itself.

After installation and MCP restart, use the existing Klink MCP server:

{"tool":"klink.find_tools","arguments":{"domain":"vestigraph"}}

Then call vestigraph.guide and follow next_action. See Local agents and skills.

Documentation

Vestigraph is Apache-2.0. See Security and local access, third-party notices, and changelog.

Metadata

Release files for vestigraph 0.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vestigraph 0.2.3
File Size Uploaded Provenance
vestigraph-0.2.3.tar.gz 445.5 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for vestigraph 0.2.3
File Interpreter ABI Platform
vestigraph-0.2.3-py3-none-any.whl Python 3 none any Details

Total release size: 829.7 kB

Release files / vestigraph-0.2.3.tar.gz

Download URL vestigraph-0.2.3.tar.gz
Size 445.5 kB
Tags Source
SHA-256 checksum
How to use checksums
b23a5ce11097f8f4e35e1f2eae56b86a26c05684ebc1497c5e663f211ac13dff
BLAKE2b-256 checksum
How to use checksums
0db938f12f11eeaa134b24a43b39cce4851ccc430b2d589f82d07aafa6e3c37c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

Release files / vestigraph-0.2.3-py3-none-any.whl

Download URL vestigraph-0.2.3-py3-none-any.whl
Size 384.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c714265ef3edb2b73ed197bb713d48eea5a5f972ffe2ca06e43ccf108043a6cd
BLAKE2b-256 checksum
How to use checksums
e40f9617654bf0698951fce5ea2cfb91b4a5c214c0039ab4b1687ec67f2df657
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

Security for vestigraph 0.2.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for vestigraph-0.2.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page