Trips

Trips helps you plan trips in Obsidian. It creates trip notes from your templates, saves them in the right folder and fills in their dates and links. Each trip gets a tab where you move its days and activities around.

Your notes stay ordinary Markdown. They work the same when the plugin is turned off.

Words used here

• Trip: one note for the whole trip, with a start and an end date.
• Day plan and stop: notes for part of a trip, such as three nights in one city. Each has its own dates inside the trip.
• Activity: a note for something to do, such as a museum. You can put it on one or more days.
• Kind: a type of note, with its own template, folder and form fields. You can use the kinds from the travel setup, change them or add your own. See Change the kinds.

Use it

All actions are commands. Open the command palette with Cmd+P (macOS) or Ctrl+P (Windows, Linux) and type "Trips".

Set up Trips

1. Open Settings → Trips.
2. Choose one way to start:
   • Use the travel setup to start with ready-made kinds. Trips adds their templates to _templates/ and their Bases to _templates/Bases/. You see the list of files first. Files already in your vault are never changed.
   • Use my own templates to start with one trip kind based on a note you pick, or on a starter note that Trips creates. Put {{start_date}} and {{end_date}} in the properties that hold the dates, for example startDate: "{{start_date}}".
3. Optional: under Travel folder, choose where trips are saved. Trips also looks for existing trips there.

The travel setup has these kinds:

Whichever way you start, you can change every kind later.

Change the kinds

Open Settings → Trips. Your kinds are listed under Trip kinds and Inside a trip. Select a kind to change it, or use Add trip kind and Add note kind to add one.

For each kind you can set:

• Name: how it appears in menus and buttons.
• Template: the note that new notes of this kind copy.
• Save new notes to: the path, built from {{trip_name}}, {{entry_name}} and {{trip_start_year}}, for example Travel/{{trip_start_year}}/{{trip_name}}.md.
• Contains (trip kinds only): which kinds you can add to the trip.
• One section per day: whether new notes get a heading for each date, and its format under Day-heading format.
• Form fields: the fields you fill in when you create a note. Use Add a field for more.
• Recognition and property names: how Trips tells the kinds apart and which properties hold the dates and links.

Template, path, field and day-section changes apply to notes you create afterwards; existing notes aren't rewritten. Renaming a property doesn't rename it in existing notes.

You can also edit your templates like any note. Change headings, callouts and text freely. Keep their properties and {{…}} placeholders, because Trips uses them to recognise and fill in notes.

Create a trip

1. Run Trips: Create trip….
2. If you have more than one trip kind, choose one.
3. Enter a name, a start date and an end date. The end date can't be before the start date.
4. Fill in any other fields from your template and select Create.

Trips saves the note in the folder shown under the name, for example Travel/2026/South Korea/South Korea.md, and opens it.

Add a day plan, stop or activity

1. Open the trip note.
2. Run Trips: Add to trip… and choose what to add.
3. Enter a name and dates. Dates must be inside the trip's dates.
4. For a day plan, you can select Add activity… to link activities and choose a day for each.
5. Select Create.

The new note links back to the trip and gets a section for each of its days. If you run the command without a trip open, Trips asks which trip to use.

Edit a trip's properties

Open a trip note, run Trips: Edit trip properties…, change the fields and select Save. If the note changed since you opened the form, nothing is saved. Reload the form and try again.

Plan the days

Open a trip note and run Trips: Edit trip itinerary. A tab opens with every day of the trip and the day plans, stops and activities on each day.

In this tab you can:

• Change the trip's dates: select the dates under the trip name, or use Trip actions → Change trip dates.
• Move a day plan or stop: drag it to another day, or use its ⋯ menu: One day earlier or One day later.
• Make a stay longer or shorter: use One night longer or One night shorter in its menu. To set exact dates, use Change dates….
• Put an activity on a day: drag it from Not on a day, or select + on a day and choose or create an activity.
• Move an activity: drag it to another day or another place in the list, or use Move to day… in its menu.
• Take an activity off a day: select × next to it. The activity note stays.
• Detach or delete a note: use Detach from trip or Delete… in its menu. Detached notes stay in your vault but no longer belong to the trip.
• Open a note: select its name. Cmd-click (macOS) or Ctrl-click opens it in a new tab.

Each change is saved to your notes at once. To reverse the last change, select Undo in the bar at the bottom. Undo only works while the changed notes are as Trips left them.

Moving a day plan or stop changes only its date properties. Check dates and day headings you wrote in the note text yourself.

Keyboard

Fix notes Trips can't read

Run Trips: Review notes that need attention. It lists notes that Trips can't match to one kind or one trip. Pick a note, then choose its kind or trip. Trips remembers your choice and doesn't change the note.

Use Trips from a script or agent

Trips adds commands to the Obsidian CLI. Obsidian must be running with the vault open, and Trips must be set up in it. Notes come out exactly as the creation form and the trip tab write them.

Fields and activities go in json, for example json='{"kind":"planning","name":"Alfama","trip":"Lisbon","start":"2026-09-11","end":"2026-09-12","activities":[{"name":"Tram 28","day":"2026-09-11"}]}'. Dates are YYYY-MM-DD; position counts from 1.

Every command answers in JSON. The CLI always exits with 0, so check the ok field: when it's false, error.code and error.message say what went wrong and what to do. When an edit to several notes fails partway, error.report lists the notes that were written. There is no Undo from the CLI.

Editing properties, attaching and detaching notes, deleting, Undo and fixing notes that need attention stay in Obsidian.

To let an AI agent plan trips this way, install the trips skill with skills:

npx skills add LekoArts/obsidian-trips --skill trips

It asks which agents to install it for. Add -g to install it for all your projects instead of the current one. You can also copy the skills/trips folder into the agent's skills folder by hand, for example .claude/skills/trips.

Requirements

Obsidian 1.13.1 or later. Works on desktop and mobile. Planning days works best on a larger screen; on a phone, the trip note's Base shows the plan.

Privacy

Trips works offline. It makes no network requests, collects no telemetry and needs no account. It only reads and writes notes inside your vault.

Contributing

See CONTRIBUTING.md.

License

MIT