How AIClaw 3.7.19 Makes Generated Documents Easier to Open

An agent can generate a useful report and still leave an awkward last step: finding the file and choosing the right application. A raw path gives the user location information, but it does not make that decision easy-especially when the answer contains several documents. AIClaw v3.7.19, released on October 23, replaces the earlier compact file cards with horizontal document rows and an explicit Open with menu. The change is already shipped and remains in the current v3.7.22 release. The implementation links below are pinned to v3.7.19. The earlier docked-reader article covered staying oriented while reviewing several files. This change addresses the step before that: recognizing an output and deciding where to open it.

Make the output recognizable before opening it

The shared file-card renderer puts three things in each row:

• a type marker,
• a filename with a readable format label,
• an opening control on the right.

DOCX files say Word, XLSX files say Excel, and PPTX files say PowerPoint. Markdown has its own label too. The visible name is extracted from either slash-separated or backslash-separated paths. The original path stays in a data attribute for the opening action. Hiding directory prefixes reduces visual clutter; it does not redact those paths from the rendered page or establish a privacy boundary. This markup is reused rather than reconstructed separately for every output surface. Markdown rendering uses it for recognized inline paths and local file links. GeneratedFiles uses it for remaining generated attachments, combining multiple outputs into one bordered list with a separator between rows.

Offer a choice that matches the file

The menu in FileReferences.vue offers an internal preview only when the shared format map recognizes a supported text format. The system-application action remains available. For example:

The format map includes text, SQL, Markdown, and common programming and configuration formats. It does not turn the reader into a Word, Excel, or PowerPoint renderer. Clicking the filename retains the existing default behavior. The preview store routes supported text into the reader when there is an active session; other formats go to the system-opening action. Opening the menu alone does not read the document or launch its application.

Keep the interaction consistent inside a document

Rendered Markdown previews use the same reference component, with the current document supplied as the base path. A relative reference inside a report therefore starts from that report's directory. The host still resolves and