Skip to content

fix(lr-c5ab): use npm install -g for in-app update instead of npx#151

Merged
akuehner merged 1 commit into
mainfrom
fix/lr-c5ab-update-global-npm
May 19, 2026
Merged

fix(lr-c5ab): use npm install -g for in-app update instead of npx#151
akuehner merged 1 commit into
mainfrom
fix/lr-c5ab-update-global-npm

Conversation

@akuehner
Copy link
Copy Markdown
Member

No description provided.

npx installs to a per-invocation cache directory that the process
manager (systemd / clagentic-daemon.sh) does not consult on restart.
The old approach spawned a new daemon from the npx cache, which then
got replaced by the stale global install the next time the supervisor
restarted the service — leaving the user on the old version.

Fix: run `npm install -g @clagentic/console@<tag>` then shut down
cleanly. The supervisor restarts from the updated global install, which
is exactly what the daemon script already resolves at
/usr/lib/node_modules/@clagentic/console/lib/daemon.js.

Also adds an update_failed broadcast on install error so the UI can
surface the failure rather than silently hanging.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@akuehner akuehner merged commit dde5457 into main May 19, 2026
@akuehner akuehner deleted the fix/lr-c5ab-update-global-npm branch May 19, 2026 20:32
@clagentic-release-bot
Copy link
Copy Markdown

This issue has been resolved in version 1.2.0 (stable).

To update, run:

npx @clagentic/console@1.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant