Skip to content

Add Agent Message Queue to Community Plugins#22

Merged
internet-dot merged 1 commit into
mainfrom
feat/plugins-json
Mar 31, 2026
Merged

Add Agent Message Queue to Community Plugins#22
internet-dot merged 1 commit into
mainfrom
feat/plugins-json

Conversation

@internet-dot

Copy link
Copy Markdown
Collaborator

Summary\n- Add Agent Message Queue by @avivsinai to the Community Plugins list under Tools & Integrations\n- File-based inter-agent messaging with co-op mode, cross-project federation, and orchestrator integrations\n- Updates plugins.json with new entry and total = 27\n\nSupersedes #21 (closed due to merge conflict with #20).

@internet-dot internet-dot merged commit 35a0292 into main Mar 31, 2026
3 of 5 checks passed
@internet-dot internet-dot deleted the feat/plugins-json branch March 31, 2026 18:39

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the total plugin count in plugins.json from 26 to 27. However, the feedback indicates that the actual plugin entry is missing from the file, creating an inconsistency. Furthermore, plugins.json is a generated file that should not be edited manually; the recommended workflow is to update the README.md and run the regeneration script to ensure data integrity.

Comment thread plugins.json
"version": "1.0.0",
"last_updated": "2026-03-31",
"total": 26,
"total": 27,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The total count has been updated to 27, but the corresponding entry for "Agent Message Queue" is missing from the plugins array in this pull request. This results in an inconsistent state where the metadata does not match the actual number of plugins.

Additionally, plugins.json is a generated file (see scripts/generate_plugins_json.py). Manually updating it bypasses the source of truth in README.md and will likely lead to these changes being overwritten during the next build or regeneration process. The recommended workflow is to update the README.md first and then run the regeneration script to ensure both files are consistent and correctly formatted.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant