Release notes

Smarter segment editor

• Auto-titles.Leave the title blank and itinly derives one from the segment's own fields — flights become DEP → ARR (Carrier RouteCode) once both airports are set, and ground transport gets sensible defaults. Titles you type by hand are always respected; only auto-generated ones re-derive.
• Airport typeahead everywhere. The departure / arrival fields search a bundled catalogue of 1,178 commercial airportsby IATA code, city, airport name, or alias (so “Tokyo” finds NRT).
• City auto-fill. Picking an airport fills in the matching city automatically, so map pins and day-city grouping get the right location without a second lookup.
• Blur-to-save. Segment fields persist when you tab or click away instead of requiring an explicit Save press.
• Baggage field dropped from the flight form, and corrected placeholders for car-service and other-transport segments.

Faster, cleaner email scanning

• Parallel parsing (~3× faster).The scan pipeline parses emails in concurrent batches of three instead of one-at-a-time. A twelve-email inbox drops from roughly 54s to ~18s, well within Anthropic's rate limits.
• Marketing + reminder emails skipped.The parser now recognises promotional venue blasts and airline / hotel “your trip is coming up” reminders and skips them, instead of hallucinating segments out of content with no booking in it.
• Skip emails during review— skip individual emails, or “Skip all” when nothing's worth adding, before applying.
• Atomic dismissfixes the staggered banner flicker where the pending count lagged behind the list, and the mobile scan sheet no longer scrolls past the day's content.

Trips that keep themselves current

• Automatic status transitions.A trip's status now derives from its dates on load: planning before the start date, active once it's underway, completed after the end date. Cancelled trips stay cancelled. Transitions persist lazily in the background, so the Now / Upcoming / Past buckets stay accurate without anyone touching a status dropdown.

Exports + maps

• Cost-free PDF exports.PDF export can now omit per-segment costs and the cost summary — handy for sharing an itinerary with someone who doesn't need to see what you paid.
• Mobile map stops flashing Japan.The full-screen mobile map no longer renders a default Japan viewport while it geocodes the trip's real locations, and falls back to the segment's city when precise coordinates aren't available yet.

Reliability + under the hood

• Sentry bot-noise filter. A Deno-based crawler executing client JS on /login was generating unrecoverable errors in a runtime that can't stream fetch responses. The browser Sentry client now drops events from any such runtime, and the Service Worker registration path is hardened against a register() that resolves to undefined.
• Release-PR-only version bumps.The in-app version is bumped inside the release PR's own commit, so production always deploys a commit that already carries the right version.
• Tests grew to 1,065 across 66 test suites — new coverage for auto-title derivation, the email-skip parser branch, the parallel-scan pipeline, and the trip auto-transition helper.

Places to go

• Per-trip POI listthat isn't tied to a date or time — distinct from todos (action) and segments (date + time bound). Each place takes a name, address, and / or URL (at least one required), with optional city and notes.
• Renders as an orange map pin on both the desktop Map view and the mobile full-screen map, alongside the existing four itinerary pin categories (transport / lodging / activity / dining). Uses the --brand vermilion token so the colour stays in sync with the rest of the palette.
• Dedicated Places tab on the trip detail page on desktop, mirrored as a /m/trip/places route on mobile, with city-grouped section headers so a long list stays scannable.
• Backed by a new places Postgres table with cascade-delete from trips and an owner-only RLS policy. Trip schema bumps 2 → 3 with a migration step that backfills places: [] on legacy trips.
• Future “schedule this” action can promote a place into a real segment with a date and time — the data model is ready; the affordance lands in a future release.

Calendar sync on shared trips

• Recipients can sync now.A shared-edit trip's calendar-sync button used to be hidden behind useTripPermission().isOwner. The gate is now canEdit, so anyone with edit access can push to their own Google or Outlook calendar independently.
• Per-(trip, user) sync state. New trip_user_calendar_syncs table holds (tripId, userId, calendarId, segmentEventMap) per user. Two users syncing the same trip can't clobber each other's event ids — each user's mapping lives on their own row.
• Migration backfills the owner's state from trips.calendar_id + segments.calendar_event_id into the new table via jsonb_object_agg. Existing sync setups carry over without a re-sync.
• The menu label flips to Calendar synced (N) once the current userhas any segments synced — not the owner's count.

Auto email-scan robustness

