hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 33 Packages Projects Releases Wiki Activity

Revert "docs(portal): the shared token store refreshes a login, it does not seed one"

Browse Source 
This reverts commit 0269ddb7ca.
This commit is contained in:
teknium1
2026-09-21 09:51:18 -07:00
committed by Teknium
parent 2632229bcf
commit f50d4b3423
2 changed files with 2 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
website/docs/integrations/nous-portal.md
View File

@@ -124,9 +124,7 @@ OAuth needs a browser, but the loopback callback runs on the machine where Herme
### Profile setup {#profile-setup}
If you use [Hermes profiles](../user-guide/profiles.md), the Portal refresh token is shared across profiles via a shared token store — but the store **refreshes an existing login, it does not create one**. Profiles are independent islands ([#111724](https://github.com/NousResearch/hermes-agent/issues/111724)), so a profile that has never signed in to the Portal has no Nous credentials of its own: at boot it fails closed with `Profile '<name>' is not connected to any AI provider yet` rather than silently adopting another profile's session.
Sign in **once per profile** with `hermes -p <name> portal` (alias for `hermes -p <name> auth add nous --type oauth`). When a shared Portal session already exists on the machine, that command offers to import it — one confirmation, no browser round-trip. After that first import the profile keeps its own state, and the shared store keeps its token current whenever any profile refreshes or re-logs in. `hermes profile create <name> --clone-all` from a signed-in profile also carries the Portal login (only single-use grants such as Anthropic/Codex are stripped from clones).
If you use [Hermes profiles](/user-guide/profiles), the Portal refresh token is automatically shared across all profiles via a shared token store. Sign in once on any profile, and the rest pick it up automatically — no need to repeat the OAuth flow per profile.
## Using the Portal day-to-day

4
website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/integrations/nous-portal.md
View File

@@ -120,9 +120,7 @@ OAuth 需要浏览器，但回调的 loopback 运行在 Hermes 所在的机器
### Profile 配置 {#profile-setup}
如果你使用 [Hermes profiles（配置文件）](../user-guide/profiles.md)，Portal 的 refresh token 会通过共享令牌存储在各 profile 间共享——但该存储**只刷新已有的登录，不会创建新登录**。各 profile 是相互独立的孤岛（[#111724](https://github.com/NousResearch/hermes-agent/issues/111724)），因此从未登录过 Portal 的 profile 没有自己的 Nous 凭证：启动时它会直接失败，提示 `Profile '<name>' is not connected to any AI provider yet`，而不会静默采用其他 profile 的会话。
**每个 profile 都需登录一次**，命令为 `hermes -p <name> portal`（即 `hermes -p <name> auth add nous --type oauth` 的别名）。如果机器上已有共享的 Portal 会话，该命令会提示导入——确认一次即可，无需再走浏览器流程。首次导入后该 profile 保留自己的状态，只要任一 profile 刷新或重新登录，共享存储便会让它的令牌保持最新。从已登录的 profile 执行 `hermes profile create <name> --clone-all` 也会一并带上 Portal 登录（克隆时只会剥离 Anthropic/Codex 这类一次性授权）。
如果你使用 [Hermes profiles（配置文件）](/user-guide/profiles)，Portal 的 refresh token 会通过共享令牌存储自动在所有 profile 间共享。在任意 profile 上登录一次，其余 profile 自动获取——无需为每个 profile 重复 OAuth 流程。
## 日常使用 Portal