Automated Provisioning for Config

[amithkk]

Validations

• [X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
• [X] I'm not able to find an open issue that requests the same enhancement

Problem

In an enterprise setting, it'd be great to be able to provision continue from some sort of "provisioning url" that the user can choose to enter as part of the onboarding flow. This would enable an enterprise to push down model urls, limited access keys, customized prompts and more in a centralized manner. This could also allow for customising configuration centrally for users that have specific requirements

Solution

This would probably require an extended discussion to flesh out, if this feature makes sense for continue. However, stating some nice-to-haves to begin:

• Ability to select "Provision from URL" on continue's onboarding flow
• A standard schema for the provisioning API could be defined. The provisioning API should probably be able to authenticate via OAuth and store tokens
• On each start, continue should contact the provisioning API to retrieve updates to the configuration.

[byjrack]

So that sort of stuff can get fun with proxies (or absence of), vpn race conditions, spoofing risk, etc.

For policy type controls I tend to recommend systems just use native platform policy management with would be windows registry (gpo/mdm) and managedprefs (mobileconfig) for mac. Linux is a bit of a free for all though in that space though there are some conventions that have been adopted, but probably would say a config file. So the organization would stage the controls in the conventional location and the Extension would respect configurations in those locations similar to Chrome, Grammarly, Windows, etc.

Otherwise packing in a config with the upstream installer also may work well.