How works right now AI assistants from the Hub (now Mission Control)? #8811
Unanswered
ivanhercaz
asked this question in
Help
Replies: 1 comment
-
|
Custom configs still existing, but are now located in your profile. We found that most users still use custom config.yaml in their repo instead of the hub. Trying to build a SaaS around this problem seemed less valuable for paying customers and this direction towards Mission Control seems more viable, but agreed a different use case. Open to feedback on this. But to reiterate all custom configs should work as is. We've just move the screens around and have it less discoverable.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I just see the latest news from Continue and see that the Hub has been replaced by Mission Control. It looks great! I have not read yet everything what involves this change, however, I am bit worried from how I was using the Hub and interested in how the extensions work right now regarding the login and load the custom AI assistants.
I have an AI assistant that I have configured in the Hub, to the login in different VSCode in different machines, so I can login and get the same configuration without having to maintain a configuration file per machine nor environment variables for secrets, etc. It is still working on the extensions! I have not see any issue yet.
However, in the Mission Control space, I didn't see any section dedicated to this so I am worry about:
Thanks in advance to Continue's team for the effort improving this great tool!
Regards
Beta Was this translation helpful? Give feedback.
All reactions