You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why
Users will be able to use big-agi on a new tab without requiring them to locate the first instance.
Description
The current behavior is that if you open the application on a second tab, there is a message that says "It looks like big-AGI is already running in another tab or window. To continue here, please close the other instance first". If the first instance of the application is buried when someone has many tabs open, it becomes a challenge to locate the first instance.
The requested capability would be to not require the user to locate the first instance, but instead allow the user to start the new instance and doing so will simply terminate the first instance.
Requirements
If you can, Please break-down the changes use cases, UX, technology, architecture, etc.
Instead of forcing the user to go back to the first instance, the action could be to terminate the first instance and continue the usage on the latest instance
The text was updated successfully, but these errors were encountered:
@bensonrlee there's an improvement coming to this feature, but no multiple-tab support yet.
Bg-AGI is not a server-side application but a client-side web application as this gives us unparalleled speed and control for the user. We will need to have communication and conflict resolution between state stores in every open Tab before we can release this.
We have a solution but won't be able to work on it until 2.0 is launched.
Why
Users will be able to use big-agi on a new tab without requiring them to locate the first instance.
Description
The current behavior is that if you open the application on a second tab, there is a message that says "It looks like big-AGI is already running in another tab or window. To continue here, please close the other instance first". If the first instance of the application is buried when someone has many tabs open, it becomes a challenge to locate the first instance.
The requested capability would be to not require the user to locate the first instance, but instead allow the user to start the new instance and doing so will simply terminate the first instance.
Requirements
If you can, Please break-down the changes use cases, UX, technology, architecture, etc.
The text was updated successfully, but these errors were encountered: