feat(agent): streamline minimal harness prompt - #2359
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Streamline the stable Minimal Harness system prompt while preserving the cross-tool coding and safety contracts that are not expressible through individual tool schemas.
You are a helpful software engineer assistant.Type and Areas
Type:
Feature, prompt-policy refinement, test, and architecture documentation.
Areas:
Agent content assembly, Minimal Harness prompt policy, prompt catalog contracts, and Minimal Harness architecture documentation.
Motivation / Impact
The previous Minimal prompt repeated detailed tool instructions already supplied by the live tool descriptions and schemas. This increased prompt size and constrained model behavior without adding runtime enforcement.
The revised prompt keeps only stable persona and cross-tool rules that the schema or runtime cannot communicate on their own. Minimal remains a BitFun product profile with the same tool manifest, permissions, execution lifecycle, provider/model configuration, and stable prompt key. Balanced and other profiles are unchanged.
Verification
cargo test --locked -p bitfun-agent-content --test prompt_catalog_contracts— 4 passed, 0 failed.deepswe-bitfun-dsv4flash-max-minimal-prompt10-20260818-bitfun-0f850c7-pier-47adce3— all 10 trials completed with 0 agent exceptions; official verifier reward was 7/10. This validates live Minimal startup and execution for this sample, not broad product behavior or a final benchmark score.Reviewer Notes
minimal-harness-v1; only its prompt bytes and matching contract/documentation change.Checklist