Product updates ✨

We're happy to introduce the Developer CLI v2.0, which is a major update to our developer handoff solution.

‍

Until now, push only created new keys, so code edits had to be copied into Frontitude by hand. Teams with monorepos or a non-default i18n library also had to script around the CLI. Version 2.0 fixes all three.

‍

✨ What's new

• Update existing keys on push: frontitude push --update sends content and key edits to Frontitude, so devs can finally push updates to Frontitude from code!
• Monorepo support with config files per package, page, or component: Use separate configs per package, page, or component in the same repo. Add {prefix} to filePath to route keys to matching files, such as Checkout.heading → Checkout.json.
• Your variable and plural format: The CLI now supports any variable format your client side library needs. Use variableFormat and pluralFormat to let the CLI know your custom format. Both pull and push use them.

‍

⚠️ What's different in v2.0

• Lock files: Pull and push commands keep a lock file next to each strings file to spot content and key changes correctly and handle conflicts robustly.
• Apple translation files: When the source isn't in a .lproj folder, translations now go to <locale>.lproj/ next to it, not to the disk root.
• Apple placeholders are kept: Pull keeps your %d, %ld and %1$@ and no longer writes %@ for every variable.
• Safer pull: A broken strings file, or an Android XML element the CLI can't manage, stops the pull before anything is written.
• Shorter errors: Errors are now in the format of CODE: message.

‍

🐞 Bug fixes

• Android XML: Pull no longer escapes the same strings again on every run.
• Plural export: The plain form of a plural is no longer exported as key_, which used to create an extra component on push.
• Reordered variables: Numbered placeholders in translations now follow the source order on Apple and Android.

‍

🎥 New demo video

We decided to celebrate the new major version with a demo video that walks you through the main flows you can build with the new CLI.

‍

‍

‍

Update to CLI v2.0 with npm install -g @frontitude/cli or share the Developer Docs with your developers.

Duplicate components can pile up, especially when components are created automatically. Now Frontitude finds the duplicates for you, and you can merge them in a few clicks.

‍

🔀 Merge components

• Merge up to 10 components at once: Select two or more components in the library and click Merge. Then pick the one to keep. Its text, translations, key and details stay exactly as they are.
• Nothing is left behind: Every instance of the other components moves to the one you keep, and so do their comment threads. Then the other components are deleted.
• See the impact before you confirm: You can view each component's instances on their designs. You also see which instances will change text, and which unique keys developers will lose.
• A record of every merge: The merge is saved in the kept component's history.

‍

‍

🔎 Find duplicates automatically

• Duplicates in the Suggestions tab: The library's Suggestions tab now lists groups of components with exactly the same text and variables, with the biggest groups first.
• Review and merge in one click: Each group opens the merge dialog, and the best component is already picked.

‍

‍

💪 Use it to:

• Clean up a library that grew with auto-created components
• Keep translations in one place, not spread across copies

‍

🤖 Also, Frontitude is now an official Claude connector!

• Find it in Claude's directory: Frontitude's MCP server is now listed in Claude's connector directory.
• Work with your library from Claude: Ask Claude to find, write and update texts and components in Frontitude. Claude can reach only what you can reach in Frontitude, and changes are saved under your name.

‍

🐞 Bug fix

• Plural components are listed once: Expanding a category in the library sometimes showed a component once for each plural form. Each component now shows once.

Large libraries are hard to keep track of, and attaching text to the right component shouldn't be time-consuming. This update makes both easier, and adds a few more improvements.

‍

📚 Library activity feed

Have a clear overview of changes in your library, with who did what and when, so you can follow up on edits without digging through each component. The feed is available to enterprise customers on the Organization plan.

‍

‍

Use it to:

• See who changed a component and when
• Follow up on edits made by your team
• Spot unexpected changes before they ship

‍

🔗 Auto-attach improvements

• Smarter auto-attach: Auto-attach now looks at translation status when it chooses between matching components, so text is less likely to land on the wrong component.
• Flags in the attach box: Components in the attach box are labeled with flags showing the languages they're translated into, so you can find the right one faster.‍
• Review auto-attach matches by email: If auto-attach matches text to more than one component, the person who started it gets an email, so they can review the matches and change components further if needed. You can opt out of these emails at any time.

