Describe the bug
When using a custom agent across two different communities in Buzz, the agent does not remain active in both communities. Switching between the communities appears to cause the custom agent to restart or disconnect.
The custom image icon added to the agent also disappears. If the agent is restarted in one community, the agent in the other community then requires another restart. This makes it appear that a custom agent cannot remain active across multiple communities at the same time.
To Reproduce:
- Create or configure a custom agent with a custom image icon.
- Add the custom agent to two different communities.
- Open the first community and start or restart the custom agent.
- Switch to the second community.
- Observe that the custom agent needs to be restarted.
- Return to the first community.
- Observe that the agent may need to be restarted again.
- Check the custom agent icon and observe that the image may have disappeared.
Expected behaviour:
The custom agent should remain active and available in both communities without requiring a restart when switching between them.
The custom image icon should remain attached to the agent and display consistently across all communities.
Restarting or activating the agent in one community should not affect its availability or configuration in another community.
Supporting Material
Screenshots
Environment (please complete the following information):
- OS: macOS
- Buzz version: 0.4.22
- Application type: Desktop app
Additional context
I am currently testing the Buzz application with two communities using the same custom agent. The issue occurs consistently when moving between the communities.
The behaviour suggests that the agent's active state and custom icon may be stored at community level or overwritten when the same agent is activated in another community.
Describe the bug
When using a custom agent across two different communities in Buzz, the agent does not remain active in both communities. Switching between the communities appears to cause the custom agent to restart or disconnect.
The custom image icon added to the agent also disappears. If the agent is restarted in one community, the agent in the other community then requires another restart. This makes it appear that a custom agent cannot remain active across multiple communities at the same time.
To Reproduce:
Expected behaviour:
The custom agent should remain active and available in both communities without requiring a restart when switching between them.
The custom image icon should remain attached to the agent and display consistently across all communities.
Restarting or activating the agent in one community should not affect its availability or configuration in another community.
Supporting Material
Screenshots
Environment (please complete the following information):
Additional context
I am currently testing the Buzz application with two communities using the same custom agent. The issue occurs consistently when moving between the communities.
The behaviour suggests that the agent's active state and custom icon may be stored at community level or overwritten when the same agent is activated in another community.