Claude to import Flighty records into a stay counter

Chris Henry wanted to track planned travel without retyping years of flight records. He already used Flighty and could export flights from 2023 onward as CSV, so he made that file format the starting point for a custom stay counter built with Claude Code.

His account describes moving from requirements to architecture and implementation, then using GitHub issues and custom commands to continue the work. He built the application over a few days, with a reference file for testing. He also reported higher token use, without publishing a precise total cost.

The linked application accepts a Flighty CSV and offers manual trip entry. Its repository documents identifying relevant trips, showing a rolling stay estimate and presenting a calendar. Shared URL state is part of the published application, while the browser interface makes clear that the results are estimates rather than confirmation of legal status.

The completed artifact was available when Henry wrote about it, but he described using it for future travel. The source does not show a visa decision, an official compliance check or an avoided overstay. The useful workflow is importing an existing travel record into a purpose built view, while retaining manual entries for trips that the flight history alone cannot represent.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: chenryventures.substack.com · Chris Henry