‍

‍

Use these to:

• Find the correct component to attach faster
• Catch wrong matches as soon as they happen

‍

🛠️ Improvements and fixes

• Translation status in library search: Filter the library by translation status to find components that are missing a language or are ready to ship.
• Security fixes: We also made several security and stability fixes across the platform.

‍

This update is for teams that rely heavily on AI tools (Claude, ChatGPT, and others) and want them working with Frontitude to produce high-quality copy in a fraction of the time.

‍

Until today, giving an AI agent access to your copy library meant manually exporting a file, pasting text into a prompt, or building something custom.

‍

‍Frontitude MCP closes that loop: connect any MCP-compatible AI tool directly to your Frontitude workspace, so it can read and write content and metadata.

‍

‍

‍

‍

✨ What's inside

• More than 30 tools, available the moment you connect: search your copy library by meaning, read character limits, variables, plurals, status, translation coverage and revision history, and see everywhere a component is used.
• Write access, not just read: create components and categories, update values in any language, attach and detach texts, set status, manage tags and variables, and leave comments — all from the agent.
• Every connection tracked by person: a connection carries the access of whoever made it, and every change it makes is recorded under their name.

‍

💪 Use it to

• Check whether a string already exists — and what status it's in
• Ask what isn't Final yet, before you ship
• Find what's missing in translation, and what won't fit
• Put a flow up for review without exporting anything
• And many more!

‍

This feature is now available on all Frontitude workspaces, at no additional cost.

‍

Set up your MCP integration from your workspace's AI settings page, or see the docs to get more details.

This update is about control and clarity: a redesigned settings page, a single switch that governs every AI feature in your workspace, a proper way to give people view-only access, and a set of import and performance fixes.

‍

🧭 Settings, redesigned

Settings had grown into a row of tabs where personal preferences and workspace-wide configuration sat side by side, with no way to tell which was which.

‍

• A left-hand nav: Every page is one click away instead of hidden behind a tab strip.
• Your settings, split from your workspace's: The nav is grouped into You and Workspace, so it's clear what affects everyone.

‍

‍

‍

🤖 One switch for AI

AI features were scattered across settings, so there was no single place to see what was on or to turn everything off. AI now has its own page, with a master switch above it.

‍

• AI in this workspace: One switch that governs every AI feature. Turn it off and AI translation stops drafting and metadata is no longer generated.
• Each feature keeps its own setting: Turning AI back on restores exactly what was on before - you don't have to reconfigure anything.

‍

‍

👥 Invite project viewers by email

If you share projects with stakeholders, clients, or reviewers who only need to read them, view-only access has meant sending a shareable link - and anyone who receives that link can open the project.

‍

You can now invite project viewers by email, the same way you invite project editors.

‍

• Invited viewers appear in settings: Accepted invitations show up on the Account page alongside everyone else.
• Know before someone hits the wall: Workspace admins on paid plans now get an email when the last viewer seat is taken, rather than finding out when a collaborator can't be invited.

‍

‍

‍

📥 Import a CSV without a unique key

A unique key has always been optional when you create a copy component by hand, but the file import required one on every row - so a file without them imported nothing and reported itself as empty.

‍

Rows without a unique key now import fine, and the Unique key column doesn't have to be in the file at all. Keys you do provide still have to be unique.

‍

‍

⚡ Performance and stability

• Faster filtering in large projects: The project view's filters are now answered by the server and not in the browser.
• Search handles long queries: Pasting a long string - a Figma layer path in front of a sentence, for example - used to fail the search outright. It now returns a clear message naming the limit.

‍

‍

🐞 Bug fix

• Plural columns on CSV round trips: Exporting a pluralized component and importing the file back dropped its plural forms. The plural columns now land on the component, so an export survives the round trip.

We rebuilt the Figma plugin from the ground up, added a way to bring back any earlier version of your copy, and made it quicker to work through frames in bulk.

‍

⚡ A rebuilt Figma plugin

The plugin has been rewritten end to end on a modern stack. What you'll notice:

