docs(nest-skill): explain agent-owned git repos and automatic auth#1437
Open
tlongwell-block wants to merge 1 commit into
Open
docs(nest-skill): explain agent-owned git repos and automatic auth#1437tlongwell-block wants to merge 1 commit into
tlongwell-block wants to merge 1 commit into
Conversation
Managed agents hit a wall creating git repos: they assumed the human had to own the repo and run repos create with a private key. Neither is true — repos create signs with the agent's own key (agent owns the repo) and the git-credential-nostr helper handles NIP-98 auth automatically, so no key ever touches a git command line. Add a short Git Repositories section to the nest skill covering ownership, the automatic credential helper, the clone-URL owner segment, and the announce+push flow. Co-authored-by: Tyler Longwell <tlongwell@block.xyz> Signed-off-by: Tyler Longwell <tlongwell@block.xyz>
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.
What
Adds a short Git Repositories section to the managed-agent nest skill (
desktop/src-tauri/src/managed_agents/nest_skill.md).Why
A managed agent (and its human) got stuck trying to create a git repo — they assumed the human had to own the repo and run
repos createwith a private key, and went in circles. Both assumptions are wrong:repos createsigns the announcement with the agent's own key, so the agent owns the repo. The clone-URL owner segment is the agent's own pubkey (hex, not a username).git-credential-nostrhelper, so plaingit clone/push/pullwork over NIP-98. No private key ever touches a git command line, and the human never needs to hand over a key.The nest skill previously covered relay/CLI mechanics but said nothing about git — exactly the gap that bit. Four lines close it.
Scope
One section, 4 inserted lines. No behavior change — documentation only.
Sources:
docs/git-on-object-storage.md,crates/git-credential-nostr/README.md,crates/buzz-dev-mcp/src/shim.rs(harness credential-helper wiring).