Noodle 0.10.2 keeps each collection’s latest Runner results available for the app session. Reload a collection, switch to another one and back, or leave the Runner to edit a request, then press F5 to return to the same result. Source navigation connects a failed check to the request, folder, or collection script that produced it.

Keep the run you are investigating

A retained run carries its executed configuration, request labels, and selected request/iteration. Editing options for the next run does not relabel the result you are inspecting. A configuration or script preflight failure also leaves the previous result available.

Each collection retains one latest settled run. A later completed, failed, or cancelled run replaces it; exiting Noodle clears the session. Runner results stay in memory and do not create Timeline entries or files on disk.

Open the source, then return

After the run and cleanup finish, open a completed result’s details and press o, or choose Open source. On Results, the selected script, test, assertion, or capture determines the destination. Inherited scripts and tests open the owning folder or collection script phase. Aggregate test results can offer several origins through a searchable picker.

From other detail tabs, Open source takes you to the request. External scripts open at their declaration, where Ctrl+Alt+X uses the existing validated-file workflow to open your configured editor. A renamed or deleted source produces a warning while the retained result remains available. Press F5 to return to its selection.

Source selection stays stable while navigating, including repeated visits to collection script phases. Searching the origin picker no longer triggers the detail overlay’s shortcuts underneath it.

Know what was retained

Text body previews stop at 10,000 UTF-8 bytes and show a truncation notice. When diagnostic limits omit details, Noodle says so and preserves failure summaries and source origins. Omitted results are distinct from checks that never ran. Binary responses retain metadata without body bytes.

Runner snapshots and Timeline now share diagnostic bounds, preserving cancellation, persistence, inherited-source, and child-request metadata. The transitive fast-uri dependency is updated and the schema validator bundle is regenerated. Runtime and development dependencies are refreshed while OpenTUI stays pinned to 0.5.14.

Windows build and artifact validation now use Bun 1.4.4 with target-specific producer metadata; other release targets remain on Bun 1.4.3. Windows keeps the full applicable suite and native platform checks without the repeated async stress pass.

The maintained noodle-dev and noodle-use skills now describe session retention, source navigation, and preview limits. Read the Collection Runner guide for the workflow and full changelog for the release details.