• Faster to open: Boot fires its requests in parallel instead of one after another, and the panel paints without waiting on work it doesn't need yet.
• Faster Changes refresh: Far fewer round trips to Figma when checking a file for changes.
• A roomier panel: Wider and taller, so the change log, tags and dropdowns have room to breathe.

‍

‍

↩️ Restore a previous version

Until now, looking at an older version in the change log was as far as you could go. Now any entry can be made current again, from the web app or the Figma plugin.

‍

Click Restore on a change-log entry and the confirmation shows whose version you're restoring, how many instances it will update, and a diff against the current text. It's safe: restoring adds to the history rather than rewriting it, so the current version stays in the log. Available to Editors.

‍

‍

💪 Use it to:

• Undo a change that went out to every instance of a component
• Bring back wording a round of edits talked you out of
• Recover a text someone overwrote by mistake

‍

🖼️ Multi-select for frames in Design View

Working through a project one frame at a time added up, especially in larger design files. You can now select multiple frames in Design View and act on them together.

‍

• Select as you go: Click a thumbnail to add it to the selection, or press Cmd/Ctrl+A to select every frame on the page.
• Delete a batch at once: Remove the frames you no longer need in a single action. Deleting more than ten asks you to type the count first, and any page left empty is cleared up for you.

‍

Deleted frames take their texts and history with them - your copy components stay in the library.

‍

‍

✏️ Editing improvements

• Discard unsaved changes: A rollback button in the text edit box puts the saved value back - text, plurals and variables - leaving your note and status alone.
• See where a component lives: The edit panel and the plugin's edit tab now show a component's full category path.
• Plugin polish: The insert-variable dropdown no longer closes on the click that opened it, tags can be removed in one click, and the change log rows and nav bar spacing are evened out.

‍

‍

🐞 Bug fix

• Design-hidden texts no longer show up in the plugin's edit tab when several texts are selected.

We've shipped a set of fixes and improvements to make Frontitude more reliable day to day - from importing content and syncing with Figma to managing project access and running the CLI in your pipeline. Here's what's new:

‍

⚡ Performance and stability

This quarter we went into making Frontitude hold up under heavy use, especially in large workspaces.

• Faster project loading: We optimised the queries behind loading project content and parent-component lookups that were the slowest part of opening a large project.
• More reliable service in large workspaces: Work aimed at the errors that could appear in content-heavy workspaces at peak use, including a restructured content export path.

‍

🎨 Figma plugin

• Fixed an issue that caused the plugin to slow down in large and complex design files.
• Fixed an issue where some frames in Figma sections failed to sync.

‍

📚 Copy library and imports

• Fixed a bug that caused copy components to be created in the wrong workspace when working across multiple workspaces.
• Fixed a bug that caused tags to be created in the wrong workspace from the Search tab.

‍

🔐 Project access

• Fixed an issue where project permissions weren't applied correctly when opening a project from the Search tab.

‍

🛠️ Developer CLI improvements

🚨 Clear, actionable errors

The CLI now returns structured errors: a stable error code alongside a readable message, so your pipeline can branch on the actual cause instead of parsing generic output. Long-running calls also return a clear timeout error rather than an opaque failure. This is opt-in behind a flag, so existing setups are unaffected.

‍

🔒 Reliability and security improvements

A set of hardening changes across CLI commands, with better internal visibility into CLI health so we can catch issues sooner.

This week's update has something for everyone: a new workflow for teams managing external collaborators, and a set of meaningful improvements for developers using the CLI.

‍

📂 Folder-level collaborator access

If you collaborate with external clients, agencies, or contractors in Frontitude, you've had to invite them project by project, even when all those projects live in the same folder.

‍

You can now invite a collaborator directly from a folder's options menu, and they'll automatically get access to every project inside it, current ones and any added in the future.

‍

• Invite from the folder menu: Open the "..." menu on any folder → "Share…" → enter emails and choose Editor or Viewer.
• Collaborators get auto-access for new projects: Projects added to the folder are automatically covered — no need to re-invite.
• Access revokes on move: If a project is moved out of the folder, the collaborator loses access to it immediately.

‍

‍

‍

