Enloop v0.5.8
Two changes since v0.5.6.
Capture the page's console during a run
The console is where the cheapest evidence of a bug lives and where it is
invisible by default — an uncaught TypeError behind a button that appears to
do nothing, a 401 logged by a fetch wrapper. Settings → Capture during runs
now makes it part of the run, with two independent toggles, both off by
default: console output, and failed requests (method, URL, status, duration —
never headers, never bodies, query strings redacted). Off by default because
console text carries tokens and customer data, and runs are written to a folder
people commit.
Turning capture on needs a page reload; turning it off does not. The wrapper
has to be installed before any page script runs, or it misses the load — usually
the interesting part — and Chrome can only guarantee that from the next
navigation. The panel says so and offers a Reload page button. Capture
covers the sites you have already granted Enloop access to, and no others.
A run folder gains console.jsonl (the record, appended live) and console.md
(the same thing rendered for a person at finish, grouped by step), and
run.json gains per-step counts. Whether any of it reaches an agent is a
second, separate decision made in the finish bar — what gets attached is a
deduplicated digest, not the raw log.
Shared links go in the fragment, compressed
A viewer link carried the case in ?c=, so every shared case travelled to
GitHub Pages on its way to the reader. Nothing was ever uploaded — the page has
always decoded on the reader's own device — but the host still saw the bytes go
past, and cases name internal URLs and staging logins. The case now rides in the
fragment, which browsers never send to a server.
It is also deflate-compressed, which brings a case link down to a third to a
half of its old length: a long case that had to be pasted now fits in a link.
Links written before this still open.
Install: download enloop-0.5.8.zip, unzip it somewhere you intend to
keep, then chrome://extensions → Developer mode → Load unpacked → select
the unzipped folder, the one with manifest.json directly inside it.
Upgrading: replace that folder's contents with the new zip's, then press
Reload on the Enloop card. A new build alone does not refresh an already
loaded extension.