added tools for searching/booking/add-ons for flights

[charlesmeng18]

Tools

Tool: Get Current Date

Tool: Search Flights from a flights.json (generated via generate_flights.py script)

Tool: Book Flights, save to reservations.json

Tool: Add-Ons to Existing Reservation

Frontier Data Modeling
Models the different services available to each of the Fares (aka Bundles)

Frontier Fares (Bundles)

• Basic
  • Services: None
• Economy
  • Services: Basic + Carry on, Standard seat selection, Refundability (no change/cancel fee)
• Premium
  • Services: Economy + Premium seat selection + Priority Boarding
• Business
  • Services: Premium + 2 checked bags + UpFront Plus Seating

Services

• Seating Options
  • Standard Seats
  • Stretch Seating
  • UpFront Plus
• Change/Cancel Fee Waived
• Priority Boarding
• Travel Insurance
• Refundability

[charlesmeng18]

Added the following domain modeling:

Cabins

• no separate cabin classes

Fares (Bundles)

• Basic
  • Services: None
• Economy
  • Services: Basic + Carry on, Standard seat selection, Refundability (no change/cancel fee)
• Premium
  • Services: Economy + Premium seat selection + Priority Boarding
• Business
  • Services: Premium + 2 checked bags + UpFront Plus Seating

Services

• Seating Options
  • Standard Seats
  • Stretch Seating
  • UpFront Plus
• Change/Cancel Fee Waived
• Priority Boarding
• Travel Insurance
• Refundability

[anishathalye]

Nice work! Started a Slack thread to talk about when we can merge this (README will need to be redone).

On the code side, a couple notes for when we get around to iterating on this:

• Took a quick glance at the code, it looks pretty good, it can be a useful starting point for someone on eng or ML team who can clean up the code before we merge it.
• The date should be dynamic instructions (Pydantic AI supports this) rather than a tool call, IMO.
• We might want to make the agent stateless across reboots of the backend (no on-disk JSON for reservations, instead switching to maintaining this in-memory across chat threads).

Before someone iterates on this code, I can take a closer look and give more feedback.

[anishathalye]

For future reference, status of tests:

[anishathalye]

The domain modeling isn't perfect, but given that our demos are very "shallow" (1-2 messages deep), this seems okay for now. Code quality for some of the vibe coded stuff isn't amazing, but good enough for now. If we think it's worth the effort, someone can improve this later.