🛠️ Developer CLI improvements

These updates are landing together in CLI v1.5.0:

‍

📦 Monorepo support: new --config flag

Until now, the CLI has only read frontituderc.json from the current working directory. For teams managing multiple packages in a monorepo, that meant a separate install per package and a cd before every command.

‍

The new --config flag lets you point any command to a specific config file by path, so a single install at the repo root can drive every package.

‍

frontitude pull --config packages/web/frontituderc.json

‍

• Works on every command: init, login, pull, push, config, source
• Accepts absolute or relative paths
• One CLI install in root devDependencies instead of one per package

‍

Read more on this new feature here.

‍

📋 Richer metadata with --include-metadata

The --include-metadata flag on the pull command now includes a fuller set of design hierarchy identifiers, giving developers more context alongside each string:

• Frontitude Project, Page, and Screen IDs
• Figma File, Page, Frame, and Text Node IDs
• Frontitude Parent Component ID

‍

⚡ Faster content exports

Pull times are now up to 95% faster and much more stable in content-heavy scenarios.

‍

🐞 pnpm compatibility fix

Installing @frontitude/cli via pnpm caused every command to fail silently. This is fixed in v1.5.0.

‍

Update to v1.5.0 with npm install -g @frontitude/cli or share the Developer Docs with your team.

‍

⚙️ Under the hood

The component instances panel now loads around 65% faster for components with many instances. We also shipped a set of stability improvements that some workspaces were experiencing.

This update is for teams where developers are moving fast, building interfaces with AI, and need an easy way to bring new copy back into Frontitude for writers and designers to review.

‍

Until today, the Developer CLI only went one way - pull copy from Frontitude into your codebase.

‍

‍frontitude push closes the loop: upload new copy directly from your codebase into your Frontitude library as copy components, ready for writers and designers to work on straight away.

‍

✨ What's new

• frontitude push: Upload new copy keys from your source files to Frontitude in one command
• Dry-run mode: Run --dry-run to preview exactly what would be created before anything is written to Frontitude
• Format support: Works with JSON, iOS .strings, Android XML, and XLIFF 1.2/2.0 files
• CI-friendly: Pass --non-interactive to skip confirmation prompts in automated pipelines

‍

💪 Use it to

• Get new components into Frontitude the moment developers add them to code with no manual handoff
• Let writers start on copy while developers are still building
• Onboard your first content into Frontitude straight from your codebase
• Automate content sync as part of your CI pipeline

‍

Available in Developer CLI version 1.3.0. Update with npm install -g @frontitude/cli.

‍

Share the new command's documentation with your developers so they can start bringing new copy to Frontitude straight from their codebase.

Variables let developers embed dynamic content into strings at runtime - statuses, counts, or any other backend data.

‍

For writers and designers, variables mean you can preview realistic copy while designing, without waiting for real data.

‍

For example: a string like {assignee} marked {task} as complete shows up with mock, realistic values as Alice marked Onboarding as complete — readable, reviewable, and ready for handoff.

‍

✨ What's new

• Per-instance placeholder overrides: Set different placeholder values per project instance, so each screen reflects its context. Changes stay local and persist through Figma re-syncs.
• Improved variable management: All workspace variables and placeholders now live in Settings → Data Management, making it easier to add, update, and keep naming consistent across teams.

‍

‍

🛠️ UX improvements

We shipped a number of small but meaningful UX improvements across the web app and Figma plugin. These don't always make the headlines, but they add up to a noticeably smoother day-to-day work with Frontitude!

‍

📚 Learn more

See the full Variables guide for setup instructions and best practices.

Tags help you organize and find components in your library, but adding them used to mean switching contexts at the wrong moment.

‍

⬇️ Tag imported components

When bringing content into the library from a file, you can now tag components as part of the import. Use it to mark a batch for review, group components by feature or release, or make a set easy to roll back if something goes wrong.

‍

‍

✏️ Tag copy components from projects

You can now tag a component directly from the project view, without navigating to the library. Use it to flag work-in-progress components, assign ownership by team or feature, or keep your library organized as you edit.

Design content often have strict character constraints - a button label that can't exceed 20 characters, a notification that needs to fit a single line.

