The greybeards' edge was never typing
Agentic AI gives senior engineers a lift and juniors a drag, which tempts firms to automate away the entry level entirely.
Categories
20 pages
Ai
AI didn't kill curl's bug bounty. The bounty did.
The cash prize for anything that looked like a finding was the accelerant, and AI only made plausible-looking reports free to produce.
Supporting a provider, or actually using it
A lowest-common-denominator AI interface throws away what each provider is good at. When to route through an abstraction and when to drop below it.
The AI provider that isn't an API
Five AI providers behind one Go interface, including one that shells out to a locally authenticated CLI for networks that allow no API calls.
AI conversations you can resume
Persisting an AI conversation in Go: snapshot the messages, prompt and tool metadata, and deliberately never the handlers or the API token.
An AI agent that has to make the build pass
Generate-and-hope does not work for codegen. Handing the draft to a repair agent with a fixed toolset that has to make build, test and lint pass.
Stop regex-ing the LLM's prose
Stop parsing an LLM's prose with regular expressions. Derive a JSON schema from your Go or Rust type so the schema and the type cannot drift.
Letting the AI call your Go functions
Tool calling and the reason-act-observe loop explained, and how to define a tool in Go so the schema comes from the type rather than by hand.
An AI interface that fits on one screen
You do not need LangChain in a command-line tool. A four-method chat interface can hide five providers, tool calling and structured output.
Your CLI is already an AI tool
A well-built CLI already has what an agent needs: named operations, descriptions and typed parameters. Exposing one over MCP takes no AI code.
