Repository navigation
docs: add Suno Seedance HappyHorse GPT Image and Nano Banana guides - #837
acedatacloud-dev wants to merge 4 commits into
Conversation
|
@acedatacloud-dev is attempting to deploy a commit to the LibreChat's projects Team on Vercel. A member of the Team first needs to authorize it. |
2026-11-08 compatibility and navigation follow-upThis now fixes the current sidebar gate rather than only waiting on the Vercel preview: review head The already published v0.1.0 service packages also pass the current upstream deployment-loader seam ( Could a documentation maintainer review the five guide entries plus the translated navigation changes, and approve the fork workflow when appropriate? The Vercel status currently requests authorization from the existing LibreChat project team; no access expansion is needed on our side. If the preferred discovery surface is a different guide/category, please point us to that location and we can narrow this existing PR. Related model-config contribution remains LibreChat-AI/librechat-config-yaml#94 ; it is an opt-in collection entry, not a default-provider claim. No duplicate package upload, new paid request or repeated submission was made. |
Adds five individually titled MCP/Agent Plugin guides and discovery cards: Suno, Seedance, HappyHorse, GPT Image and Nano Banana by Ace Data Cloud. Names start with the services users search for, while the introduction makes clear these are independent Ace-provided integrations, not service-brand or LibreChat-maintainer official plugins.
Guides explain the current experimental Agent Plugins operator-install path, per-instance discovery, account register/sign-in/General application, OAuth and separate personal Token routes, service access/price/balance, same-ID asynchronous results and errors. They reuse real redacted Ace Console screenshots plus an existing official LibreChat settings screenshot (v0.8.2, explicitly labeled as a reference, not an Ace run). No fabricated success media or installation claim.
Package source: AceDataCloud/LibreChatPlugins#1 is now MERGED. Public release v0.1.0: https://github.com/AceDataCloud/LibreChatPlugins/releases/tag/v0.1.0 . The five independent ZIPs include license/attribution, English/Chinese guides and screenshots, plus SHA256SUMS; every public asset was downloaded and checked after publication. Commands now use the release/tag rather than the former review branch. The packages reuse five existing MCP implementations; no hook, shared credential, billing/fallback changes or duplicated generation code. Model provider collection is separately proposed in LibreChat-AI/librechat-config-yaml#94 .
Validation on the final changed docs:
pnpm typecheck,pnpm lint,pnpm check:config-version: passed.pnpm test: 421 passed / 37 files.pnpm build: success, 4,131 static pages. After correcting only the source-guide links to the actual review branch, final typecheck/lint/format still pass, but the repeat full build timed out exporting the unchanged/homepage after three 60-second attempts (4,085/4,131 pages generated). This final build is not claimed successful. No preview server/browser was opened.Acceptance is requested as official searchable documentation. No global plugin marketplace or default provider integration is claimed; actual host OAuth/install/generation and unique billing remain separate. All four UTM fields on account/pricing links only identify the integration source; no attribution-conversion claim.
Adversarial review not requested. No merge, production deployment or new paid model/media request performed.
2026-10-19 published artifact update
Own source PR #1 merged at
5395321770f06982bfcadbabdcefbb57ff007d89. Version v0.1.0 published with five service archives and SHA256SUMS. Every asset was downloaded from its public URL; hashes match, each archive has one plugin root with 14 files, complete local EN/ZH/graphics links and license/attribution. Four focused installer/archive tests and five native parser/schema checks passed at the reviewed source head; exact-head CI passed before merge.This update changes only the five guides' source/release references and installation text. MDX compile and whitespace check pass; no full-site test/build rerun for a link/text-only change. Earlier homepage timeout and external Actions/Vercel permissions remain separately documented. Actual LibreChat instance OAuth/host calls and official acceptance are still pending; public source/release is not claimed as global marketplace/default integration.
2026-11-08 current-base verification
Current review head
0862f0d493218c3aa06a36d07e2ff4d85b046b41fixes a concrete current-base gate:check:locale-metareported 13 stale translated MCP sidebars when these five guides were applied to maine521426d55955e2bdb4078927324503e01d59d0a. The existing upstream sync script added the five page slugs to each locale, preserving translated titles and all unrelated main content. No translations, packages or permissions were invented.Verification in an isolated latest-main checkout with this PR's files:
node scripts/sync-locale-meta.mjs --check: passed after the repair; 13 languages aligned.pnpm exec vitest run scripts/sync-locale-meta.test.mjs: 9 passed.pnpm typecheck,pnpm lint, changed-guide/sidebar Prettier, diff-check: passed.pnpm build: SUCCESS, 4,169 static pages. The new component-preview prerequisite initially hit a local package-feed 404; using the official npm registry with the unchanged frozen lockfile completed the install and build. No development server or browser was started. This supersedes the older local homepage timeout as current-base build evidence.loadPluginsFromDirectory→ plugin/skill/MCP loaders at LibreChat sourcef4154b649efa37e1345ccc517a4d8d1ed2178c82, real filesystem and published data-schema validators. Result: 5 Skills, 5 MCP configurations, zero diagnostics; a Suno-only directory loads only Suno. This is the deployment-loader seam in a standalone Node process, not a full database/HTTP/UI host or OAuth/tool-call test. Logger is no-op; the import adapter includes the exact pure helpers used by the loader. No package republish or paid request.The repository-level external-contributor workflow approval and Vercel team preview authorization remain separate maintainer controls. No expanded account role or new publisher identity is requested. Real OAuth/host tools/call, terminal media, unique billing and conversion remain unverified.