Use whichever AI you already trust and carry the relevant text between the two yourself. This page explains the manual method: choose one question, inspect its brief, and copy it to your AI.
Field procedure
Four deliberate steps
1
Choose one question.
Open the Handoff view in your Trip and pick the question, the chapter, and the comparison it concerns. You can leave the route or the saved research out entirely.
2
Check what stays behind.
Before you copy anything, the workspace lists what it included and what it deliberately excluded: other Trips, unrelated chapters, anything you marked sensitive, and every reservation and document record. Read the preview first.
3
Ask wherever you like, then review.
Paste it into the assistant you choose. Assist With Travel has no relationship with that service and cannot tell that you did it. Separate the recommendation from its evidence, its date, and its uncertainty.
4
Record the result with its source.
Save it under Research, naming where it came from, so the next session inherits the evidence rather than the conclusion. Deciding is a separate step you take yourself.
Plain text · built from what you saved
What goes out, and what should come back
The brief you take out
TRIP BRIEF — [trip name]
Prepared [date] · saved revision [n]
QUESTION: [one question, narrowly stated]
Chapter: [which part of the route this is about]
BRIEF
Purpose: [what would make this trip worthwhile]
Dates: [window and how much it can move]
Constraints: [what cannot move]
RECORDED CONSTRAINTS
- [requirement] [label]: [in your own words]
WHAT THIS PERSON ALWAYS WANTS
- [firm] [a standing preference, in their words] ([when it applies])
ROUTE
- [chapter] (stay, chosen) · [timing]
→ [the chapter in focus]
COMPARISON: [the question being weighed]
OPTION: [title] [candidate]
[why it might suit]
Price: [amount] · Freshness: [state]
Source: [where it came from] · observed [date] · limits: [what it cannot tell you]
SAVED RESEARCH
- [title] [observedFact, currentWithinWindow]
[what it says]
Source: [name] · observed [date]
DECISION SO FAR: [state]
Preferred: [option] · Fallback: [option]
Reason / Concern / Revisit when: [...]
TREAT AS OUT OF DATE
- [anything observed long ago or marked for refresh]
DELIBERATELY NOT INCLUDED
- [other Trips] — a brief answers one question about one Trip.
- [reservations, documents, and uploaded files] — never placed in a brief.
- [constraints you marked sensitive] — they stay in your workspace.
- [which Trip taught a standing preference] — a preference is about the
person; the journey behind it is another Trip's business.
BOUNDARY
Context only. No tool permission, provider access, booking authority, or
payment authority. Do not book, pay, hold, cancel, log in, message anyone,
publish, or take any other outside action.
The result you bring back
{
"contract": "travel.save_complete_result",
"schemaVersion": 1,
"summary": "One sentence describing what this result added.",
"runStatus": "completed",
"assumptions": ["Anything you had to assume, stated plainly."],
"sources": [{
"title": "Where this came from",
"kind": "website",
"url": "https://example.org/page",
"observedAt": "YYYY-MM-DD",
"limitations": "What this source cannot tell us."
}],
"findings": [{
"title": "Short title",
"summary": "What was learned.",
"findingKind": "observedFact",
"freshnessState": "currentWithinWindow",
"sourceIndex": 0
}],
"options": [{
"title": "A choosable option",
"summary": "Why it might suit this trip.",
"status": "candidate",
"sourceIndex": 0,
"priceMinor": 14500,
"currency": "EUR"
}]
}
The workspace generates both of these for you from your own Trip; these are only their shape. The AI's output and your decision remain two different things — a returned result may propose options, never choose one.
What this is not
Not a connected model or background worker.
Not a claim that your particular AI client works. A remote /mcp endpoint is live and standards-compliant, but no named client has completed a proved lifecycle here yet, so none is named.
Generic structured fields refuse booking references and confirmation codes. Only the explicit private reservation field accepts a person-reported confirmation code, kept owner-only and returned only through deliberate owner-only detail retrieval. Generic listings, activity, briefs, exports and MCP output exclude it. API keys and provider logins are never stored. Private original screenshots and files are kept byte-for-byte and may contain confirmation codes; their contents are never extracted into structured fields, listings, activity, or briefs.
Manual briefs never include uploaded files. A connected AI may retrieve ordinary-sensitivity originals explicitly selected for a Queue question, with files.read and the required Trip grant. Sensitive and unselected files stay excluded.
Not a route to booking, payment, provider login, or another outside action.
Not a way to reach us. Nothing written in a Trip or a brief arrives anywhere; help runs through Assist With Life support, and this site has no email address.