docs: catch sem-ai CLI reference up with current release#1120
Open
skipi wants to merge 1 commit into
Open
Conversation
Documents commands shipped since the page was last touched: signin (browser device-flow auth, with the token-reset caveat), context switch, SEMAPHORE_HOST/SEMAPHORE_API_TOKEN env overrides, task parameters (create --param-def, run --param/--branch/--pipeline-file), deploy update, and the Claude Desktop MCPB bundles attached to releases. Co-Authored-By: Claude Fable 5 <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
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.
The
sem-aiCLI reference had drifted behind the released CLI. This adds the missing pieces, verified against the currentsemaphoreio/sem-aimain (--helpoutput and source):sem-ai signin— browser device-flow auth (aliasessignup/login), now the first thing in Setup. Includes the caveat that approving a sign-in resets an existing account token, and points atsem-ai connectfor existing-token auth.sem-ai context switch— was missing from the context section.SEMAPHORE_HOST/SEMAPHORE_API_TOKENoverride~/.sem.yaml(useful for CI/containers).task create --param-def NAME[=DEFAULT]andtask run --param KEY=VALUE, plus the per-run--branch/--pipeline-fileoverrides.sem-ai deploy update— PATCH semantics, with examples..mcpbextension attached to each sem-ai release, as an alternative to the CLI install.Deliberately not documented:
sem-ai notification create— it currently exits withnot_implemented, so listing it would mislead.🤖 Generated with Claude Code