docs: automated documentation updates 2026-04-06#1375
Open
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
The following comment was made by an LLM, it may be inaccurate: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs refresh for 19:00 PDT. This PR updates documentation to match behavior introduced by commits from the last 24 hours.
Commits reviewed:
Why these docs changed:
LLM Providersdashboard where admins save shared credentials, choose models, and grant access to people or teams.packages/docs/introduction.mdx,packages/docs/team-provisioning.mdx, andpackages/docs/how-to-connect-a-custom-provider.mdxhad to be updated because they still described shared model management as unavailable or purely local.API Keysscreen with named keys, owner/admin access, and one-time secret reveal. The Cloud docs were incomplete because they did not mention API-key-based automation at all or warn that the full secret is only shown once.den-api, so narrative docs needed to point people to the current API reference instead of leaving route discovery implicit.API Referencetab. The provisioning and provider docs now point readers to that tab because the old pages had no path to the live endpoint reference.Documentation updates in this PR:
packages/docs/introduction.mdxto replace the outdated Cloud overview with the current Team Templates, Members, Shared Workspace, LLM Providers, API Keys, and API Reference surfaces.packages/docs/team-provisioning.mdxto replace the old template-only workflow with a current provisioning sequence that includes shared model access, API keys for automations, and the API reference tab.packages/docs/how-to-connect-a-custom-provider.mdxto distinguish OpenWork Cloud's sharedLLM Providersflow from workspace-levelopencode.jsonsetup for local or self-managed providers.Custom LLMsbeing "coming soon".Why this merits a docs update:
Validation:
git diff --checknode -e 'const fs=require("fs"); JSON.parse(fs.readFileSync("packages/docs/docs.json","utf8")); console.log("docs.json OK")'