DEV Community

Arthur031221
Arthur031221

Posted on

Keeping the original beside a shorter reply

I built Cut to it for a small problem: sometimes I want a direct answer from a chatbot reply, but the answer arrives wrapped in several paragraphs. Asking again is easy. Keeping the original nearby while checking the result is less convenient.

The extension adds a control to completed assistant replies on the supported chat site. Clicking it opens a panel containing the original and a shortening prompt. The prompt asks for the useful answer first, in the same language, with facts, numbers, caveats, commands, and uncertainty preserved. Those are requests to the model. They are not guarantees.

A draft I can inspect

I can read or edit the prompt before inserting it. Insertion requires an empty, recognized composer. If the composer already contains my writing or its structure is unfamiliar, the extension refuses to replace it and offers a copy fallback. It never clicks Send or simulates the Enter key.

Undo belongs to a specific draft. Once I edit that draft, ownership is revoked, even if I later put the same text back. This avoids treating a matching string as permission to erase my work. Closing the panel leaves an inserted draft in the composer.

Choosing the comparison

After I send the prompt and receive another reply, I select the message to use as the rewrite. I chose this explicit step because automatically associating replies can be wrong during streaming, retries, or navigation. The panel shows both texts and their word counts. It does not infer that the rewrite is accurate.

Scripted local browser demo of Cut to it

The recording uses the real extension controls on a local fixture with prewritten replies. It demonstrates the interaction, rather than measuring a model's shortening quality. The source includes browser tests for the draft controls and navigation cases.

What remains rough

The current site adapter relies on recognizable page controls. A website update can break that integration. Authenticated live compatibility has not been checked, and installation still requires loading the extension through browser developer tools.

The extension makes no network requests and does not save conversation text itself. That boundary does not stop the host website from saving drafts or the clipboard from retaining copied text. I kept those details in the privacy notes because they affect how I use the tool.

Source and installation: https://github.com/Arthur031221/cut-to-it

I would like feedback on composer compatibility and the comparison controls.

I found a Windows CI test path issue. Its local correction passes Node 20 tests, but the guarded update flow has not uploaded it.

Top comments (0)