Generate a command from a script or a sentence with go-tool-base
Generating a Go command from a shell script or a plain sentence, and the repair agent that has to make the result build before you see it.
Tags
27 pages
CLI
Building a CLI with go-tool-base, part 5: a CLI that updates itself
Add self-update to a Go CLI: resolve releases per platform, compare versions, verify checksums and migrate config on upgrade.
Building a CLI with go-tool-base, part 4: an AI dungeon master
Build an AI dungeon master in Go: keep the model to prose only by putting the rules in the system prompt and the mechanics in typed tool calls.
Building a CLI with go-tool-base, part 3: expose your CLI to AI agents
Expose an existing Go CLI to AI agents over MCP without writing any AI code, using built-in commands. The agent reach equals the CLI reach.
Building a CLI with go-tool-base, part 2: configuration your tool can trust
Configuration for a Go CLI: precedence of flags over env over files, per-command embedded defaults, layered config merging and a strict mode.
Building a CLI with go-tool-base, part 1: scaffold and your first command
Install gtb, scaffold a releasable Go project, understand the generated and owned file split, then add your first command and run it.
clap's global flag, except in a passthrough subtree
Why a clap global flag stops working inside a passthrough subtree: the tokens get captured as trailing args before the flag is ever parsed.
Registering commands without life before main
Rust has no init or pre-main phase, so self-registering commands need another mechanism. Using a distributed slice to get the same shape.
rust-tool-base: the same idea, in a language that argues back
A sibling to go-tool-base rather than a port, filling the gap between excellent Rust crates and a coherent way to assemble them.
Where should a CLI keep your API keys?
Credential storage for a Go CLI: an env-var reference by default, an opt-in OS keychain, and plaintext only as a last resort and banned in CI.
