You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
shoulderd update brings the binary to the newest release. A plugin or
release install has its binary replaced after a check against the
published SHA256SUMS, a go install build is installed again, and a
checkout or a container is told what to run. --check only asks and
exits 3 when a newer release is out.
The Claude Code plugin's SessionStart hook says, once a day, when a
newer release is out. It does not install it: the place where the harness
would is a stub in scripts/ensure-daemon.sh, empty on purpose.
The install guide has an update section: the binary, the adapter and the
process, and what moves each.
Notices in the editor, on by default. The daemon tells the person what
it does, as it does it: errors, advice injected with its text, facts
stored with their text, and facts superseded. warnings (a fact that
could not be kept, and why) and maintenance (tidying passes, with
counts) are named to switch on with SHOULDER_NOTIFY; all is
everything, off is silence. Claude Code shows them as systemMessage, the one hook field
addressed to the person and never the model; OpenCode shows them as
toasts. A notice is queued for the session it concerns and rides on that
session's next hook. shoulderd doctor prints the setting in use.
Fixed
shoulderd doctor told a plugin install that the plugin fetches a newer
release on the next editor start. It never did: the start script fetches
only when there is no binary at all. The hint now says shoulderd update.