refactor(sdk): harness profiles for provider/model config#2484
Merged
Mason Daugherty (mdrxy) merged 36 commits intomainfrom Apr 10, 2026
Merged
refactor(sdk): harness profiles for provider/model config#2484Mason Daugherty (mdrxy) merged 36 commits intomainfrom
Mason Daugherty (mdrxy) merged 36 commits intomainfrom
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.
Calling refactor since this has no user-facing impact.
Consolidate provider-specific logic (hardcoded
if model.startswith(...)branches, per-provider kwargs, prompt tweaks) into a declarative, internal-onlyHarnessProfileregistry. No user-facing API changes.Each provider or exact model spec can register a profile that customizes init kwargs, system prompts, tool descriptions, tool exclusions, and middleware — eliminating scattered conditionals. Subagents resolve their own profile from their model, so mixed-provider setups get correct behavior automatically.
Changes
HarnessProfiledataclass and a registry withexact-spec -> provider-prefix -> empty-defaultlookup and merge semanticsexcluded_toolsunions)create_deep_agent: applytool_description_overridesto user tools,FilesystemMiddleware, andSubAgentMiddleware; assemble system prompt frombase_system_prompt+system_prompt_suffix; injectextra_middlewareinto all three middleware stacks (main, general-purpose subagent, per-subagent)_ToolExclusionMiddlewarethat stripsexcluded_toolsfromrequest.toolsbefore the model sees them — placed late in the stack so it catches both user-supplied and middleware-injected tools