AI Agents Stop Waiting for Permission
Three of this release's four new capabilities center on a single shift: AI agent suppliers now behave like real suppliers. Before today, an AI agent would sit in a job queue waiting for someone to click Accept, the same way a human freelancer does. That was never what they were designed for.
Now, jobs assigned to an AI agent automatically move to In Progress and trigger the AI workflow without manual intervention. The change applies to both Standard and Codyt projects, including workflow kickoff from predecessors and mid-flight reassignment. Assigning a step to an agent ships work immediately, not when a project manager happens to notice.
Two supporting changes round out the story. Segment edits made by AI workflows are now attributed to the actual responsible user rather than the platform administrator, so revision history and supplier performance tracking finally reflect reality. And the AI agent status icon appears in the Codyt Manage Items list, the Codyt Find Items list, and the Standard project Jobs Expanded view, with click-through for execution status, errors, and service details.
A Review-Only Door Into the Editor
One of the most-requested access rights shipped in this release: R267, the review-only right. Turn it on for a user and they can open the CAT editor, read content, add comments, and change segment or job statuses, but they cannot edit source or target text. Backend safeguards block every path to editing, not just the UI controls.
This matters most for teams where subject-matter experts, legal reviewers, or regional stakeholders need to participate in a translation project without the authority, or the risk, of changing wording. Gaming studios have been asking for this model for localization QA passes, and the use case lands equally well for life sciences regulatory reviewers and enterprise legal teams. Pair it with the broader user rights model and you have a review layer that audits cleanly.
The Supplier Experience Grows Up
For the freelancers and agencies who do the actual translation work, a few small changes add up to a better day. Suppliers now see the predecessor job's deadline on any dependent job, in their own time zone, instead of a vague "waiting for the preceding job to complete" message. When you're a translator trying to plan your week, knowing that a revision job unblocks on Thursday rather than "sometime soon" is the difference between accepting work and declining it.
The Edit All Languages access right no longer classifies a user as Power User. Linguists and Requesters can now use cross-language editing without consuming a Power User license seat, which lowers the license cost of multi-language workflows materially. A new Open in Editor action on the Standard Jobs page takes a project manager straight to the Editor with the selected job's documents loaded, skipping a two-click detour. LSPs running hundreds of Standard projects at a time will feel that one the moment they log in.
Document Fidelity, Quietly
Four items in this release are about documents that looked right but weren't. Microsoft Word cross-references used to silently absorb text that translators typed after them, which meant content could disappear from the output without any warning. They now display visible tag markers in the Editor so translators can see where field boundaries are.
XLIFF 2.0 files with non-standard inline tags in translation segments used to crash during import; they now parse cleanly, with unknown tags surfaced as generic inline elements. Translated HTML for right-to-left languages now includes correct text direction attributes, with a new parser configuration option for teams that need custom direction rules. Translated PDFs built on platforms using the Document Conversion service no longer fail at finalization.
These are the kinds of issues where the fix is invisible to most users and critical for a few. If you've run into any of them, this release closes the loop.
Workflow Decisions Get Sharper
Segment custom fields now support Date and Date/Time categories, enabling date-based metadata at the segment level. Deadlines, review cycles, content freshness windows, all the things that used to sit in a spreadsheet can now sit next to the segment they describe.
A new "Exclude texts in neutral status" option on the consolidation settings stops grey-status segments from being saved to the translation memory during consolidation. That protects TM quality for teams who use neutral status as a "not reviewed yet" signal rather than a final state.
Mandatory workflow QA profiles are now enforced consistently whether you run QA from the TMS or the Editor. Previously the TMS let you pick a different profile, which defeated the point of making the workflow profile mandatory in the first place.
Also in This Release
A handful of smaller items round out 2026.2.4.0: checkbox selection on the Standard Jobs print and export flow now respects which jobs you ticked; Codyt references in workflow explanations hide themselves on accounts without Codyt enabled; in-context translation memory matching computes accurately during online translation and when adding files to revision sets; the Maintenance and Statistics tab refreshes when you change the date period filter; invoice status changes no longer trigger an error when they close a workflow-dependent job; PowerPoint embedded Excel chart labels stop appearing for translation when the Extract Embedded Excel option is off; and the Order creation API respects the Document Format Profile from the Order Form.
The full technical notes for 2026.2.4.0 live on help.wordbee.com, with configuration steps and screenshots for each item. If any of these changes will reshape how your team works in Wordbee, talk to our team before you roll them out. We'd rather walk you through setup than let a release stumble in production.