Skip to content

armgit / hypit

Public Imported from GitHub
0

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

docs: document skill credential login flow

rponeab304d559ceb
diff --git a/docs/guide/skill.md b/docs/guide/skill.md
index 44b3f963..d19a9c3a 100644
--- a/docs/guide/skill.md
+++ b/docs/guide/skill.md
@@ -48,6 +48,39 @@ same Run to Studio or Build.
The initial presenter/product/brand change attached to a reconstruction remains inside reconstruction;
it is not routed through Revision. Revision begins only when the user later asks for another change.
+## Credentials and login
+
+Credentials are an environment gate for every production route, not a step deferred until a paid Build.
+The Skill defaults to HypiHub, does not ask the author to choose a Provider, and does not require copying an
+API key.
+
+The standard sequence is:
+
+```text
+select Runtime Profile → check HypiHub credential → explain and run OAuth when missing
+→ confirm login → hypit runtime up → verify WhisperX/other programs
+→ only then inspect media, call Gemini, author Source or Build
+```
+
+```bash
+hypit auth status hypihub.default --runtime hypit.runtime.json
+hypit auth login hypihub.default --runtime hypit.runtime.json
+hypit runtime up
+```
+
+When status reports that the writable OS credential is missing, the agent must explain that browser OAuth
+avoids copying an API key, login itself does not submit a paid generation, and an account without an active
+subscription can purchase one after signing in at [hypit.ai](https://hypit.ai). The agent runs
+`hypit auth login` and waits for the callback; it must not merely hand the command to the author or switch to
+the credentialless observer because no key was found.
+
+The session is stored in the local OS credential store and is reusable by other projects and later
+conversations. Only when the author explicitly requests an author-owned Provider may the agent configure
+`KIE_API_KEY`, the two Vertex Google variables, or `MIMO_API_KEY`, and it must identify that as the
+non-default path. Secrets never enter `.svml`, `.svs`, `.svrun`, Runtime Source, state JSON or logs. Before
+a paid Build, report every Provider and credential source, disclose the cost and wait for approval; if a
+credential or model is unavailable, return to the environment gate and guide the author to HypiHub.
+
## Shared phases
### 1. Environment and durable start
diff --git a/docs/zh/guide/skill.md b/docs/zh/guide/skill.md
index 01ed1617..fe446e1f 100644
--- a/docs/zh/guide/skill.md
+++ b/docs/zh/guide/skill.md
@@ -45,6 +45,34 @@ description: Hypit skill 如何把描述或参考视频变成可检查、可恢
复刻请求中一开始就附带的人物、产品、品牌替换仍属于复刻;只有后续再次提出自然语言修改才进入 Revision。
+## 凭据与登录流程
+
+凭据是每条生产路径的环境门禁,不是付费 Build 时才处理的事项。Skill 默认使用 HypiHub,不先询问
+Provider,也不要求用户复制粘贴 API key。
+
+标准顺序:
+
+```text
+选择 Runtime Profile → 检查 HypiHub 凭据 → 缺失时说明并执行 OAuth 登录
+→ 确认登录成功 → hypit runtime up → 检查 WhisperX/其他程序健康
+→ 才能读媒体、调用 Gemini、写 Source 或 Build
+```
+
+```bash
+hypit auth status hypihub.default --runtime hypit.runtime.json
+hypit auth login hypihub.default --runtime hypit.runtime.json
+hypit runtime up
+```
+
+当 status 显示可写的 OS 凭据缺失时,agent 必须说明:浏览器 OAuth 不需要复制 API key,登录本身不会
+提交付费生成;没有有效订阅的账号可以登录后在 [hypit.ai](https://hypit.ai) 购买。然后 agent 直接
+执行 `hypit auth login` 并等待回调成功,不能只把命令交给用户,也不能因为缺 key 改走无凭据 observer。
+
+登录会话保存在本机 OS credential store,可被其他项目和后续会话复用。只有用户明确要求自有 Provider
+时,才配置 `KIE_API_KEY`、Vertex 的两个 Google 变量或 `MIMO_API_KEY` 等,并明确这是非默认路径;
+secret 永不写入 `.svml`、`.svs`、`.svrun`、Runtime Source、状态 JSON 或日志。付费 Build 前必须
+先列出 Provider/凭据来源、披露费用并获得批准;凭据缺失或模型不可用时,回到环境门禁并引导 HypiHub。
+
## 共用阶段
### 1. 环境与持久化启动