• Run now on any schedule from /settings/account — fires the same executor the cron tick uses, so you can verify a configuration works without waiting for the next anchored fire-time.
• Sentry alert when scheduled runs start failing — every failed run is reported with email.outcome=failed + the schedule id + the provider so an operator gets paged before the user notices nothing's happening.
• Reconnect banner. When a scheduled-scan provider revokes its refresh token (Google reissues a session, Microsoft mandatory MFA bounces it, etc.), the in-app ConnectionRevokedBanner surfaces a one-click reconnect link instead of the schedule silently failing under the hood. Pauses the schedule until the user reconnects.
• DEBUG_EMAIL_SCHEDULE=1 Railway debug knob documents what each tick does (fan-out → per-schedule start / finish → cadence advance → next-run timestamp) so steady-state cron operation is debuggable. Failures still go to Sentry + console.error regardless.

Mobile + desktop polish

• Email-scan review card cleaned up.The cycling action chip is gone — it was redundant with the status pill (New / Enrich / Conflict / Duplicate) and confusing alongside the checkbox. Checkbox is now the sole add / skip control; the footer button matches desktop's “Add N segments” wording. Same treatment on the /m/share PWA share-target review card. Toggling a Duplicate's checkbox promotes the action so the apply call doesn't silently drop it.
• Trip header stops rendering two … menus on shared editor trips. “Leave trip” folded into the main TripActionsMenu for non-owner editors; the standalone LeaveTripMenu is reserved for read-only viewers.
• Account → Settings on the user menu (desktop + mobile) and the destination page H1. Better reflects the catch-all settings surface (theme, notifications, connections, delete account, scheduled scans, …).
• EditableTitle + trip-picker <select> overflow fixed on narrow viewports — both lacked min-w-0, so the edit-mode input box and the trip-picker dropdown extended past the right edge on 320 – 375px screens.
• Calendar-sync info dialogno longer flashes a pre-loaded description from a stale fetch before the current trip's state lands.
• “Tap to confirm” review sheet on mobile updates immediately when a segment is confirmed instead of waiting for the next React Query refetch.
• Page-shell padding standardized across home / trip / account on the web — the previous mix of p-4 sm:p-8 and ad-hoc values caused inconsistent left-margins between adjacent surfaces.

Sign-in + trust

OAuth and session-recovery improvements:

• Privacy + Terms surfaced in-app with a Google Limited Use disclosure on the privacy page (sections renumbered to match the Google API Services User Data Policy). No ads, no model training, no human review without consent; narrow transfer to Anthropic + Supabase.
• OAuth sign-in buttonsrepainted to match Google + Microsoft's published branding specs — full- colour Google “G,” approved container colours, Microsoft logo on a white-on-cyan layout that matches the identity-platform reference.
• Recovery from broken Supabase sessions. Stale refresh-token exchanges that previously left the user stuck in a “signed in but every request 401s” loop now surface the exchange error explicitly and route the user back to sign-in.

Under the hood

• Drizzle migration 0007 (places.sql) adds the per-user places table with RLS following the established pattern; migration 0008 (per_user_calendar_sync.sql) adds the per-(trip, user) calendar-sync table with backfill from the legacy single-user shape.
• Trip.schemaVersion bumps from 2 → 3 to gate the places backfill; migrateTrip handles both v1 → v2 history backfill and v2 → v3 places initialisation.
• CSP connect-src widened to cover Sentry's regional ingest hosts (*.sentry.io), unblocking client-side error reporting after Sentry moved customers off the global endpoint.
• Tests grew from 967 → 1052 across 66 test suites — new coverage for the places CRUD + RLS path, the per-user calendar-sync routes + migration, the scheduled-scan Run-now + reconnect banner flows, and the mobile review-card promote-action behaviour.

Thanks

Two big features (Places + per-user calendar sync), a fistful of scheduled-scan safety nets, and a long-overdue mobile review-card rewrite. Onward to 1.5.x.

Auto email-scan scheduler

• Recurring scans on a daily or weekly cadence — pick a folder or label per provider, anchor on a specific time of day (and day-of-week, for weekly), and itinly polls the mailbox on its own.
• Multiple schedules per user — one per (provider × folder × cadence) tuple, so a personal Gmail Travel/ label and a work Outlook folder can run independently on different rhythms.
• Include sub-folders / sub-labels— a single “Travel” pick optionally fans out to every descendant (Travel/Hotels, Travel/Flights/Confirmed, …) so you don't have to enumerate them.
• Findings land in the same review queueas a manual scan — nothing is auto-applied, so a scheduled scan can't silently put a misparsed booking on a real trip.
• Push notification + in-app banner when a scheduled scan turns up something new, deep-linking straight to the review step on either desktop or mobile.
• Pause / resume / edit / delete each schedule from /settings/account, with a “Recent runs” history dialog (last 50 per schedule).
• Backed by Supabase pg_cron + pg_net firing a shared-secret-guarded tick endpoint; per-user row-level security on the new tables.