‍

For multilingual products, this matters even more: translated strings can expand significantly, and a limit that works in English may break the layout in German or French.

‍

‍

You can now set a character limit directly in the text edit box from Frontitude projects, Figma, or the library. The counter updates in real time, so writers and translators know immediately when they've gone too long, before it becomes a design or dev problem.

‍

Use it to:

• Keep UI labels within design constraints (buttons, tooltips, menu items)
• Prevent translated strings from breaking layouts in other languages
• Catch overruns during writing, not during QA or dev handoff
• Simplify repeated content edits with a strict, documented limit

This month’s updates focus on improving day to day workflows across Frontitude. Hope you like them!

‍

🧑‍💻 Developer experience

• Developers can now connect project folders as a data source in the Developer CLI, so pulling texts automatically includes all projects inside a selected folder without manually managing project lists.
• We published full documentation for the frontituderc.json configuration file, after we received number of requests to document it.

‍

✅ Content reviews

• We now log text approvals in the activity log, so every approval action can be clearly tracked.

‍

📚 Copy library improvements

• You can now update text status and notes directly through CSV import, eliminating manual edits inside the app.
• Frontitude now automatically creates missing categories during CSV import using the forward slash convention in the "Name" column.
• The library's filter bar is now sticky, so filters remain visible while scrolling through components.
• You can now copy a component’s value to the clipboard in one click, making it easier to reuse or share texts.

‍

🎨 Figma plugin enhancements

• Detach is now available directly inside the Figma plugin, aligned with the web app behavior.
• We replaced Figma's plugin notifications with custom toast messages for clearer, more consistent success and error feedback.

Content folks can now kick off automated content reviews directly from Figma, so feedback and approvals move faster with less manual back-and-forth.

‍

Review Mode is great for collaboration, but starting a review can still take time when you need to collect the right strings and loop in the right stakeholders. This update automates that process.

‍

✨ What’s new

• A new Review tab in our Figma plugin, dedicated to starting and managing content reviews.
• Teammates can select text in Figma and click Add to Review to collect content that needs review, then send it and forget it.
• PMs, legal, marketing, and other stakeholders get a clean review experience in the web app, with clear review state tracking so teams know what’s pending and what’s approved.

‍

Automated reviews from Figma are perfect for:

• 🔹 Sharing UX copy with UX writers for quick edits
• 🔹 Sending copy to PMs for fast approvals before shipping
• 🔹 Getting legal and compliance sign-off on sensitive text
• 🔹 Sending copy to clients for review and approval
• 🔹 Handing off strings for localization review or translation post-editing
• 🔹 And a lot more…

‍

‍

‍

📚 Learn more

Learn how to use it in this guide, and try it out to streamline your content review workflow today! ⚡

‍

We’ve shipped a few updates to make exporting and managing content faster, more consistent, and less repetitive across Frontitude and the Figma plugin. Here’s what’s new:

‍

✨ Improvements

• Detach is now available in the Figma plugin, aligning with the web app experience.
• Export project is now available directly from Language View, so you can export without switching views.
• Export options for projects and library are now persisted, so there’s no need to set your preferences on every export.

‍

🐞 Bug fix

• Fixed an issue in the Figma plugin where an irrelevant warning message briefly flashed when submitting a change, even when there was no incoming change.

‍

A big update is coming soon on automating content reviews from Figma. Stay tuned!

We’ve rolled out updates that improve the Frontitude Figma plugin’s speed and stability.

‍

✨ Performance improvement

• Added dynamic page loading, which speeds up plugin load times and reduces memory usage, especially in complex and large Figma files.

‍

🐞 Bug fixes

• Fixed issues where text layer names didn’t update correctly with the copy component status and unique key when attaching or detaching components.

‍

We’ve shipped a new set of updates focused on improving stability, expanding UX Writing Assistant capabilities (in beta), and giving you more control over billing and subscriptions.

‍

🐞 Bug fixes

Android string formatting

• Fixed an issue that caused strings with multiple variables to be formatted incorrectly in Android format.

Writing Assistant Beta

• Fixed a bug where the Rewrite feature ignored custom instructions.

