Start here
There is nothing to install. No programs, no downloads, no black windows with green text. You already have everything you need, which is the browser you are reading this in.
Quiraing, Isle of Skye · photo Andrew RidleyTrips that show their work
Every travel site will tell you a restaurant’s opening hours. None of them tell you how they know, when anybody last looked, or what you should click to be sure. That gap is the entire point of this.
So every item in a trip carries four things: where it came from, how confident it is, when a human last checked, and what someone should do to settle it. The site will not let anything in without them.
See one in ten seconds. Before anything else, load the example trip. Look at how each item shows its own evidence — that is what you are going to be making. Nothing on that page is saved or sent anywhere; it is a scratch pad, so poke at it.
Making your own
Making your own
Spin the globe
Drag it. Scroll to zoom towards whatever you are pointing at, and it keeps resolving as you go: countries, then their regions and borders, then their cities, then the towns. On a phone, pinch.
Click any country you would be glad to end up in — you are not committing to anything, it is a shortlist. Click its cities to add those too. Then answer the easy questions underneath: how long, what season, how fast a pace, what you are in the mood for.
Copy the brief
At the bottom there is a brief — a block of text built out of everything you just chose. Press Copy brief.
This site never talks to an AI. It writes you something to ask, and you ask it yourself. That is deliberate: there is no key to leak, no bill that grows, and it keeps working no matter what any of these companies do next.
Ask Claude
Go to claude.ai and paste the brief in. Sign up for the free plan if you have not. Do not pay for anything yet — three sessions in you will know whether you need more, and you will know exactly what you were doing when you ran out. That is a much better basis for deciding than a guess.
It will come back with two or three trips to compare.
Paste the whole reply back
Come back here and paste the entire reply in. All of it. You do not need to tidy it up, delete the chatty bits, or find the right part — it goes looking for the trip inside whatever you give it.
Press See it. Your trip renders. It shows you the trip before it offers to keep it, on purpose, so nobody saves something they have not read. When you are happy, press Keep this trip.
Now the actual work
Everything that arrives is marked unverified. That is not the site being rude about Claude — it is the site being honest. Nobody has checked any of it yet.
Checking things is the real work, and it is the interesting part. Ring the place. Look at the official site. Then mark it confirmed — and it will ask for your name, and it will not accept a confirmation without one. A confirmation nobody signed is worth nothing six months later, which is exactly when you will be reading it.
The number can go down. Confirmations go stale after about four months and quietly drop back to needing a check. Information genuinely rots, and a score that only ever climbs is not measuring anything.
Send it to someone
Press Send to someone and you get a link. The whole trip travels inside the link — every item, and every check with the name and date on it.
They open it, check a few things themselves, send it back, and yours picks up their changes with their name on them. Nothing is ever applied without showing you what would change first. No accounts, no server, and nobody’s database to quietly die in two years and take the itinerary with it.
One thing to know about where trips live. They are saved in the browser you made them in, on that device. Plan on the laptop and it is on the laptop — it will not be on your phone, and it will not be there in a different browser. That is the trade for having nothing to sign into.
The link is how a trip travels. If a trip matters, send yourself the link. That is the backup.
Changing the site itself
Changing the site itself
Everything above is using the thing. This is building it, and it is a genuinely different activity. When stage one starts to feel like it is missing something, that is the moment for this — and not before.
- A GitHub account. Think of it as a shared folder that remembers every version of everything, forever — which is what makes it safe to poke at things, because nothing you do can be lost or broken.
- You edit one file, in your browser, with the pencil icon. It is mostly plain English with notes explaining each part.
- A check runs automatically. If you have made a mistake it leaves a comment in plain English saying what and where — like “Day 3, item 2: you wrote
verifyed, did you meanverify?” Fix it and it runs again by itself. - A link appears showing the whole website with your change in it.
When something goes wrong
It will, and it is fine. If the site tells you something is wrong with what you pasted, read it — it is usually exactly what it says.
For anything else: copy the whole ugly error, paste it to Claude, and say this is what happened, what do I do. Do not summarise it. Paste the whole thing, including the parts that look like nonsense. The parts that look like nonsense are usually the useful parts.
And if a page is being strange, reload it. Your saved trips are not going anywhere.