From 1659a92309696ee40c4ebc9f162ca2a513b5ed88 Mon Sep 17 00:00:00 2001 From: Steve Yegge Date: Fri, 26 Dec 2025 17:05:53 -0800 Subject: [PATCH] docs: Update sling help text to reflect pinned beads (not hook files) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- internal/cmd/sling.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/internal/cmd/sling.go b/internal/cmd/sling.go index 36d855d8..844a7a49 100644 --- a/internal/cmd/sling.go +++ b/internal/cmd/sling.go @@ -51,13 +51,13 @@ Natural language args (for LLM executor): gt sling beads-release --args "patch release" gt sling code-review gt-abc --args "focus on security issues" -The --args string is stored in the hook and shown to the executor. +The --args string is injected into the prompt and shown to the executor. Since the executor is an LLM, it interprets these instructions naturally. When the first argument is a formula (not a bead), sling will: 1. Cook the formula (bd cook) - 2. Create a wisp instance (bd wisp) - 3. Attach the wisp to the target's hook + 2. Create a wisp instance (bd wisp create) + 3. Pin the wisp to the target (bd update --status=pinned --assignee=) 4. Nudge the target to start Formula-on-bead scaffolding (--on flag):