Copy library and copy components

• Fixed a bug that caused plural versions of a copy component to appear as multiple components in the copy library instead of a single grouped component.
• Fixed an issue where AI translation selected the wrong plural form as the main version when auto-translating a copy component.

Projects and collaboration

• Fixed a bug where the Figma file link didn’t show in frame breadcrumbs when viewing a project as a workspace collaborator.

‍

✨ Improvements and new capabilities

UX Writing Assistant Beta

• Added similar copy components from your library to the Rewrite feature, making it easier to reuse existing content and keep copy consistent.

Billing and subscriptions

• Improved billing settings reliability and overall experience.
• Added more self-serve subscription actions, including adding and removing seats and managing other subscription details directly from your account.

‍

We’ve rolled out several updates that make collaboration smoother using Frontitude.

‍

💺 Introducing seat types

You can now assign teammates with specific seat types, giving them access to the Content Management Platform, the UX Writing Assistant, or both. This makes it easier to control access and plan your workspace seats effectively.

‍

Teammates can now also be invited directly from the Settings page with Writing Assistant access only, simplifying onboarding for writers and designers.

‍

🐛 Bug fix

The Activity Log in the component edit panel now loads properly and no longer disappears when the panel opens.

‍

💻 Developer CLI improvements

Developers can now filter project content by page or screen name when using the CLI. This means developers can fetch specific screens instead of the entire project. See documentation here.

‍

🎨 Content Management Figma Plugin

When clicking “Open in Frontitude” from the Figma plugin, you’ll now be taken straight to the selected frame (if one is selected). A small tweak that saves a lot of clicks.

‍

✨ New Writing Assistant (Beta)

We’re introducing a revamped UI and a new audit feature in the Writing Assistant Beta. The experience is smoother, more focused, and designed to make auditing content easier and faster.

‍

Thanks for all beta participants for your amazing feedback! We're excited to build the best writing assistant for UX content together.

‍

We’ve shipped two enhancements to make reviewing and managing component suggestions faster and more flexible:

• Bulk selection in suggestions list - Added Select all/Deselect all to pick the right suggestions quicker.
• "Don’t show again" option - Control whether the component suggestions modal appears after syncing. You can now dismiss it directly in the modal, with the option to re-enable anytime from the settings tab.

We’ve rolled out a set of improvements to boost project performance and make search and translation workflows even more intuitive:

‍

🔍 Case‑sensitive and exact‑match search

Search in projects and in the library now supports case‑sensitive and exact‑match queries.

‍

‍

🔄 Reactive project text and translation stats

Project-level word source text and translation progress now update live, with no need in page refresh. Just make a change, and the stats reflect it instantly.

‍

🚀 Improved project load performance

Projects now load in roughly half the time by loading part of the data asynchronously.

‍

💡 P.S. Beta registration for the new writing assistant with style guide integration is still open! Register here

We’ve rolled out several updates to improve reliability, consistency, and visibility across the platform. Here’s what’s new:

‍

🧠 Frontitude AI Metadata enhancements

• Improved stability when generating metadata in large batches
• Auto-generated unique keys now better align with your existing library keys
• Auto-generated category names are now more readable and consistently formatted

‍

✨ Improvements

• Unique keys are now shown in the Figma plugin to help identify each copy component more easily

‍

🐞 Bug fixes

• Fixed an error in the developer CLI when using the pull command
• Fixed a bug where changing the casing of a unique key would delete the component

‍

💡 P.S. We’ve about to launch a new writing assistant with style guide integration in beta! Register here to join

We’ve just released a new interactive playground file to help you get hands-on with Frontitude’s UX content platform, now available in the Figma Community!

‍

‍

This guided file walks you through key workflows, including:

• Sharing for review – Use Review Mode to easily share content with teammates and stakeholders outside of Figma.
• Building a content library – Learn how to turn UX content into reusable copy components and organize them in a centralized library.
• Localizing your designs – See how to build a design-driven localization workflow and hand off finalized content to translators.

Use this file to get started with Frontitude or share it with a teammate who’s ready to dive in.

‍

👉 Check it out on Figma Community