Published 13 September 2026 · Source dated 10 September 2026
Figma's community-maintained Penpot Exporter plugin shipped two updates this month: safer handling of corrupted grid data and a new per-page export scope. Small fix, but it matters if you move files between Figma and Penpot.
The Penpot Exporter plugin for Figma pushed Version 51 (Sept 8) and Version 52 (Sept 10). Version 51 stops exports aborting when a file has corrupted grid track data, and falls back to a default font instead of erroring on unresolved font families. Version 52 adds a 'choose pages' export scope, so you can grab one screen instead of dumping an entire file into Penpot.
If you're testing Penpot as a Figma alternative, or just want a portable backup of your work outside Figma's ecosystem, this plugin is worth having installed. It's not exciting, but reliable file portability is the unglamorous infrastructure that makes multi-tool workflows actually work day to day.
Coach
install the Penpot Exporter plugin and export one small Figma file into Penpot this week — see what breaks before you need it to work.
A September 2026 roundup shows AI agent tools narrowing in on single business tasks — procurement, invoicing, logistics — rather than acting as general chatbots. None of it is design-tool specific yet, but the same narrow-agent pattern is what design tools are chasing too.
pick one repetitive task in your workflow (renaming layers, writing alt text, chasing feedback) and see if a narrow AI agent — not a general chatbot — can take a first pass at it this week.
A new coding-agent platform lets you run dozens of AI agents in parallel from one dashboard. It's dev-focused today, but it's a live example of where design-to-dev handoff tooling could head next.
Skim how the '/workflows control room' concept works, then name one repetitive handoff step in your own process (spec writing, redlines) you'd want an agent to own first.
Figma now ships a design agent that works directly on the canvas, plus an MCP server that lets AI tools read your actual file data instead of screenshots. This is a real product shift, not just a demo.
open one messy Figma file, rename your layers and components properly, then try Figma's MCP server (or a Penpot plugin) with an AI tool to see what it actually reads.
