Skip to content

docs: clarify difyctl reference and agent auth wording (#831) (backport to release/1.15.0)#832

Merged
RiskeyL merged 1 commit into
release/1.15.0from
backport/release/1.15.0/pr-831
Jun 29, 2026
Merged

docs: clarify difyctl reference and agent auth wording (#831) (backport to release/1.15.0)#832
RiskeyL merged 1 commit into
release/1.15.0from
backport/release/1.15.0/pr-831

Conversation

@RiskeyL

@RiskeyL RiskeyL commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to release/1.15.0:

- reference/apps: drop the inaccurate "per-node" qualifier on metadata.reasoning
- reference/auth-and-contexts: rename the "sealed-file" fallback to "protected file"
- integrate-agents/auth-for-agent-deployments: point the keychain dead-end to sign-in Option 1

(cherry picked from commit 5ec724e)
Copilot AI review requested due to automatic review settings June 29, 2026 18:11
@RiskeyL RiskeyL self-assigned this Jun 29, 2026
@dosubot dosubot Bot added size:S This PR changes 10-29 lines, ignoring generated files. documentation Improvements or additions to documentation labels Jun 29, 2026
@RiskeyL RiskeyL merged commit 407105a into release/1.15.0 Jun 29, 2026
6 of 7 checks passed
@RiskeyL RiskeyL deleted the backport/release/1.15.0/pr-831 branch June 29, 2026 18:13

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This backport updates Dify CLI (difyctl) documentation wording across English, Chinese, and Japanese to better reflect token storage behavior, agent authentication guidance, and the shape of metadata.reasoning in app run output.

Changes:

  • Reworded metadata.reasoning output description to remove the “per-node” qualifier.
  • Updated token-storage fallback wording (“sealed file” → “protected file”) in auth/context docs.
  • Clarified agent deployment auth guidance when OS keychain storage prevents exporting tokens.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
zh/cli/reference/auth-and-contexts.mdx Updates wording for the token storage fallback in contexts/auth reference.
zh/cli/reference/apps.mdx Adjusts metadata.reasoning wording in stdout format table.
zh/cli/integrate-agents/auth-for-agent-deployments.mdx Clarifies what to do when tokens.yml is absent due to keychain capture.
ja/cli/reference/auth-and-contexts.mdx Updates wording for the token storage fallback in contexts/auth reference.
ja/cli/reference/apps.mdx Adjusts metadata.reasoning wording in stdout format table.
ja/cli/integrate-agents/auth-for-agent-deployments.mdx Clarifies what to do when tokens.yml is absent due to keychain capture.
en/cli/reference/auth-and-contexts.mdx Updates wording for the token storage fallback in contexts/auth reference.
en/cli/reference/apps.mdx Adjusts metadata.reasoning wording in stdout format table.
en/cli/integrate-agents/auth-for-agent-deployments.mdx Clarifies what to do when tokens.yml is absent due to keychain capture.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

---

`difyctl` can hold sign-ins for several Dify hosts and accounts at once. Each host and account pair is a context: its metadata lives in `hosts.yml` in the [config directory](/en/cli/reference/environment-variables), and its bearer token lives in your OS credential store (with a sealed-file fallback).
`difyctl` can hold sign-ins for several Dify hosts and accounts at once. Each host and account pair is a context: its metadata lives in `hosts.yml` in the [config directory](/en/cli/reference/environment-variables), and its bearer token lives in your OS credential store (with a protected file fallback).
> 本文档由 AI 自动翻译。如有任何不准确之处,请参考 [英文原版](/en/cli/reference/auth-and-contexts)。

`difyctl` 可同时保持对多个 Dify 主机和账户的登录状态。每一对主机和账户构成一个上下文:其元数据保存在 [配置目录](/zh/cli/reference/environment-variables) 下的 `hosts.yml` 中,其 bearer token 则保存在操作系统的凭据存储中(并以密封文件作为回退方案)。
`difyctl` 可同时保持对多个 Dify 主机和账户的登录状态。每一对主机和账户构成一个上下文:其元数据保存在 [配置目录](/zh/cli/reference/environment-variables) 下的 `hosts.yml` 中,其 bearer token 则保存在操作系统的凭据存储中(并以受保护文件作为回退方案)。
> このドキュメントは AI によって自動翻訳されています。不正確な部分がある場合は、[英語版](/en/cli/reference/auth-and-contexts) を参照してください。

`difyctl` は、複数の Dify ホストとアカウントへのサインインを同時に保持できます。各ホストとアカウントの組み合わせが 1 つのコンテキストです。そのメタデータは [設定ディレクトリ](/ja/cli/reference/environment-variables) 内の `hosts.yml` に保存され、bearer token は OS の認証情報ストアに保存されます(封印ファイルへのフォールバックあり)。
`difyctl` は、複数の Dify ホストとアカウントへのサインインを同時に保持できます。各ホストとアカウントの組み合わせが 1 つのコンテキストです。そのメタデータは [設定ディレクトリ](/ja/cli/reference/environment-variables) 内の `hosts.yml` に保存され、bearer token は OS の認証情報ストアに保存されます(保護されたファイルへのフォールバックあり)。
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport documentation Improvements or additions to documentation size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants