Skip to content

feat(tripo-3d): update China account workflow (0.1.5) - #157

Open
sunshakestrong wants to merge 8 commits into
zai-org:mainfrom
sunshakestrong:feat/tripo-3d-dual-region
Open

sunshakestrong wants to merge 8 commits into
zai-org:mainfrom
sunshakestrong:feat/tripo-3d-dual-region

Conversation

@sunshakestrong

@sunshakestrong sunshakestrong commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Plugin type / 插件类型

  • UI Plugin / UI 插件
  • Standard plugin / 普通插件
  • Not applicable / 不适用

Affected plugin / 涉及的插件:tripo-3d

What / 改动内容

tripo-3d@0.1.5 updates the workflow for mainland China Tripo accounts. The release scope of this PR is mainland China accounts. It retains the tripo server and https://developers.tripo3d.com/mcp OAuth endpoint used by the published 0.1.4 package.

  • A text-only request starts with a concept image after image-cost confirmation. The agent displays the image and waits for acceptance before planning and separately confirming 3D costs. User-supplied images go into the appropriate 3D plan. Users can explicitly request direct text-to-3D.
  • The skills select a model based on the required capabilities, distinguish humanoid and creature rig settings, and save a model to disk when requested.
  • The English and Chinese README and marketplace text explain the China account requirement. The marketplace entry and both manifests are version 0.1.5.

本次上架范围为 Tripo 国内站账号,延续已上架 0.1.4 的国内 MCP 授权入口。新版本包含概念图与 3D 分阶段确认、兼容性选模和交付规则的更新。

Dependencies and side effects / 依赖与副作用

The plugin uses Tripo browser OAuth through the China MCP endpoint. Its Node SessionStart hook reads the event on stdin and outputs workflow instructions. Requested uploads or downloads use a shell. Billed operations use the connected Tripo account's credits. The READMEs describe hosted MCP analytics and the non-credential X-Tripo-Distribution: zcode_plugin header. Existing VAST MIT-licensed plugin content is retained.

Verification / 验证

  • Source revision 23de1f5, based on upstream 19439c8. All 55 marketplace entries passed scripts/validate.py, and git diff --check origin/main...HEAD passed.
  • Compared the published 0.1.4 package and verified that 0.1.5 keeps the same China server ID and endpoint. The target ZIP was built with the repository's distribution packager and checked for CRC and member byte equality. SHA-256: 715f2bb5018320cd989c5b94a5561404e1aa0b136811005dca40b01fc2791878.
  • Ran the SessionStart hook in two time zones and checked the matching authorization instructions. The China endpoint gave the expected unauthenticated OAuth challenge.
  • Authenticated ZCode installation, upgrade and paid workflow checks remain pending. Full local workspace distribution remains pending because its Photocraft build requires rustup.

Self-check / 自查清单

  • Standard plugin type, package name and marketplace category / 已声明普通插件及市场分类
  • Matching package and marketplace versions / 包与市场条目版本一致
  • Equivalent English and Chinese README and metadata / 中英文文档与元数据等价
  • Network, credit use and telemetry documented / 已说明网络、积分消耗和遥测
  • Directory validation, target ZIP and diff checks passed / 目录、目标制品及差异校验通过
  • Full marketplace build and authenticated host acceptance / 全量构建及真实授权验收

Please review the updated China-account release scope for the official marketplace.

@sunshakestrong

Copy link
Copy Markdown
Contributor Author

CI note / CI 说明

The build check fails in "Build and test MCP Apps" while preparing the kicad Python runtime (No usable Python was found: neither uv nor a Python 3.11+ that has fastmcp, pydantic and numpy). The same step fails on main itself (run 40852244159 at 0cc58d6), so it is unrelated to this PR, which only touches plugins/tripo-3d, its marketplace entry and scripts/test/. Because that step stops the job, validate.py and build_dist.py did not run in CI; locally validate.py passes (52 plugins) and the tripo-3d 0.1.5 artifact builds.

build 检查失败在 kicad 的 Python 运行时准备步骤,main 分支自身(0cc58d6)也在同一步失败,与本 PR 无关。该步骤中断了后续的 validate.py / build_dist.py;本地 validate.py 已通过(52 个插件),tripo-3d 0.1.5 制品可正常构建。

@panda920

panda920 commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

Thanks for the contribution! This PR changes files that are maintained by the ZCode team and cannot be taken from external contributions: scripts/test/semantics.test.mjs, scripts/test/validate-tripo.py. Please drop those changes (plugin content, marketplace.json and docs are welcome) and push again; it will be picked up automatically.

🤖 Copy this prompt into Claude Code / Codex to fix it
You are updating my pull request #157 to github.com/zai-org/zcode-plugins (the ZCode plugin marketplace).
The maintainers' automated intake reported: the PR touches maintainer-owned files

Remove my changes to: scripts/test/semantics.test.mjs, scripts/test/validate-tripo.py

