Expired links show a clear page, not raw transport errors.
If a reviewer opens an expired link, a stopped or refreshed link, or an invalid token, the relay returns a branded HTML page that explains what happened and what to do next.
How it works
How wiremaven turns localhost into a controlled review session.
Sharing localhost sounds simple until someone needs to review unfinished work live. wiremaven separates public access, local tunneling, and in-browser awareness so sessions are faster to run and easier to manage.
The flow
From install to shared review in three steps.
One install, one command. wiremaven handles the relay so you can focus on the review.
01
Start
Create a temporary review session from the port you use.
For supported frameworks, start with the same package manager your project uses to install wiremaven, run npx wiremaven init or the equivalent runner, then let the overlay create the first link from the page. The standalone CLI remains available when you want an explicit terminal-driven tunnel instead.
02
Route
Reviewers visit wiremaven instead of your local machine.
The hosted relay acts as the public entry point, then forwards requests through the tunnel to your local app. Access stays scoped to the active session and the link stays simple to share.
03
Stay aware
Live session signals stay visible while the review is in motion.
The overlay shows viewer activity, request outcomes, disconnects, and expiry events in your local app, so you do not need a separate dashboard.
Failure states
wiremaven gives each edge case a clear state.
Expired links, disconnects, and stale sessions each surface a clear state so reviewers and presenters know where they stand.
Presenters recover from the local CLI or overlay.
When the relay disconnects or the local app stops answering, the CLI and overlay surface structured error states with suggestions such as reconnecting the tunnel, restarting the app, or sending a fresh link.
A new session means a new URL.
Refreshing or recreating a session generates a new URL. The previous link stops working, so reviewers know to use the new one.
Architecture
How the localhost review flow is split in v1.
Each part runs where it belongs, making sessions temporary by default and visible during reviews.
| Part | Runs where | Role |
|---|---|---|
| Hosted relay | wiremaven edge | Public review link, request routing, temporary session state |
| Local agent / CLI runtime | Developer machine | Outbound tunnel, localhost proxying, session heartbeat, and optional terminal UX |
| Local control API | Loopback origin on the developer machine | Status, link actions, and event stream for the overlay |
| Overlay widget | Local dev page | In-context awareness for viewers, requests, failures, and expiry |
This split keeps wiremaven scoped: temporary, visible during reviews, and simple enough to trust.
Last updated: May 2026