docs: harness-vs-Code-Puppy feature compatibility matrix - #807
Open
mpfaffenberger wants to merge 1 commit into
Open
docs: harness-vs-Code-Puppy feature compatibility matrix#807mpfaffenberger wants to merge 1 commit into
mpfaffenberger wants to merge 1 commit into
Conversation
The redundancy sweep behind the ToolOutputLimits adoption (#806): which pydantic-ai-harness capabilities can replace hand-rolled Code Puppy code, tiered by adoption effort, with a suggested attack order and the upstream gaps each big migration needs first.
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.
The full redundancy sweep that motivated #806 (ToolOutputLimits adoption), preserved from the closed #805.
Maps every pydantic-ai-harness capability against its Code Puppy counterpart: what is already adopted (compaction), what is adoptable now, what needs glue, what needs upstream gap proposals first (FileSystem undo/permission/backend seams, Shell UI event taps, SubAgents session continuity), and what stays app-side. Ends with a suggested attack order so follow-ups land in dependency order.