Step-by-step

✈️ GitHub Copilot

GitHub

📘 Step-by-step 📘 GitHub Copilot↗ GitHub Copilot · Official sitebeginner 🏠 Everyday life

Plan a week-long trip itinerary with Copilot from a simple destination list

Q: Do I need to prepare anything?

A GitHub account (free at github.com — sign-up takes about two minutes). A way to reach Copilot Chat : in a browser at github.com/copilot, or inside VS Code if you already use it. The free tier has a monthly usage limit that's usually plenty for a one-off planning chat; if you hit it, you'll see a clear message. A short list of the places you want to visit — even rough is fine. Your travel

Q: What mistakes should I avoid?

Asking for too many cities at once. Six cities in seven days usually produces a rushed, joyless plan. Cap it at four or five for a relaxed trip; let Copilot spread them out. Trusting train times and opening hours blindly. Copilot drafts plausible schedules — they may be wrong. Cross-check with the operator's website before you book. Forgetting to mention how you'll travel. The plan changes

Turn a short list of cities and dates into a day-by-day plan with travel times, using GitHub Copilot Chat in your browser

6 min read·August 13, 2026

This guide was written by AI. It passed automated fact and quality checks; no human editor reviewed it.

See AI World HQ first on GoogleAdd us as a preferred source and our stories show up higher in Google’s Top Stories.Add on Google

Planning a one-week itinerary is one of those tasks that feels simple but turns into a long spreadsheet. GitHub Copilot — the AI assistant made for code — also has a chat mode (think of it as a chat box inside GitHub or VS Code) that handles everyday questions like this. It's a slightly off-label use, but it works well for first drafts. Here's how to use it for a trip.

💡 Tip: tap a step’s number when you finish it — a green tick appears and your browser remembers how far you got.

✅ Before you start

A GitHub account (free at github.com — sign-up takes about two minutes).
A way to reach Copilot Chat: in a browser at github.com/copilot, or inside VS Code if you already use it. The free tier has a monthly usage limit that's usually plenty for a one-off planning chat; if you hit it, you'll see a clear message.
A short list of the places you want to visit — even rough is fine.
Your travel dates and a general sense of pace (relaxed vs packed).
About 15 minutes from first click to a printable plan.

Step 1 of 6

Open Copilot Chat in your browser

Go to github.com/copilot and sign in with your GitHub account. After signing in, look for a chat box — usually labeled "Ask Copilot" or something similar — at the top or side of the page. Click inside it. The cursor blinks in an empty text field, and the rest of the page fades back slightly to show the chat is the active area. If you use VS Code, the same chat lives in the sidebar under the Copilot icon; the steps below work the same way. A new chat session is now active and waiting for your first message.

💬 Exampletype a single word first to confirm it works, like "hi".

🔄 If it looks different

**** the exact label and position of the chat box change often, so look for a rounded rectangle that says "Ask", "Chat", or "Copilot".

✅ You'll know it worked when

Copilot replies with a short greeting.

Next step ↓

Step 2 of 6

Set the scene with one short sentence

Before you paste your list, write a one-line brief so Copilot knows the tone you want. Treat it like briefing a friend who's helping you plan. State who's traveling, how long you have, and what kind of trip it is. A line of context up front usually gives you a more useful first answer than jumping straight into the city list. The reply may simply acknowledge — that's fine; the goal is to set expectations before the real ask.

💬 Try typing this"I'm planning a relaxed 7-day trip for two adults in October, and we love food, walking, and quiet neighborhoods."➤

✅ You'll know it worked when

later replies reference your tone or pace, not just generic tourist spots.

Next step ↓

✏️ Sketch — your screen may look a little different

Step 3 of 6

Hand over your destination list and dates

Now paste the city list in plain English. The clearer your dates and the order you'd like to visit in, the more accurate the plan. You don't need exact addresses — cities, regions or neighborhoods are fine. If you already have a rough order, say so ("I'd like to start in X and end in Y"). Copilot reads the whole message as one go and starts building a structure from it, so put everything you want considered in this single message.

💬 Try typing this"Cities I'd like to visit: Lisbon, Sintra, Porto, Coimbra. Dates: 5 to 11 October. Start in Lisbon, end in Porto. We have a rental car."➤

✅ You'll know it worked when

the next reply is a numbered day-by-day breakdown, not a single clarifying question back to you.

Next step ↓

✏️ Sketch — your screen may look a little different

Step 4 of 6

Ask for travel time between each stop

After the first draft, send a follow-up that explicitly asks for travel time between stops. This is the part most people forget, and it's where Copilot is genuinely useful — it can roughly estimate drive, train or bus times so you don't accidentally schedule a six-hour drive into a half-day stop. Be clear about how you'll actually travel, because the same two cities can be 30 minutes apart by train and three hours by road.

💬 Try typing this"Can you add the approximate travel time between each city by car, and flag any day where the drive eats more than 3 hours? Suggest a faster option if one exists."➤

✅ You'll know it worked when

