Multi-Agent Shared Protocol Blocks with API-Based Deployment


Summary:
Organizations running multiple Runbear agents (e.g., Ask_Sam, Ask_HR, Ask_Eng) need a way to maintain shared behavioral rules — identity resolution, circuit breakers, access control, response protocols — across all agents without manually updating each one individually.

Problem:
Today, every system prompt update must be applied manually per agent via the Runbear UI. When a fix is validated on one agent (e.g., a user name resolution bug), replicating it to other agents requires:

•   Copy/pasting the updated block into each agent manually
•   No version control or audit trail at the deployment layer
•   High risk of drift between agents over time

Requested Features:

1.  ​Shared Protocol Library​ — A workspace-level repository of reusable prompt blocks (e.g., identity-resolution.md, circuit-breaker.md) that can be referenced by multiple agents

2.  ​Agent Configuration API​ — A REST endpoint to programmatically read/write agent system prompts, enabling CI/CD integration (e.g., on GitLab MR merge → push updated shared blocks to all registered agents)

3.  ​Inheritance Model​ — Allow agents to inherit base protocols + override with agent-specific config, similar to how .cursorrules works in Cursor

Business Impact:
Reduces admin overhead, eliminates agent drift, and enables enterprise-scale governance of AI agent behavior.

Please authenticate to join the conversation.

Upvoters
Status

In Review

Board

💡 Feature Request

Date

2 days ago

Author

Patrick Codrington

Subscribe to post

Get notified by email when there are changes.