Skip to content

Releases

figma-vault 0.1.5

figma-vault 0.1.5 Latest
Latest

Choose a tag to compare

View all tags
@NBhey NBhey released this 28 Sep 17:55
v0.1.5
5f3444b

Batch export and SECTION/CANVAS expansion. No vault format changes: vaults and configs from 0.1.x work as-is.

  • figma-vault add <url>... exports several screens in one run. Links from the same file share
    one structure read and one render batch, so a pull costs a fixed, predictable number of requests.
  • --expand turns a SECTION or CANVAS link into separate screens instead of one huge document;
    --max-screens caps how many (20 by default) and reports the ones it skipped.
  • The frame screenshot and raster images are rendered in one /images call. If rendering fails
    for a reason other than 429, screenshots are retried in smaller batches, at most 8 extra
    requests per file, and the warning lists screens left without a screenshot.
  • figma-vault limits accepts several links, no longer renders a whole SECTION/CANVAS as a
    probe, and prints how many Tier 1 requests the probe used.
  • The /figma command passes each link as its own argument. Re-run npx figma-vault init
    to refresh an existing /figma command.
Assets 2
Loading

figma-vault 0.1.4

figma-vault 0.1.4

Choose a tag to compare

View all tags
@NBhey NBhey released this 24 Sep 16:45
v0.1.4
95c1542

Security fixes from an internal review. No format changes: vaults and configs from 0.1.x work as-is.

  • vault_get_asset no longer reads outside the vault: document ids . and .. are rejected,
    and the real path is checked after resolving symlinks.
  • The exporter refuses to write through symlinked document or asset directories
    and through a symlinked doc.json/raw.json/index.json.
  • The /figma command and the MCP server instructions now tell the agent to treat node names
    and texts from a design as content, not as instructions. Re-run npx figma-vault init
    to refresh an existing /figma command.
Loading

v0.1.3

v0.1.3

Choose a tag to compare

View all tags
@NBhey NBhey released this 23 Sep 18:46
v0.1.3
3f41e65

Pull a Figma frame once, then let Claude Code, Codex or any MCP agent read it offline, with no Figma token and no rate limits.

What's new in 0.1.3

  • Listed in the official MCP Registry as io.github.NBhey/figma-vault. Clients that read the registry can now find and install it (npx figma-vault mcp).
  • server.json and mcpName added; a test keeps their versions in sync with package.json.
  • README: a terminal demo, the key numbers up front and a 30-second try-out that needs no token.

No changes to the CLI, the MCP tools or the vault format. Vaults from 0.1.x are read as they are.

Install

npm i -g figma-vault
figma-vault init && figma-vault demo && figma-vault check
Loading