Fix it in this repository:
- New external plugins belong under external_plugins/<my-plugin>/; keep existing plugins in their current directory;
  never modify .github/, scripts/, tests/, .gitignore, .gitattributes or AGENTS.md.
- Follow CONTRIBUTING.md and AGENTS.md: the manifest lives at <plugin-directory>/.zcode-plugin/plugin.json,
  its name/version must match marketplace.json, names are kebab-case, keep the required i18n fields.
- Fetch the latest main of zai-org/zcode-plugins and rebase onto it; if marketplace.json conflicts,
  keep every existing entry and re-add mine.
- Run `python scripts/validate.py` until it passes, then force-push my PR branch.

@sunshakestrong
sunshakestrong force-pushed the feat/tripo-3d-dual-region branch from 074a2fb to 132ce8a Compare November 3, 2026 17:37
@panda920

panda920 commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

✅ Internal validation passed. A ZCode maintainer will review the change next; after acceptance, release checks run separately and this PR is closed automatically.

@panda920

panda920 commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

✅ Internal validation passed. A ZCode maintainer will review the change next; after acceptance, release checks run separately and this PR is closed automatically.

sunshakestrong and others added 7 commits November 19, 2026 07:35
…ution (0.1.5)

- Game/realtime recipes prefer P2; P1 stays optional for lower cost and
  speed, v3.1 for film/render/print. Rig defaults to v3.0, retopology
  smart_uv and tripo_smart_uv are separate billed workflows, fast textures
  require v3.5 and chat_image_1 is retired.
- The CLI path requires tripo-cli >= 0.8.0 (npx tripo-cli@0.8) and runs only
  when the user explicitly chooses it; no automatic fallback from MCP.
- MCP sends X-Tripo-Distribution: zcode_plugin; the SessionStart hook adds
  source/version and explicit model/billing rules.
- Keep the upstream 0.1.4 marketplace descriptions and mirror them into
  .claude-plugin/plugin.json so both manifests stay identical.

Co-authored-by: Cursor <cursoragent@cursor.com>
- Revised README and skill documentation to emphasize that the plugin operates solely through the Tripo MCP tools, eliminating any CLI path references.
- Clarified the model selection process, establishing P2 as the default for game/realtime topology, with P1 only used when explicitly chosen by the user.
- Updated hook rules to ensure PBR is off by default unless explicitly requested.
- Enhanced capability reference and game asset recipes to align with the new execution path guidelines.
…docs

Rigging passes the model per body type: v3.0 for bipeds and others, v2.5 (the official animal rig) for animals. The API's own default is v1.0-20240301 (biped only).

Same plugin content as the Tripo GLM plugin repository's 0.1.5 candidate; the version is unchanged.
… process

- Updated README and skill documentation to emphasize that a user's explicitly chosen compatible model takes precedence over usage-based defaults.
- Clarified billing and cost estimation processes, ensuring users are informed about unestimated steps and required confirmations.
- Revised hook rules to maintain PBR off by default unless explicitly requested, and detailed the implications of model selection on billing.
- Enhanced capability reference to reflect the latest changes in model handling and processing workflows.
Replace the "no data collection" note in both READMEs with what the deployed Tripo MCP server records, the declared non-credential X-Tripo-Distribution: zcode_plugin header, and what analytics exclude. The plugin version stays 0.1.5: the marketplace still serves 0.1.4.
…sh-only plugin

Add a second MCP server, tripo-global (https://openapi-mcp.tripo3d.ai/mcp),
next to tripo (https://developers.tripo3d.com/mcp); both declare
X-Tripo-Distribution: zcode_plugin. The skill and the SessionStart hook ask
which site the account is on, use the system time zone only to phrase that
question, and keep each task chain on one server.

Make the package English-only: drop README_CN.md and the zh-CN example
prompts, quote ZCode's English UI labels, and fill the required zh-CN
description with the English text. The category keeps validate.py's fixed
3D enum value.

Update the README for both servers, including the telemetry note. The
version stays 0.1.5: the marketplace still serves 0.1.4.
@sunshakestrong
sunshakestrong force-pushed the feat/tripo-3d-dual-region branch from 132ce8a to 8049f9e Compare November 19, 2026 13:37
@sunshakestrong sunshakestrong changed the title feat(tripo-3d): support China and international accounts, English-only package (0.1.5) feat(tripo-3d): support China and international accounts (0.1.5) Nov 19, 2026
@sunshakestrong sunshakestrong changed the title feat(tripo-3d): support China and international accounts (0.1.5) feat(tripo-3d): update China account workflow (0.1.5) Nov 19, 2026
@panda920

Copy link
Copy Markdown
Collaborator

✅ Internal validation passed. A ZCode maintainer will review the change next; after acceptance, release checks run separately and this PR is closed automatically.

@panda920

Copy link
Copy Markdown
Collaborator

✅ Internal validation passed. A ZCode maintainer will review the change next; after acceptance, release checks run separately and this PR is closed automatically.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants