diff --git a/packages/docs/how-to-connect-a-custom-provider.mdx b/packages/docs/how-to-connect-a-custom-provider.mdx index 116ddda7b..0d51d1f41 100644 --- a/packages/docs/how-to-connect-a-custom-provider.mdx +++ b/packages/docs/how-to-connect-a-custom-provider.mdx @@ -3,9 +3,11 @@ title: "Adding a custom LLM provider/model" description: "How to connect a custom provider with openwork" --- -Because `Openwork` is built on `Opencode` primitives, we support everything that you could modify in `.opencode.json`, like adding a [model](https://opencode.ai/docs/models/). However, our recommendation is to add it to `/path-to-your-workspace/.config/opencode/opencode.json` instead of modifying `~/.config/opencode/opencode.json`. +Because `OpenWork` is built on `OpenCode` primitives, you can still add your own provider config directly in `opencode.json`, including a custom [model](https://opencode.ai/docs/models/). For local or workspace-specific providers, we recommend updating `/path-to-your-workspace/.config/opencode/opencode.json` instead of modifying `~/.config/opencode/opencode.json`. -The reason for this is that you may want to support different models and permissions across several workspaces, specially when sharing it with a team. +This keeps different models and permissions isolated per workspace, which is especially helpful when you share setups with a team. + +If your organization manages providers in OpenWork Cloud, use the cloud flow instead: sign in, open `Settings > Cloud`, pick your org, and import the provider from the Cloud providers section. You can also sync or remove that imported provider from the same screen later. Inside `/path-to-your-workspace/.config/opencode/opencode.json`: ``` @@ -27,6 +29,6 @@ Inside `/path-to-your-workspace/.config/opencode/opencode.json`: } ``` -We've also built a [custom skill](https://share.openworklabs.com/b/01KNBQDQAK41VZSZDF5G9MW4MW) that you can import in Openwork following [this guide](/importing-a-skill). +We've also built a [custom skill](https://share.openworklabs.com/b/01KNBQDQAK41VZSZDF5G9MW4MW) that you can import in OpenWork following [this guide](/importing-a-skill). The following tutorial covers how to [import a custom provider using the skill](https://x.com/getopenwork/status/2034129039317995908?s=20). diff --git a/packages/docs/introduction.mdx b/packages/docs/introduction.mdx index 79b03ce39..3996e5e7b 100644 --- a/packages/docs/introduction.mdx +++ b/packages/docs/introduction.mdx @@ -2,15 +2,16 @@ title: "Introduction" --- -OpenWork Cloud enables team to move faster by making it easy to share your setup across your org. +OpenWork Cloud helps teams share the setup they want everyone to use across an org. [https://app.openworklabs.com/](https://app.openworklabs.com/) -- \*\*Team Templates: \*\*make it easy to share your setup across your team so they spend less time copy and pasting configs. -- \*\*Members: \*\*Makes it easy to invite members to your org. -- \*\*Shared Workspace: \*\*Are cloud instances you can use to perform long-running tasks or connect permanent connection to messaging channels like Slack or Telegram. -- \*\*Custom LLMs: \*\*(coming soon) +- **Team Templates:** share a starting point across your team so people spend less time copying configuration by hand. +- **Members:** invite teammates into your org. +- **Shared Workspaces:** run longer-lived cloud instances and keep integrations like Slack or Telegram connected. +- **Cloud providers:** import org-managed LLM providers into a workspace from `Settings > Cloud`, then sync or remove them later. +- **Skill hubs:** import shared skill bundles from your org into a workspace from `Settings > Cloud`. ![Image](/images/image-6.png) - \ No newline at end of file + diff --git a/packages/docs/team-provisioning.mdx b/packages/docs/team-provisioning.mdx index 3db999713..e142b5cfa 100644 --- a/packages/docs/team-provisioning.mdx +++ b/packages/docs/team-provisioning.mdx @@ -2,8 +2,12 @@ title: "Team Templates" --- -OpenWork Cloud enables team to move faster by making it easy to share your setup across your org. +OpenWork Cloud helps teams share the setup they want everyone to use across an org. -When your team starts with OpenWork they'll have the option to pick from one of the templates that is uniquely provisioned to them. +When your team starts with OpenWork, they can pick from templates that are provisioned for their org. -Creating a template is easy: simply create a setup as you would usually. Create your skills, connect your MCPs, and simply click on Share. \ No newline at end of file +Creating a template is simple: build the setup you want, create your skills, connect your MCPs, and click Share. + +Team provisioning can also include shared cloud resources. After signing in on desktop and selecting an org in `Settings > Cloud`, users can import org-managed skill hubs and cloud providers into the current workspace. + +Use templates when you want to share a complete starting point. Use cloud providers and skill hubs when you want the team to pull in centrally managed models or skills without manually editing local config files.