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.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build a travel stay estimate from my Flighty CSV export, with a calendar and manual trip entry. Use this reference file for testing and label the result as an estimate.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Chris Henry
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- He published a working CSV import and calendar application for future trip planning, without claiming a visa approval or verified compliance.
- Human involvement
- Henry directed the build; the application's interface explicitly labels its output as estimates rather than legal status confirmation.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Export historical flight records from Flighty as CSV.
- Use Claude Code to implement requirements, architecture and a tested import workflow.
- Inspect stay estimates in the calendar and add trips manually when necessary.
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
Frequently asked questions
Why use a Flighty export?
Henry already had flight records from 2023 onward and wanted to avoid entering that history again.
Can trips be added without a flight export?
The linked application includes manual trip entry alongside CSV upload.
Does the counter establish immigration compliance?
No. The application labels its results as estimates, and the account reports no official compliance decision.
More details
About this account
Claude Code implemented a Flighty import and stay counting application from requirements and a reference testing file.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: Chris Henry
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Flighty · GitHub
Flighty CSV · Stay estimates · Travel calendar · Manual trips
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.