feat: add Aegis to ACP registry#292
Conversation
|
👋 Gentle ping — this PR has been open since May 10 with no CI checks triggered. I noticed other registration PRs are being merged daily (e.g. #299, #298, #297). Is there anything we need to adjust in For context: Aegis is an enterprise orchestration middleware for Claude Code — REST API, MCP, RBAC, audit trail, web dashboard. npm: Thanks! 🙏 |
|
👋 Gentle follow-up — pinging again since the last check on May 12 (thank you @OneStepAt4time for the initial ping). Our PR has been open since May 10 with no CI checks triggered, while other registration PRs continue to be merged regularly. Is there something specific in our submission that needs attention? We are happy to adjust anything to move this forward. Thanks for your time! |
- Add Aegis agent.json with proper registry schema - Include monochrome 16x16 SVG icon - Version: 0.6.7 - Distribution via npx package @onestepat4time/aegis@0.6.7 mcp Resolves #3018 - Critical for ACP ecosystem distribution Closes agentclientprotocol#292
OneStepAt4time
changed the title
Aegis is licensed under AGPL-3.0, not MIT. The agent.json had an incorrect license field. This aligns with the actual repository license.
|
👋 @anna239 — fifth check-in. Quick update: I just pushed a fix to correct the PR has been open since May 10 (15 days). CI still hasn't triggered on our side. We've seen many newer PRs merged in the meantime (#302, #301, #300, #316, #319, etc.). Is there anything else we can adjust to move this forward? We're happy to iterate. Thanks for your time! 🙏 |
|
👋 @ignatov — reaching out to you directly since we have not heard back on this PR after multiple check-ins with @anna239 over the past 15 days. Context:
We are happy to make any changes needed. Is there something specific blocking this registration? Thanks for your time. |
2 participants
Register Aegis
Adds Aegis to the ACP registry.
agent.json
npx @onestepat4time/aegis@0.6.7 mcpChecklist
@onestepat4time/aegis)Closes OneStepAt4time/aegis#3018