PWA polish

• “Send to itinly” share target — pick itinly from any iOS or Android share sheet and the shared text / URL / page title goes straight into the parser. Forwarded confirmations from non-Gmail mailboxes work without leaving Mail.
• “Create trip” app-icon shortcut — long-press the installed PWA icon (Android) or right-click it (desktop) to jump straight into a new-trip sheet.
• App-icon badge on the installed PWA — incoming push notifications bump a numeric badge on the icon (Chromium / Edge / iOS 16.4+ Safari); cleared when you bring the app forward or tap the notification.

Timeline + segment polish

• Cruises render as multi-day bands on the Lodging lane instead of a single-day pill under Activities — same visual treatment as a hotel block, but with the ship name + 🚢 + duration.
• Car rentals get their own multi-day bands on the Transport lane, packed onto the same row as the per-day flight / train / transfer pills so the rental window is visible at a glance.
• Overlapping lodging bars no longer disappear — hotels and cruises that overlap (e.g. a hotel on embarkation day plus the cruise that picks up from there) pack onto separate tracks instead of one bar silently clobbering the other.
• Richer car rental titleslike “Hertz - Lihue”, with pickup / dropoff cities and times in the calendar event description; the all-day event spans through the dropoff date inclusive.
• Dedicated shipName field on cruises — extracted automatically by the email parser, used in the timeline pill and calendar event title; ports of call render in the calendar description.
• Cost displays always show 2 decimals (288.40 instead of 288.4).

Cleaner segment form

• “More options” disclosure at the bottom of the add / edit form gathers everything past the core booking fields — cabin class, baggage info, address, phone, breakfast included, free-form details, plus Cost and Confirmation # — into one collapsible section.
• “N filled” hint on the disclosure header so a rich parsed booking still telegraphs how much sits behind the fold without auto-expanding.
• Whole desktop segment cards are clickable to open the edit dialog (the pencil icon stays for discoverability); Enter / Space on a focused row works the same.
• Clearing the cost field now persists— previously the empty value silently no-op'd and the old cost stayed put.

Email parsing

• Prefers the plain-text part on noisy multipart confirmations when the HTML alternative is dominated by marketing copy and image alt text. A Marriott Vacation Club receipt that previously parsed as “no travel content” now produces the right hotel + dates + total.
• No-travel-content emails no longer report to Sentry — promotional mail that Claude correctly skipped was creating false-positive operator alerts.

Accessibility + parity pass

• Screen-reader labels on icon-only buttons— trip-card rename save / cancel, trip-card overflow menu, scheduled-scan row Pause / Edit / Delete, to-do panel add / cancel toggle, EditableCity save / cancel, share-link “ready” announcement.
• Escape cancels EditableCity to match the rest of the inline editors.
• Segment row actions reveal on keyboard focus (Edit / Confirm / Delete + the city-edit pencil) instead of being hover-only.
• Empty days surface “Add the first activity” CTA on desktop instead of a flat “No activities planned” placeholder.
• Mobile to-do detail sheet renders a Markdown preview under the Notes textarea, matching the desktop edit-todo dialog.
• Dialog inputs stop clipping the focus ring on the left (edit-todo, add / edit segment, html-import, suggest-meals).
• Schedule editor stores correct UTC during DST — a 9:15 AM PDT pick now writes 16:15 UTC, not 17:15.

Trust and polish

• RLS on every email_scan_* table captured in migration 0004 — idempotent and guarded for vanilla Postgres so CI integration tests still pass on a non-Supabase container.
• Routine [auth] supabase token not used … log gated behind DEBUG_AUTH=1 so steady-state Railway logs aren't drowned by Supabase JWT expiry / legacy Google access-token coexistence noise.
• Trip-card rename input auto-focuses when it appears.
• Stale service workers unregister in dev mode so a cached /m shell from a prior session doesn't masquerade as the live build.
• Mobile / desktop parity in costs editing and share-link error surfacing.

Under the hood

• Drizzle migrations 0003 – 0006 land the schedules + runs tables, RLS policies, the include_sublabels flag, and the time-of-day / day-of-week anchor columns.
• ts-node is now an explicit devDependency on server so a fresh install doesn't fail the migration runner.
• Shared expandLabelFilters helper keeps the manual /emails/scan route and the scheduled executor in agreement on how to expand a parent label/folder into its descendants.
• packIntoTracks helper centralises the timeline's overlap-aware lane packing for hotels, cruises, and rentals.
• SSRF-guarded URL fetch on the new /emails/import-shared endpoint — http(s) only, blocks loopback / RFC1918 / link-local / cloud-metadata hosts, 10s timeout, 1 MB cap, content-type filter.
• Tests grew from 948 → 967 — new server coverage for schedules CRUD, the cron tick, share-target routes, plain-text-preference parsing, and the cost-clear contract.

