fix(simulator): Prefer build_run_sim for run intent #213
+60
−19
Conversation
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
Align agent guidance and simulator discovery hints so run or launch intent\ndefaults to build_run_sim while keeping build_sim as compile-only.\n\nThis avoids the common redundant sequence of running build_sim and then\nbuild_run_sim, which double-builds without adding value. Co-Authored-By: Claude <noreply@anthropic.com>
commit: |
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.
Prefer build-and-run as the default simulator path when intent is to run or launch, while keeping build as a compile-only option.
Agents were frequently chaining build + build-and-run, which causes redundant builds and slows down iteration. This change aligns the behavior across three high-signal surfaces: skill guidance, tool descriptions, and list_schemes next-step hints.
I considered changing every hint surface in one pass (list_sims, show_build_settings, and additional docs), but kept this PR focused to minimize regression risk while still shifting default behavior at the main discovery funnel.
This touches workflow guidance and tool metadata, so reviewers should focus on whether the compile-only vs run-intent distinction remains clear and consistent.