docs: install the CLI and the Agent from their releases - #3
Merged
Conversation
Both components now publish prebuilt archives, and neither page said so. The Stone CLI page opened its install section with `go build -o stone`, and the Agent page had no install section at all -- it went from "what the Agent is" straight to the credential lifecycle, leaving the reader to work out where a binary comes from. The Agent's subsection is deliberately unnumbered. Numbering it would renumber every section below it on that page, and the numbers are how the other pages refer to it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Both components now publish prebuilt archives, and neither page said so.
stone-cli.md§2 opened withgo build -o stone. It now leads with the prebuilt archives and keeps the source build after it, plus a line on the practical difference: a source build reportsdevfrom--version, a release build reports the tag.agent.mdhad no install section at all — it went from "what the Agent is" straight to the credential lifecycle. Added Getting the binary at the end of §1: the archive contents, the four targets, and the fact thatagent -service installresolves to systemd, a Windows service or rc.d, so there are no unit files to place by hand.The Agent's subsection is deliberately unnumbered. Numbering it would renumber every section below it on that page, and those numbers are how other pages refer to it — verified
## 2. Provisioning & Credential Lifecyclestill reads## 2afterwards.Companion PRs: stone-age-io/stone-cli#2, stone-age-io/agent#2.
🤖 Generated with Claude Code