A Queue of real questions
Each one carries only the part of the Trip you point it at. Revise it, ask again, or close it with a reason.
Private soft launch · planning only
Keep the journey's reasoning, not just its reservations.
A private Trip keeps its brief, its chapters, the dated evidence behind each option, why a choice was made, and every question still open. You can carry a bounded slice of it to your chosen AI yourself; nothing here is connected to one.
The division of labour
You bring the AI. This keeps the record.
There is no assistant running inside Assist With Travel. It does not search, book, pay, contact a provider, or take another outside action. The workspace keeps your planning state so the thinking survives.
What it actually keeps
Come back months later, not minutes later.
Travel research is worth keeping because it should not have to be repeated. The workspace stores the evidence and the tradeoffs, not only the answer you landed on.
Dated evidence
Every finding and option keeps its source, the date it was observed, and what that source cannot tell you.
Comparisons and decisions
Your own criteria, a ranked shortlist, and a decision trail that survives changing your mind. Chosen never means Confirmed.
A bounded handoff
See exactly what a question would carry—and what stays behind—before you copy anything.
The planning model
A route is more than a list.
This static specimen shows the shape the signed-in workspace now saves: nested chapters, a library of sourced research, and a decision trail. Live research and providers remain later work.
Planning direction · static example · not current saved data
Cascade Loop
21–29 September · three chapters
- Seattle arrivalFirst stay
- Highway 20 eastPossible nested stops
- Diablo Lake
- Winthrop
- Return via Stevens PassAlternative route
- Pass closure dates
- Packing notes
- Route notes brought in by hand
Route east
Highway 20 is the working choice. Revisit when seasonal closure evidence changes.
Candidate reasoning · not a bookingNight three
Winthrop is preferred over a longer second driving day.
Planning choice · not confirmedChosen-AI continuity
Bring your own AI.
Nothing is connected. You move the text, on purpose.
- 1
Choose what travels
One question, with the route, evidence, and constraints it actually needs.
- 2
Ask wherever you like
Your assistant, your account, your terms.
- 3
Review the answer
Separate suggestions from dated facts and stated uncertainty.
- 4
Record it with its source
Save the result yourself, and decide separately from what you were told.
Product truth
Where this is today
Current
- A home showing what needs you across every Trip
- A Queue of real questions, each carrying only the context you chose
- Nested chapters, places, and source-backed evidence with observed dates
- Comparisons, rankings, decisions, and their history
- Your own constraint, reservation, and document records
- Private file uploads attached to the part of the Trip they belong to
- Export, archive and restore, and deliberate deletion of your own data
Partial
- Every source is entered by you or transcribed from your own AI
- A remote
/mcpendpoint is live; signing in from your AI client is the approval, and it grants every scope this product has - Your connection settings page only narrows: switch off anything you would rather it did not do, or revoke it, and that takes effect on its next request
- No tool here adds to your Queue. What your AI suggests waits in AI Suggestions until you accept it
- Privacy proof covers the implemented owner scope, not sharing or recovery
Later
- A provisioned tool server and a connected AI
- Live research, sources, and provider integrations
- Booking, payment, sharing, and outside actions