Thanks

Schedule one scan; never look at a confirmation email again. Onward to 1.2.x.

Multi-provider, end to end

• Sign in with Microsoft or Google via Supabase Auth. Both flows force the account picker so you never get silently signed in as the wrong identity.
• Outlook email scan alongside Gmail — point at a Mail folder (or nested folder like Inbox > Travel), the same Claude parser pulls flights, hotels, and reservations out. Inbox-only or all-mail toggle on both sides.
• Outlook Calendar sync alongside Google Calendar — push segments, all-day hotel blocks, IANA-typed flight events, and re-sync / unsync, with parity across desktop and mobile.
• Link multiple accounts on /settings/account — one Google + one Microsoft identity, with separate Mail + Calendar capability rows per provider. Disconnect cascades cleanly: unlinking a sign-in identity also removes its Mail / Calendar rows after an “are you sure” confirm.
• Inline provider pickeron calendar + email sync dialogs when you've connected more than one — defaults to your most-recently-used and remembers per-feature.

Backend rebuilt on Supabase

The product looks the same; underneath, it's a different system.

• Storage moved from Google Drive to Supabase Postgres. Trips, segments, todos, history, share-link metadata, push subscriptions, and OAuth refresh tokens now live in row-level-security-gated Postgres tables — not in a per-user Drive folder.
• Token refresh on the server— short-lived access tokens for Gmail, Microsoft Graph, and both calendars are minted from encrypted refresh tokens on demand, so a long-tabbed-open session doesn't fall over silently.
• InvalidAuthError as a typed signal across every connector — a revoked-at- Google or scope-stripped token surfaces a specific 4xx that the UI maps to the right reconnect screen, not a generic 500.
• Storage + connector contract tests — SupabaseStorage, InMemoryStorage, GoogleCalendarConnector, MicrosoftCalendarConnector, GmailEmailConnector, and MicrosoftEmailConnector all run the same shared test suites, so the two providers and the two storage backends can't drift apart.

Email scan polish

• Live progress— “Found N emails → Parsing X of M” as the scan runs, instead of a single spinner.
• Multi-trip auto-clustering on desktop — scanning an inbox that spans several trips now groups proposals by destination / dates instead of dumping a flat list.
• Better placeholder handling— TBD / open-date items are skipped silently instead of producing zero-day “trips”.
• Layover-aware titles— a SFO → NRT → BKK booking proposes “Bangkok”, not “Tokyo”.
• Provider + account stored on each parsed email so re-scans don't double-process the same thread across accounts.
• Per-folder Outlook listing including nested folders, so Inbox > Travel > 2026 is reachable.
• Anthropic 429 + Microsoft MailboxConcurrency retry so a transient upstream blip doesn't fail the whole scan.

Calendar sync polish

• Provider-aware dialogs that survive the dropdown-menu closing, no overlap, no mid-flow remount.
• Orphaned-event reuse on Outlook — if a calendar event lost its segment link, the next sync rebinds instead of duplicating.
• Time-zone correctnessverified by wire-format tests: flights carry per-endpoint IANA zones, hotels stay all-day, update-resync preserves the event's existing extended properties.

Mobile

• Microsoft + Outlook everywhere — mobile scan sheet, mobile calendar sync sheet, and the account-settings panel all carry the same multi-provider affordances as desktop.
• Email-scan sheet surfaces partial-results banners and stale-token recovery as step transitions, not silent failures.

Trust and polish

• Account settings page at /settings/account — see linked identities + capability rows, with primary-email sort and live cross-panel state refresh.
• Initials avatar fallback for accounts without a provider photo; Microsoft Graph photo support added for Microsoft sign-in.
• Diagnostic logging gated behind DEBUG_EMAIL_SCAN / DEBUG_CONNECTIONS / DEBUG_CALENDAR — production Railway logs are quiet by default; real anomalies still always surface.
• Hardened token writes — the server now rejects a Google-shaped token written to a Microsoft row (and vice versa) instead of silently corrupting the connection.

Under the hood

