✈️ Travel Planner

Mode: travel-planner · Category: Lifestyle

Trip planning, itinerary building, visa requirement lookups, booking suggestions

Quick run

From the repo root, after pnpm -r build:

node apps/cli/dist/index.js -a travel-planner -q "your question here"

Requirements

LLM provider

Recommended: anthropic, gpt-4-turbo, gemini

Set the corresponding API key in ~/.openvesper/.env:

  • ANTHROPIC_API_KEY (or other)
  • GOOGLE_PLACES_API_KEY (optional)

Plugins used

This agent has access to all plugins (cross-plugin tool registry), but typically reaches for:

maps, calendar

Skills it can pull in

weather-aware-itinerary

Example sessions

node apps/cli/dist/index.js -a travel-planner -q "Plan 5 days in Istanbul for a foodie"
node apps/cli/dist/index.js -a travel-planner -q "Visa requirements for Turkish passport to Japan?"

Scheduled mode (optional)

This agent ships with a heartbeat checklist in.agents/travel-planner/HEARTBEAT.md. The default schedule is0 9 * * SUN but the heartbeat is disabled by default.

To enable scheduled execution:

# Edit .agents/travel-planner/HEARTBEAT.md
# Change "enabled: false" to "enabled: true"

# Then add it to your cron job state
node apps/cli/dist/index.js cron add hb-travel-planner   --schedule "0 9 * * SUN"   --agent travel-planner   --prompt "Run your heartbeat checklist for {{date}}"   --deliver-to "telegram:@me"

Files

The agent's source files live under .agents/travel-planner/:

  • SOUL.md — persona and principles
  • IDENTITY.md — metadata (name, icon, model preferences)
  • USER.md — what the agent knows about you
  • TOOLS.md — tool policy
  • HEARTBEAT.md — scheduled checklist (opt-in)
  • MEMORY.md — long-term memory store

You can edit any of these files to customize the agent. Changes take effect on the next run — no rebuild needed.

Privacy

This agent runs entirely on your machine. Your prompts go only to your configured LLM provider. Nothing is sent to OpenVesper servers (we don't have any). SeeSecurity policy for details.

What's next?