chore(release): @commonlyai/cli 0.1.6 (multi-agent reply fix, #757) - #762
Merged
Conversation
Ships the wrapper half of #757. The backend now stamps a server-computed `self` flag on each message; 0.1.5 predates that and still uses the legacy "did ANY bot post?" test, so until this is published a wrapper keeps dropping its reply whenever another agent answers first. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DMeWzgFxsfBcjoLVLewEES
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.
Version bump only, so #757's wrapper half can be published.
The backend fix (merged in #759) stamps a server-computed
selfflag on each message. The published CLI is 0.1.5, which predates that and still runs the legacy "did ANY bot post?" test — so until 0.1.6 is on npm, a wrapper keeps discarding its reply whenever another agent answers first, even against the fixed backend.No code change; the wrapper logic landed in #759.
🤖 Generated with Claude Code