Devotd Github
NewAI agents

sumantxd/shrike — Adds a HAR import entry to the changelog

The latest commit of sumantxd/shrike gives credit to the PR #110 contributor and adds an entry to the changelog stating that HAR files from the browser can be imported as trips.

Repositorysumantxd/shrike ↗

The latest commit of sumantxd/shrike gives credit to the PR #110 contributor and adds an entry to the changelog stating that HAR files from the browser can be imported as trips.

GitHub description: See what your app actually does. Click anything and watch the trip through your code, database and services, with real values. AI-native: your agent sees it too and fixes the real problem.

stars
★ 39
Forks
15
Language
TypeScript
License
MIT
Latest release
v0.2.0
Read original source ↗View on GitHub ↗

sumantxd/shrike is a tool that shows exactly what an application actually does, and shows as-is the path (trip) that a request takes through the code, the database, and services. The commit dated October 26, 2026, 1432840 changed not code but just one line of CHANGELOG.md. While giving credit to the PR #110 contributor @iamcipherdev, it added a changelog entry stating that a HAR file exported from the browser's network tab can be imported as a trip.

The new entry has two parts. Secret values contained in HAR files are masked by the same rules as other records, and files larger than 50 MB are rejected before the file is read. The change in this feature is that the source of records has broadened to the browser side, outside the app runtime. The same changelog also records the ability to select and review per-trip warnings (swallowed errors, N+1 queries, etc.) with list_actions, the status (broke, slow, worked) filters placed on list_trips, and the rule that replaces emails, phone numbers, and IBANs in live trips with strings such as [email#1]. The repository description explains it as a tool for agents that looks into the screen on their behalf.

That said, what this commit actually touched is only the description. The HAR import behavior is a feature that had entered earlier through PR #110, and what was added here is one line of changelog and contributor credit. This repository's release version, license, language, and star count are not present in the given record, so they cannot be known. The 50 MB limit and the masking rules are also descriptions written in the changelog, not measurement results. Whether browser records can be taken as evidence and used to help agents narrow down a problem remains a question to be judged after more version information and verification material have accumulated.