What Shipped This Week: Writingmate Work Pilot, a No-Charge Trial, and a Fix for Crashing Long Answers

We opened a pilot of Writingmate Work, a hosted workspace where an agent runs on your Writingmate credits. We also took the $1 charge out of the trial and fixed a crash that killed long answers halfway through. Most of the rest of the week went into making the first ten minutes with the product less annoying.

Here is the full list, then the details on each piece.

Feature	Category	Who it's for
Writingmate Work hosted pilot	New	Anyone who wants an agent workspace in the browser
Writingmate as default agent, optional providers	New	Work users who also have ChatGPT or Claude subscriptions
Explore before pricing, no-charge trial, install panel	Improved	New accounts
Streaming crash fix on long answers	Fixed	Anyone asking for long, table-heavy or math-heavy replies
Credits and bonuses after trial conversion	Fixed	Workspaces that moved from trial to paid
Free tools linked from the footer and catalog	Improved	Visitors looking for a specific free tool
Logo links to the homepage	Fixed	Everyone, mobile menu users especially

Writingmate Work: a hosted pilot

Writingmate Work is a browser app that runs at work.writingmate.ai. You sign in with your Writingmate account, and you get a workspace with its own persistent storage. Each customer gets a separate origin and a separate container, and model requests go through your signed-in Writingmate account, so they draw on the credits you already have.

We built it because people kept asking for an agent that can work on files and tasks over time, not just answer in a chat window, without setting up a machine themselves. Access is checked against your current plan and your active workspace membership every time you sign in.

This is a pilot, and it is rough in places. We spent most of the week fixing what we hit while using it ourselves. Writingmate is now the default agent in new and existing workspaces, and it is the first provider in the list. ChatGPT/Codex, Claude and other providers are still there as optional choices, and your existing connections and any later selection you make are left alone. Native ChatGPT sign-in works through device authorization, which suits a cloud host.

We also replaced the duplicate login and cloud screens from the upstream app with Writingmate sign-in, so you see one account instead of two. Product copy, page titles, install manifests and icons now say Writingmate. Cursor now installs inside a hosted workspace, which failed before because the runtime had no curl. The Codex sandbox works too.

One more fix: an old Work tab left open after your session expired used to fire background requests that each bounced into the sign-in flow. A single stale tab could hit the sign-in limit and show "Try signing in again in a minute." Those background requests now get a plain 401, and normal page loads still go through the usual sign-in.

To try it, sign in at work.writingmate.ai with your Writingmate account. Live generation uses your Writingmate credits, so it depends on your plan.

Explore first, then start the trial

New accounts used to land on pricing before they had seen anything. We changed that. Signed-in users can now open the app and look around first. Generation still needs a plan, and that check still happens on the server, so nothing is bypassed.

The trial changed too. The three-day trial now starts by collecting a payment method, with no trial charge. Before this week it took a refundable $1 charge. We removed the code that created that charge, and we kept the refund path for people who paid the $1 earlier. Our reasoning was simple: asking for a charge before someone has used the product puts the payment form in front of the value.

We also added an install panel below the sign-in form. When your browser supports it, the panel uses the native install prompt. Otherwise it shows steps for your device, so you can put Writingmate on your home screen or dock.

Two smaller billing details went in behind this. Checkout events are now sent before the redirect to Stripe, so we do not lose them when the page leaves. Retried billing events use stable IDs so analytics do not double count. You will not see these, but they make our own numbers about checkout trustworthy.

You can see plans at /pricing and start chatting at /chat.

Long answers no longer crash mid-stream

A customer asking Gemini 4 Argon for a product requirements document of roughly 50,000 characters kept hitting "Minified React error #185," shown in chat as an error with a Retry button. The same thing could happen with any long reply full of tables, inline code or math formulas.

We reproduced it and found the cause. The chat updates its view for every streamed chunk, and when one render of the growing answer took longer than 100 milliseconds, each buffered chunk forced its own full re-render back to back. React never got a gap to catch up, hit its update depth limit and threw.

The fix batches streamed chunks, so consecutive text, reasoning and tool-input pieces are merged and the answer renders once per batch. We also made sure that chunks already received are delivered before an error is reported, so a failure no longer eats the last piece of text. Pressing Stop mid-stream still works. Batching yields without the one-second delay that background tabs impose on timers.

You do not need to change anything. Ask for the long table-heavy answer that failed before and it should finish. If you still see the error on a specific prompt, send it to us from the chat so we can reproduce it.

Credits and bonuses after a trial converts

We found that our payment webhook was never subscribed to the event that fires when an invoice is paid. For workspaces that converted from a trial, that meant credits were not switched on at conversion, the annual welcome bonus did not fire, and upgrade credits did not land.

Before turning that event on, we fixed a second problem. Our webhook is pinned to an older Stripe API version, where the subscription ID sits at the top level of the invoice instead of the place the code read from. Without that fix, every paid invoice would have been skipped. If you converted from a trial recently and your credits look wrong, write to us from your profile and we will check your workspace.

Free tools are easier to find

The free tools catalog used to start empty and fill in after the page loaded. Search crawlers that do not run JavaScript saw no links to the individual tools. The catalog now ships with the tool links in the page itself, and the site footer has a Free Tools column with the eight most visited tools. For you, the visible change is the footer column and a catalog that appears at once. Browse them at /free-tools.

Fixed this week

• Long, table-heavy or math-heavy answers no longer end in a React error with Retry.
• Trial-converted workspaces now get credits, annual bonuses and upgrade credits when the invoice is paid.
• The header logo links straight to the homepage instead of going through a redirect.
• The logo in the mobile menu no longer leads to a 404.
• Expired Work sessions no longer lock you out of sign-in with a rate limit message.
• Cursor installs inside hosted workspaces.

Thank you to everyone who sent us the long prompts that broke things, since those reports are why the streaming fix exists. The full history of what we have shipped is on /changelog.

Artem