Add AgentPlane to harness implementations#21
Open
densmirnov wants to merge 1 commit into
Open
Conversation
182de41 to
0d26785
Compare
Author
|
Quick update: I rebased this branch onto the current
|
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.
Hi - I would like to add AgentPlane to this list.
Disclosure: I maintain AgentPlane.
Why it fits:
AgentPlane is not a generic agent tool or model framework. It is a local, Git-native workflow control harness that makes task records, workflow policy, verification evidence, and closure state explicit repository artifacts for repo-local coding-agent work.
Suggested category:
Runtimes, Harnesses & Reference Implementations. This seems closest because the project is an inspectable implementation of a workflow-control harness rather than an article, benchmark, or generic agent framework.
Entry added:
AgentPlane - Git-native workflow control harness for repo-local coding-agent work. It makes task records, workflow policy, verification evidence, and closure state explicit repo artifacts, which is useful for auditable and resumable agent work.
Verification:
git diff --checkHappy to adjust category, wording, or remove if this is outside scope.