Repository navigation
Say which profile to use for a future depart_at - #88
Open
mattpodwysocki wants to merge 1 commit into
Open
mattpodwysocki wants to merge 1 commit into
mattpodwysocki wants to merge 1 commit into
Conversation
The profile guidance said only that "both profiles support `depart_at`", which is true but does not answer the question it raises. Asked which profile to use for a departure scheduled in the future with traffic-aware ETAs, the model reasoned that live traffic cannot help a future departure and recommended `driving` — the wrong answer, arrived at sensibly. Per the Directions API reference, `driving-traffic` with a future `depart_at` routes on "historical travel data and live traffic", with live traffic "gently mixed with historical data when the value for `depart_at` is close to current time". So a future departure is not a reason to drop to `driving`, and `arrive_by` remains the only one. Stated outright in both copies. The eval covering this went from 3/9 to 9/9 on both surfaces.
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Split out of #80.
The problem
The profile guidance said only that "both profiles support
depart_at". True, but it doesn't answer the question that raises.Asked which profile to use for a departure scheduled in the future when traffic-aware ETAs are still wanted, the model reasoned that live traffic cannot help a future departure and recommended
driving. Wrong answer, sensibly arrived at — the text gave it nothing to go on.The fix
Per the Directions API reference,
driving-trafficwith a futuredepart_atroutes on "historical travel data and live traffic", with live traffic "gently mixed with historical data when the value fordepart_atis close to current time".So a future departure is not a reason to drop to
driving, andarrive_byremains the only one. Now stated outright, in bothAGENTS.mdandreferences/web-directions-api.md.Measured
The eval covering this went from 3/9 to 9/9, on both the
skillandagentssurfaces.Test plan
npm run checkpassesmapbox-navigation-patternseval Add Mapbox search integration workflow skill #5 re-run on both surfaces🤖 Generated with Claude Code