1.4.1 ·
Tools has a Learn group: the regex syntax reference, the troubleshooting guides and the supported engines, each with what it is for; the footer links this changelog.
The site has an icon in browser tabs, bookmarks and on phone home screens.
Search engines and AI assistants can read what each page is: tools, recipes, reference pages and guides describe themselves in structured data, /llms.txt summarises the site and lists every published page, and robots.txt states that search, AI answers and AI training may use the site.
Tools that ask for Markdown get every published page as Markdown at its usual address; browsers still get the page.
The engines page shows each engine's version, build, download size, SHA-256 and license as soon as it opens, from this release's engine manifest, and still checks them against the manifest the site serves.
1.4.0 ·
Wider pages on large screens, a taller navigation bar with a larger name, and 14 px body text.
The test text shows line numbers.
Matches are highlighted in green in the text and in the match list.
Twelve verified examples, grouped by task, are one click away on an empty workbench.
When a run as you type hits its short time limit, the result says so and offers to run again with the 1 s limit.
Tools lists tasks and engine testers apart, each with what it is for; Escape or a click elsewhere closes the menus, and on phones Recipes, Saved, Help and the theme come first.
On phones, each tool page says what it is for under its name.
The keyboard hint in the editors no longer covers the engine and flags after a click: it shows when you reach an editor with the keyboard and goes away as you type.
Results no longer show an internal revision number; recipe cards state their shared verification once and open straight into the workbench.
If a part of the workbench cannot load, for example after the site was updated while the page was open, that part says so and the rest of the workbench keeps working.
Closer to the approved design: the line-number column runs the full height of the test text, a complete result shows a filled check, match cards are lighter, and Export, Add text and Open file have icons.
1.3.3 ·
The regex and test-text editors now use the same monospace type as the rest of the code on the page, at the line height the layout was designed for.
The result summary is shorter: Export sits next to the title and the details run underneath it.
Messages say things once: before a run the result panel has one sentence about what will appear, a no-match result no longer repeats "No matches", and a stopped or refused run states its status once with the fix next to it.
Run lists what is missing in the order of the fields: the regex first, then the text.
A run stopped at the match limit says in the result panel how many matches it found and why it stopped; a regex the engine refuses offers Edit regex, as a no-match result does.
While a run is in progress, Export waits for its result instead of exporting the previous one, also when the input did not change.
1.3.2 ·
The page no longer changes when the workbench starts: what you see before the script runs is the workbench itself, with the regex and text boxes ready for typing, and they stay exactly where they are.
The Python, PCRE2 and Go pages show their own engine and its download offer from the first moment; if a release ever lacks a page's engine, the page says so instead of using another one.
If the workbench cannot start, the page says so.
1.3.1 ·
Pages no longer jump while the workbench starts: the editors replace the starting view in one step, the engine check no longer moves the flags, and the generator's example builder is ready with the first screen.
1.3.0 ·
The workbench takes the approved blue-and-white look: a brighter blue, light card outlines and calmer text; buttons, fields and flags keep their high-contrast edges.
The regex sits in one compact dark bar with its slashes and flags; it grows with longer patterns and scrolls after 200 px.
Save and Share are next to the page title, with Export workspace file and Saved workspaces under More; below 1024 px they stay in the Workspace actions menu next to the save state.
Run is wider, cards have more room, result tabs are taller, and the result panel runs the full height of the input column.
1.2.0 ·
The workbench is organised as cards: the regex and engine, the test text with its line and byte counts, and one result panel with a summary of status, engine time, revision and how positions are counted.
Save, Share and Export sit together under the title; on phones they are in one Workspace actions menu.
Long result lists show 200 at a time; counts and export still use every match.
Explanation and Structure share one parse verdict and select the same token; the structure tree can be expanded, collapsed and reset.
Tests show which test is running and the time of each, and count failures apart from tests that could not be checked; a failure can be copied as text.
Result tabs follow the arrow keys; the column split starts at 55/45.
1.1.1 ·
The count of saved workspaces in the navigation is spaced from its label.
The help page's error search is a single-line field.
1.1.0 ·
Replacement chains show which step is running and which are done; Cancel still stops the whole chain.
A JavaScript regex error now points at its position; a pasted literal that cannot be converted is reported on its own.
Replace shows template errors next to the template; split results say which split the engine performs.
The navigation shows how many workspaces are saved on this device; code packages name their generator and earlier packages stay downloadable in the tab.
1.0.0 ·
First public release.
Engines: the JavaScript RegExp of your browser, and pinned WebAssembly builds of Python re (CPython 3.14.2 in Pyodide 314.0.7), PCRE2 10.48 and Go 1.27.1 regexp, all running in your browser.
Encrypted share links and remote Node runs are switched off in this release.