ngrok StrawberryHand the ngrok https edges to a companion
It reads every https edge your ngrok account holds, drafts the changes that follow, and hands you a card for each one before a single https edge moves.
Open the https edge. Check it against something else. Write the change. Move to the next one. That is the ngrok afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a https edge until you approve it.
What it can do is exactly what ngrok exposes to an account you authorise and nothing beyond it: 4 operations, 1 read and 3 writes. In practice that means it can update a HTTPS edge, delete a HTTPS edge and create a HTTPS edge.
The ngrok API stops at ngrok. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the https edges or ask you for them?
1 of the 4 operations is a read.
Your account, not a guess at it: a companion can get a HTTPS edge, and the full list below is the whole list, with nothing inferred from ngrok's documentation.
The https edges are what most of this inventory is about, alongside the https edges. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of ngrok admin becomes a queue you review.
- Get HTTPS Edge
Can it change a https edge without asking?
All 3 write operations wait for you.
A companion can update a HTTPS edge, delete a HTTPS edge and create a HTTPS edge, and each one is staged on an approval card first: you see the https edge, the field and the new value before it lands in ngrok.
Nothing in ngrok is sent, changed or deleted on your behalf without that click, and a rejected card leaves the https edge exactly as it was. The gate is the same one on every surface, described at security.
- Update HTTPS Edge
- Delete HTTPS Edge
- Create HTTPS Edge
Can it update HTTPS edge on a schedule?
Yes.
Saved as a routine, the ngrok https edges pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the engineering admin, the ngrok https edges sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents