Parity means doing the opposite
rust-tool-base needed go-tool-base's control over which commands an AI agent may call. Closing the gap meant doing the opposite of what Go did.
Categories
103 pages
Pioneering
Notes from active builds: the design decisions, war stories and how-it-works of whatever I'm making right now.
An agent is a loop with real tools and a fence
An agent is a model in a loop with tools it can really call and results it can really see. Taking the ReAct pattern apart in go-tool-base.
Publish your key where the platform can't touch it
If the platform hosting your code also hands out the key that verifies it, the signature proves nothing. Where to publish a public key instead.
Desktop apps don't paste
TikTok's OAuth flow wants you to copy a code out of a web page and paste it into a terminal. What it took to give keryx a native flow instead.
The marketplace I had to defend from my own attack surface
Opening a public marketplace for agent workflows meant publishing an attack surface, and then having to defend it from my own convenience.
The framework doesn't know where your signing key lives
Where a signing key lives is the most provider-specific decision in the whole business, so the framework deliberately refuses to have an opinion.
Merged in five days, open in seven hundred
Leaving a healthy dependency: cockroachdb/errors predates Go 1.20, so its Join hides the aggregate and everything below it goes missing.
The version pin you can't lower
A standard-library security fix forced a Go version bump, and then the release failed because the build image shipped an older toolchain.
A release is just another merge request
Moving off tag-on-merge releases, where a release is a side effect of merging, to a model where the release is itself a reviewable change.
The gateway that split my trace in two
Wiring OTel-native observability through a gRPC service with a REST gateway, and discovering the gateway had split a single trace into two.
