feat(agent): compact system prompt + guided search flow#80
Merged
DavidSchmidt00 merged 3 commits intomainfrom Apr 26, 2026
Merged
feat(agent): compact system prompt + guided search flow#80DavidSchmidt00 merged 3 commits intomainfrom
DavidSchmidt00 merged 3 commits intomainfrom
Conversation
Replace the verbose ~400-word system prompt with a ~180-word version that embeds an explicit one-question-at-a-time collection sequence before any slot search or handoff. - FIND SLOTS section: agent must collect club → date → time (one per reply), confirming even profile values; duration/court_type optional - handoff_to_find: resolve relative dates, split preferred_time into time_from/time_to, no follow-up message after call - Collapse redundant RULES + GOAL sections into a single header line - Profile section now says "confirm each before using" instead of "do NOT ask if already set" - tools.py: update_user_profile description lists preferred_time key; handoff_to_find description updated to match new prompt guidance Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replace the "always ask/confirm each field one by one" flow with a
context-aware approach:
- Info already in the user's message is used directly, never re-asked
- Saved club preference is offered as a suggestion ("Shall I search
at X?") rather than assumed or confirmed by asking
- Date + time both missing → ask for both in one question (fewer
round-trips)
- Duration + court type remain optional, sourced from message/profile
- Profile section guidance updated to match: use as defaults, suggest
club rather than assuming it
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Two issues from PR review: - FIND SLOTS now requires club_slug to be resolved via find_clubs_by_name before calling handoff_to_find — prevents Find Mode opening with empty club field when only a name was given in conversation - Profile-backed fields (date, time, duration, court_type) are now used silently as defaults when missing from the message, consistent with the profile section guidance; previously FIND SLOTS would ask even when a preferred_time was already saved Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
preferred_timeis split intotime_from/time_to; no follow-up message is sent afterhandoff_to_findTest plan
handoff_to_findand open Find Mode with all fields pre-filledfind_slotsdirectly🤖 Generated with Claude Code