Feature
Your agent traffic, in the toolbar.
The lane split, a live feed of crossings, your route policy and your settlements — without opening the dashboard. A Chrome extension for your Wayleave account.
Install it
It is not on the Chrome Web Store yet. It installs from source in four steps, and this page will say so differently when a listing exists.
- Download the repository — Code → Download ZIP, then unzip — or clone it.
- Open
chrome://extensionsand turn on Developer mode. - Click Load unpacked and choose the unzipped folder.
- Pin the Wayleave icon, click it, and sign in.
git clone https://github.com/gibrancorbin11-hub/wayleave-extension.gitWhat it shows
- The four lanes — human, verified agent, declared agent, suspected bot — as a share of the window it holds.
- A live feed of crossings: time, identity, path and what the gate decided. A 402 is shown as the product working, not as an error.
- Your route policy, read from the Identity API.
- Settlements, once an agent pays a 402 and the rail confirms it.
Percentages are of the window the extension holds locally, not of your account’s lifetime, and the page says so rather than leaving you to assume it.
What it cannot do
This is a security product, so the part worth checking is what the manifest does not ask for. Three permissions — storage, identity, alarms — and exactly one host, meter.wayleave.dev.
- No
tabs,webRequest,webNavigation,history,scriptingoractiveTabpermission. - No content script on any page, and no
<all_urls>grant. - So it cannot see what you browse. That is the manifest, not a privacy policy — and a test fails the build if it drifts.
Where your token lives
In chrome.storage.session, which is memory-only and cleared when Chrome closes. chrome.storage.local holds the cached feed and nothing else, and a test asserts the token appears nowhere in it. No key or anon JWT is baked into the source; the config is fetched at runtime.
“Open dashboard” hands the session to wayleave.dev so you are not asked to sign in twice. The token travels in the URL fragment, which is never sent to a server and never appears in a Referer header, and the dashboard strips it with history.replaceState the moment it lands.
Questions
Is it on the Chrome Web Store?
Not yet. Install from source with the four steps above. The source is public, which also means the permission claims on this page are checkable rather than taken on trust.
Do I need a paid plan?
No. It reads the account you already have, on any plan.
Is it open source?
Yes, MIT. 27 tests, no dependencies, and no build step — what is in the repository is what Chrome loads.