Catching up with crush run
Did you know that you can Crush in a non-interactive manner? It's easy as crush run.
crush run "what's the best tui framework for go?"That’s been a thing for a while. Starting with this release you can pickup sessions non-interactively thanks to an awesome feature by @seroperson:
--continue(-C): continue last session--session(-s): continue a specific session
# Continue a previous session
crush run --session {session-id} "um, can you repeat that?"
# Continue the most recent session
crush run --continue "tell me more"How can you find your session ID? You can use the session management commands we added 4 days ago. In short:
# List all sessions (ordered by most recent)
crush session list
# Alternatively output JSON, useful for scripts, etc.
crush session list --jsonThe week is just started. See ya in a few!
Charm ✨
Changelog
New!
- fad58e2: feat: be able to continue non-interactive sessions (#2401) (@seroperson)
Fixed
- b05a4ad: fix(ui): render nested tools consistently across states (@meowgorithm)
- efb52db: fix(vercel): fix validation of api keys for vercel (#2415) (@andreynering)
- c9efb20: fix: keep original order when filtering models (#2416) (@andreynering)
Other stuff
- a1fc44b: chore(events): add events for the CLI session series of commands (#2408) (@meowgorithm)
- 9a5a510: ci(labeler): add vercel label (@andreynering)
- 6e56a7f: lint: modernize new pointer creation (e.g. new(true)) (@meowgorithm)
Verifying the artifacts
First, download the checksums.txt file and the checksums.txt.sigstore.json file files, for example, with wget:
wget 'https://github.com/charmbracelet/crush/releases/download/v0.50.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.50.0/checksums.txt.sigstore.json'Then, verify it using cosign:
cosign verify-blob \
--certificate-identity 'https://github.com/charmbracelet/meta/.github/workflows/goreleaser.yml@refs/heads/main' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
--bundle 'checksums.txt.sigstore.json' \
./checksums.txtIf the output is Verified OK, you can safely use it to verify the checksums of other artifacts you downloaded from the release using sha256sum:
sha256sum --ignore-missing -c checksums.txtDone! You artifacts are now verified!
Thoughts? Questions? We love hearing from you. Feel free to reach out on X, Discord, Slack, The Fediverse, Bluesky.