Background
This repository currently explains the agent harness concepts through Python implementations. I would like to contribute a Go companion implementation for developers who are more familiar with the Go ecosystem.
The goal would be to preserve the existing teaching objectives and chapter progression while expressing the same mechanisms in idiomatic Go. This would be a companion implementation, not a replacement for the Python version.
Proposed scope
I would start with a small pilot, such as s01_agent_loop, rather than submitting all chapters at once.
The pilot would:
- Preserve the behavior and teaching focus of the Python version.
- Keep the implementation minimal and easy to read.
- Avoid production-oriented abstractions and unnecessary hardening.
- Include Go-specific documentation and run instructions.
- Be reviewed manually and kept aligned with the corresponding Python chapter.
If the pilot is acceptable, the remaining chapters could be added incrementally in focused PRs.
Questions
- Would the maintainers accept a Go companion implementation in this repository?
- Should Go code live alongside each chapter, or under a separate top-level directory?
- Should the Go version cover all chapters eventually, or only selected chapters?
- Which Go version and dependency policy should the implementation follow?
I would appreciate feedback on the scope and directory structure before starting the implementation.
Background
This repository currently explains the agent harness concepts through Python implementations. I would like to contribute a Go companion implementation for developers who are more familiar with the Go ecosystem.
The goal would be to preserve the existing teaching objectives and chapter progression while expressing the same mechanisms in idiomatic Go. This would be a companion implementation, not a replacement for the Python version.
Proposed scope
I would start with a small pilot, such as
s01_agent_loop, rather than submitting all chapters at once.The pilot would:
If the pilot is acceptable, the remaining chapters could be added incrementally in focused PRs.
Questions
I would appreciate feedback on the scope and directory structure before starting the implementation.