• Workspace packages renamed from @travel-app/* → @itinly/* (shared, api-client, server, web) with a one-shot localStorage key migration so existing browser state copies forward.
• Node ≥ 22.13required (pnpm 11's loader depends on node:sqlite).
• Vercel build config is now in a checked-in vercel.json instead of the dashboard UI.
• pnpm update-test-count keeps the README test count fresh; pnpm check-test-count runs in CI so it can't drift.
• server/.env.example audited + split — frontend-only NEXT_PUBLIC_* vars moved to apps/web/.env.example, the long-dead STORAGE_BACKEND=drive and STORAGE_POSTGRES_USERS paths removed.
• DriveStorage path fully removed (Phase 6 of the backend-migration plan) — mode: "drive", the per-user Drive folder layout, and the partial Drive → Postgres importer are all gone from the tree.

Thanks

The Drive era was good; the Postgres era is better. Onward.

Plan a trip

• Day-by-day view with inline segment editing, per-segment costs, and confirmation codes
• Timeline view — Hipmunk-style Gantt grid with swimlane / chronological toggle, hotels rendered as spanning bars, prints cleanly
• Map view — hotels, dining, activities, and transport endpoints as pins on Google Maps; KML export for Google My Maps
• Flight endpoints by IATA — typeahead over 1,178 commercial airports (search by code, city, name, or alias); auto-fills titles like JFK → NRT (JL 5)
• Embedded costs + dedicated Costs tab; categorized TODO tracking (meals / activities / research / logistics)

Auto-extract from email

• Gmail scan — point at a label, Claude parses confirmations into flights, hotels, restaurants, transport
• Email file import — paste or upload an .html / .eml for non-Gmail users
• XLSX import — one-shot import a complete trip from a OneNote-exported workbook (auto-detects column layouts, attaches Costs sheet entries to lodging segments)

Share, sync, export

• Per-trip share links with configurable visibility (costs, TODOs)
• Auto-share rules — share every existing and future trip with someone in one tap
• Google Calendar sync — push segments to any writable calendar; hotels and car rentals become all-day events; flights and trains carry per-city IANA time zones; re-sync updates, unsync removes (with a choice to delete or just unlink); available on desktop and mobile
• Export as Markdown, OneNote-compatible HTML, PDF, or iCal (.ics) with VTIMEZONE blocks for correct DST in Outlook and overnight-flight handling

Mobile (/m)

• End-to-end planning on mobile — create trips, edit metadata, add / edit / delete segments, edit day cities
• Mobile email scan sheet— Gmail → Claude → review → apply, with proposals for new trips when segments don't match an existing trip
• Map view and timeline view with rotation support
• Installable PWA — add to home screen on Android / iOS, launch standalone, read previously-loaded trips offline (mobile trip list dims trips not loaded on this device when offline)
• Calendar sync and share parity with desktop

Trust and polish

• Trip history (audit log) — every change recorded in an append-only History tab (segments added / edited / deleted, todos checked, dates rolled, day cities edited, field-level diffs, shares created / revoked, XLSX or email-scan imports). Reverse-chrono, grouped by day, capped at 500 entries per trip. Available to owners and contributors.
• Dark mode — Light / Dark / System toggle on desktop + mobile, follows OS preference, persists across sessions
• Demo mode at itinly.app/?demo=true — try it without signing in
• In-app confirm dialogs (no more native window.confirm); first-time onboarding hints; dismissible intro tour on first sign-in
• Optimistic mutations + Sonner toasts on every user-triggered action
• Locked brand palette with WCAG AA-verified contrast across all token pairings

Under the hood

• Next.js 15 + React 19 + TailwindCSS 4 + ShadCN UI on the frontend
• Express 5 + TypeScript on the backend; managed Postgres (Supabase) for trip data with per-user row-level security
• Claude API (claude-sonnet-4-6) for email parsing
• pnpm 10 monorepo orchestrated by Turborepo
• Google OAuth (auth-code + PKCE), with Gmail split onto a separate OAuth client to keep the primary client off CASA review
• Sentry on both web and server; per-user / per-trip log tagging on email-scan, calendar-sync, and trip routes
• Per-request CSP nonces, rate-limited auth + shared routes, pinned Access-Control-Allow-Origin
• Hosted on Vercel (web) + Railway (API) + Upstash Redis (share tokens) — all on free tiers

Recent fixes since 0.81.0

• Mobile share supports an optional recipient email (#236)
• Installed PWA rotates with the device; iPad portrait routes to /m (#238, #234)
• Mobile landscape timeline expands edge-to-edge; row labels stay on a single line (#240, #241)
• Slash-split city display + date range polish on mobile trip header (#239)
• Auto-share rules + share / trip-list / auth polish (#247)
• Version-bump workflow tolerates commit messages with shell metachars (#248)
• Use Railway's documented [skip-deploy] marker on auto-bump commits (#249)

Thanks

Built on Claude Code with a lot of iteration, a lot of mobile-portrait testing, and an unreasonable number of segment-color decisions. Onward to 1.x.