Repository navigation
feat: add composable Go agent packages and a durable runtime - #2
Merged
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.
Agents can now be authored and distributed as ordinary Go modules, then composed and executed by GoLangGraph. The new experimental contract is Go-native: it has no TypeScript runtime dependency or Standard Agent Specification compatibility claim.
golanggraph package initandpackage inspect, three independent example agent modules, and an offline/live consumer demonstrating both reusable composition and application-owned graph workflows.Validation: full repository tests with the race detector passed locally and in CI on Go 1.27.4. CI reports 71.1% package source coverage (65% floor). Independent modules, CLI-generated module compilation, manifest fuzzing, separate-process restart/deduplication, Linux/Windows builds, and dependency-boundary checks passed. Lint and GoSec are clean. Govulncheck on Go 1.27.4 reports no reachable vulnerabilities.
The API remains experimental. One Runtime must own a thread's writes; external effects and parent/child commits are not a distributed transaction. Modules are local development versions pending a separate SDK release. Offline tests do not certify a live model.