each transition line now includes something like "≈ 1h by train" or "≈ 2h30 drive".

Next step ↓

✏️ Sketch — your screen may look a little different

Step 5 of 6

Refine with your real preferences

The first draft will be generic — that's normal. Now ask for the changes that matter to you: pace, food, kid-friendliness, walking limits, budget, time of year. One preference at a time works best; long "and also…" lists tend to produce messy replies. Think of it like editing a draft document with a colleague: small, focused comments in sequence.

💬 Try typing this"Please slow down Day 3 — one museum, one long lunch, and a sunset walk. We don't want to be on our feet for more than four hours."➤

✅ You'll know it worked when

the revised day fits the new constraint and doesn't just pile on more activities.

Next step ↓

✏️ Sketch — your screen may look a little different

Step 6 of 6

Save the plan and double-check the moving parts

Once you're happy, ask Copilot to format the final itinerary as a clean list or table so you can copy it into Notes, Google Docs or an email. Then always verify anything that moves or costs money: train times, museum opening hours, restaurant reservations. Copilot can guess these, but it doesn't have real-time schedules, so the plan is a first draft, not a travel agent. One last sanity-check question helps: ask for the slowest day in the plan and confirm it actually feels relaxed.

💬 Try typing this"Can you give me the final itinerary as a Markdown table with columns for Day, Morning, Afternoon, Evening, and Travel Time?"➤

✅ You'll know it worked when

you can paste the output straight into another app without cleanup, and when every transit line has a number you can sanity-check online.

✏️ Sketch — your screen may look a little different

⚠️ Common mistakes

Asking for too many cities at once. Six cities in seven days usually produces a rushed, joyless plan. Cap it at four or five for a relaxed trip; let Copilot spread them out.
Trusting train times and opening hours blindly. Copilot drafts plausible schedules — they may be wrong. Cross-check with the operator's website before you book.
Forgetting to mention how you'll travel. The plan changes a lot between "by car", "by train" and "on foot". Add this in Step 3, not later, or the travel times will be invented.

🚀 Try it now

Open github.com/copilot, sign in, and ask: "Plan a relaxed 2-day weekend in [your nearest big city] for someone who likes coffee, books and walking." See what it gives you in one reply — that's your baseline.

🎯 Next guideTurn a Messy Spreadsheet Export into Clean Data with CopilotDrop a messy CSV into GitHub Copilot and get back tidy dates, names, and columns you can actually use.

❓ Quick questions

How long does this take?

About 6 minutes — the guide has 6 steps, and you can tick each one off as you go.

Which tool do I need?

This guide uses GitHub Copilot — but the approach works very similarly in other AI assistants.

Do I need to prepare anything?

A GitHub account (free at github.com — sign-up takes about two minutes).
A way to reach Copilot Chat: in a browser at github.com/copilot, or inside VS Code if you already use it. The free tier has a monthly usage limit that's usually plenty for a one-off planning chat; if you hit it, you'll see a clear message.
A short list of the places you want to visit — even rough is fine.
Your travel dates and a general sense of pace (relaxed vs packed).
About 15 minutes from first click to a printable plan.

What mistakes should I avoid?

Asking for too many cities at once. Six cities in seven days usually produces a rushed, joyless plan. Cap it at four or five for a relaxed trip; let Copilot spread them out.
Trusting train times and opening hours blindly. Copilot drafts plausible schedules — they may be wrong. Cross-check with the operator's website before you book.
Forgetting to mention how you'll travel. The plan changes a lot between "by car", "by train" and "on foot". Add this in Step 3, not later, or the travel times will be invented.

Keep reading

📘 Plan Your Next Holiday: Create a Custom Travel Itinerary with Meta AI A beginner-friendly walkthrough to using Meta AI on your phone or browser to draft a personal travel plan, day by day. 📘 Plan a Family Weekend Getaway with DeepSeek: A Step-by-Step Guide Get a kid-friendly day-by-day itinerary with restaurant picks and travel times — for any budget 📘 How to Plan a Weekend Getaway Itinerary with Any AI Assistant Tell the AI your city, dates and interests, and walk away with a day-by-day plan and restaurant ideas in about ten minutes. 📘 How to plan a trip with AI: itinerary, budget and tips Turn a vague travel idea into a detailed day‑by‑day plan, a realistic cost estimate and handy local advice using a free AI chat tool. 📘 Turn a Messy Spreadsheet Export into Clean Data with Copilot Drop a messy CSV into GitHub Copilot and get back tidy dates, names, and columns you can actually use. 📘 Build a Simple Event Sign-Up Form with GitHub Copilot Plan the fields your event needs, then have Copilot draft a clean HTML form you can open in any browser.

Was this helpful?

✦ Generated by AI in AI World HQ's automated newsroom, written in plain language. Checked by automated fact and quality gates — no human editor reviewed this guide. Spot a mistake? Use the buttons above.

📘 Prefer it in one file? Home and Family: The AI Pack (12 guides, free printable PDF)

← Back to all stories