◈OpenTree DashboardSign in

$ cat regex-tester.html

The single-file tools you keep rewriting

A regex tester. A JSON payload differ. A shape-of-this-payload viewer. Every team has ten of them, each one a single HTML file that lives in someone's downloads folder. Publish them once and bookmark the link.

The category

These are not applications. They are one-off utilities — a page with an input box, some logic, and an output pane — and the effort of hosting them has always been out of proportion to what they are. So they end up as a local file that only one person has, rewritten by the next person who needs it.

What people actually publish here

A regex testerYour patterns, your sample payloads, no third party involved.
A payload viewerPaste a blob, see its shape, without opening a formatter site.
A converterThe units, currencies or timestamps your team keeps needing.
A one-off dashboardNumbers for one meeting, at one bookmarkable address.

Publishing one

curl -X POST https://read.botook.ai/sites \
  -H "Authorization: Bearer otr_live_YOUR_KEY" \
  -F file=@regex-tester.html \
  -F expires_in_hours=never

Or let the agent that wrote it publish it directly — it usually just did.

Bookmark it, do not re-derive it

A shareable link means the tool exists for the team, not for the person who happened to generate it. Pin the expiry open and put the URL in the channel topic.

Why not a general host

A platform like VercelHere
Unit of deploymentA project with a buildOne file
SetupRepository, config, pipelineOne HTTP call
Private by defaultNoYes
Cost of a throwawayA project you will never deleteA link that expires by itself

Nothing wrong with a real platform — it is just heavy for a page whose whole source is 200 lines and whose lifetime is one sprint.

Keep it internal

These tools tend to contain the payloads you were debugging, which are exactly the payloads that should not be on a public URL:

The strict policy is a feature here

Single-file tools written quickly love to pull a script from a CDN. The viewer's content policy refuses third-party scripts, which means the tool either works self-contained or you find out immediately — better than discovering a year later that your payloads were being parsed by someone else's bundle.

Updating without moving the bookmark

curl -X PUT https://read.botook.ai/sites/SITE_ID \
  -H "Authorization: Bearer otr_live_YOUR_KEY" \
  -F file=@regex-tester.html

Same URL, new version. Nobody has to be told.

Multi-file tools

If the tool grew a stylesheet and three scripts, zip the directory and publish that. The tree is served with index.html as the entry point.

A catalogue of them

Publish an index page that links to the others and pin its expiry open. Now the team has an internal tools directory that took four minutes to build and no infrastructure at all.

What these tools may not do

Worth knowing before you move a utility here, because it decides whether the thing works at all. The viewer runs under a strict policy, so a tool is limited to what it can do inside the page itself — which is most of them, and not all of them:

The toolWorks here?
Parses, formats, diffs or converts text in the browserYes — this is the whole category
Keeps state in localStorage for the person using itYes, per reader
Pulls in a library from a public CDNNo. Third-party scripts are blocked; bundle it into the file
Calls an internal API from the pageOnly if that API allows this origin — and think about whether it should
Needs a server, a database or a loginNo. There is no server side here to give it

The rule of thumb is that anything which would work from a local file works here, minus the file:// quirks and plus a URL you can send to somebody. Bundling a dependency into the single file is usually a one-line change and makes the tool outlive whichever CDN it was borrowing.

Who else can reach it

Only people holding the link, subject to whichever gate you set. Opens and unique viewers show up in the dashboard, which is usually how you discover a tool became load-bearing for someone else's workflow.

Questions

Can the tool call our internal API?

Only if that API allows the origin. The viewer's policy restricts what the page may connect to.

How long can it live?

Forever — expires_in_hours: "never".

What if it needs a server side?

Then it is an application, and it belongs on an application platform. This hosts the document.

Keep reading