[codex] add node logs view#40
Merged
Merged
Conversation
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
1 participant
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.
Summary
amesh logsfor tailing the installed user service journalameshCLI besideamesh-nodeRoot Cause
OpenClaw/ACPX failures were only visible in local daemon logs, so operators could see an unhealthy node without enough context in the dashboard. The release artifact also only installed
amesh-node, which left no convenient installed CLI for log access. Separately, the main artifact workflow exposed a flaky ACPX stream test helper that could return empty stdout in CI.Validation
go test ./...corepack pnpm checkbash -n install-amesh-node.sh scripts/test-install-amesh-node.shbash scripts/test-install-amesh-node.sh