Claude to replan a ryokan day in Wanderlog

Denys Vitali used Claude Code during a ten-day Japan trip, with Wanderlog holding the itinerary and a personal phone app displaying it. One detailed example came from arriving at a ryokan, when the remaining afternoon depended on check-in, dinner and bath times.

He first requested a proposal and required acceptance before the agent changed the stored plan. As check-in progressed, he supplied the current time. After finishing at 3:48 PM, he corrected dinner to 7 PM and explained when the onsen would be available. Claude rebuilt the afternoon around those anchors, combining a gorge walk, a shopping-street stroll, rest, dinner and later baths.

Only after Vitali accepted did the agent operate the Wanderlog MCP tools. It deleted obsolete itinerary blocks and updated visit times and notes so the revised day appeared in the trip data consumed by his phone viewer. The result was an edited itinerary, rather than advice left in a chat transcript.

Vitali also describes limitations: generous planning buffers meant further replanning, and low-level tools required several calls to shift one afternoon. Elsewhere he corrected a hotel placement on the wrong day. The useful pattern is to separate fixed reservations from flexible activities and require approval before writing a proposed change.

Prompt
Original prompt

Source: blog.denv.it · Denys Vitali