Skip to content

fix: #1540

Closed
Closed

Description

@tianjiangtao

Pre-submission checklist | 提交前检查

  • I have searched existing issues and this hasn't been mentioned before | 我已搜索现有问题,确认此问题尚未被提及
  • I have read the project documentation and confirmed this issue doesn't already exist | 我已阅读项目文档并确认此问题尚未存在
  • This issue is specific to MemOS and not a general software issue | 该问题是针对 MemOS 的,而不是一般软件问题

Bug Description | 问题描述

https://github.com/MemTensor/MemOS/blob/main/apps/memos-local-plugin/README.md。我按这个文档尝试在hermes上安装memos-local-plugin,从文档上看应该是可以的,但是有以下的问题:
1、npm install -g @memtensor/memos-local-plugin,执行失败,因为这个包不存在。
2、手工clone项目到本地后,手工安装,发现web/ 和 site/ 目录下只有 README.md,没有任何前端源码(没有 src/、没有 vite.config.ts、没有 index.html、没有组件代码)。这些文件在打包发布时被 遗漏了。
所以无法使用。

How to Reproduce | 如何重现

按我写的就可以重现,或者按文档在hermes agent上安装就可以复现。

Environment | 环境信息

  • python 3.13

Additional Context | 其他信息

No response

Willingness to Implement | 实现意愿

  • I'm willing to implement this myself | 我愿意自己解决
  • I would like someone else to implement this | 我希望其他人来解决

Activity

  1. added
    ai:taskDispatched to AI coding agent | 已派发给 AI 编码任务
    on May 26, 2026
  2. Memtensor-AI commented on May 28, 2026

    @Memtensor-AI
    Collaborator

    ✅ AutoDev task 9c108f28727aaec1 completed.

    Summary: 已修复 issue #1540:在 apps/memos-local-plugin/README.md 的 Quick start 顶部增加 !IMPORTANT 警示,明确说明不要执行 npm install -g、解释原因(不会部署到 agent home、不会写 config.yaml、不会启动 bridge/viewer,且 tarball 只发布 dist/ + viewer/dist/ 不含源码),并新增 Troubleshooting 子节回应用户报告的两个具体症状("包不存在" 误解,以及 web//site/ 目录命名陈旧 —— 前者已重命名为 viewer/,后者已在 b683f8a 移除)。CHANGELOG 同步登记。仅文档变更,不影响代码与运行时。已 commit 到 autodev/MemOS-1540 并 push 到远端,待 scheduler 兜底创建 PR。

    Base branch: v2.0.16
    Branch: autodev/MemOS-1540
    Commit: 5e7befb
    PR: #1824
    Assigned to: @CarltonXiang, @syzsunshine219
    Reviewers: @CarltonXiang, @syzsunshine219

  3. added
    ai:codingAI agent is coding | AI 正在编码
    and removed on Jun 1, 2026
  4. Memtensor-AI commented on Jun 3, 2026

    @Memtensor-AI
    Collaborator

    🤖 AutoDev has picked up this issue and started working on it.

    Task ID: 968b9ae74b55fdef
    Working branch: autodev/MemOS-1540
    Target branch: main
    Workflow: opsp (analysis → coding → testing → PR)

    I will post the PR link here once done. If I need more information, I will ask in the comments.

  5. Memtensor-AI commented on Jun 3, 2026

    @Memtensor-AI
    Collaborator

    🚀 AutoDev task 968b9ae74b55fdef pushed commit.

    Summary: Fixed issue #1540 by updating the memos-local-plugin documentation to clarify the correct installation method and explain the confusion around web/ and site/ directories.

    What was fixed

    The issue reported two problems:

    1. Users tried npm install -g @memtensor/memos-local-plugin which failed or didn't work as expected
    2. After cloning the repo, users couldn't find frontend source in web/ and site/ directories

    Root cause

    The documentation didn't prominently explain that this package is a plugin, not a standalone CLI, and requires the install.sh script for proper deployment. Additionally, commit 26e7e3d renamed web/ to viewer/ and removed site/, but users looking at published tarballs or old documentation were confused.

    Changes made

    1. README.md: Added a prominent IMPORTANT callout in the Quick start section explaining:

      • Why npm install -g is wrong (doesn't deploy to agent home, no config.yaml, no bridge/viewer)
      • That the npm tarball ships built artifacts only (dist/ + viewer/dist/), not source code
      • That install.sh/install.ps1 is the only supported installation path
    2. README.md: Added a Troubleshooting subsection with two FAQs:

      • Explains the "package not found" message users might see
      • Clarifies that web/ and site/ are stale names; viewer/ is the current directory for the runtime viewer source
    3. README.md: Mentioned install.ps1 for Windows users alongside install.sh

    4. CHANGELOG.md: Documented this fix as version 2.0.6 (unreleased) referencing issue fix: #1540

    Verification

    This is a documentation-only change with no code or runtime behavior modifications. The changes directly address both confusion points raised in issue #1540.

    Base branch: main
    Branch: autodev/MemOS-1540
    Commit: 4deacb9

    I will create the PR next and post the PR link here.

  6. Memtensor-AI commented on Jun 3, 2026

    @Memtensor-AI
    Collaborator

    ✅ AutoDev task 968b9ae74b55fdef completed.

    Summary: Fixed issue #1540 by updating the memos-local-plugin documentation to clarify the correct installation method and explain the confusion around web/ and site/ directories.

    What was fixed

    The issue reported two problems:

    1. Users tried npm install -g @memtensor/memos-local-plugin which failed or didn't work as expected
    2. After cloning the repo, users couldn't find frontend source in web/ and site/ directories

    Root cause

    The documentation didn't prominently explain that this package is a plugin, not a standalone CLI, and requires the install.sh script for proper deployment. Additionally, commit 26e7e3d renamed web/ to viewer/ and removed site/, but users looking at published tarballs or old documentation were confused.

    Changes made

    1. README.md: Added a prominent IMPORTANT callout in the Quick start section explaining:

      • Why npm install -g is wrong (doesn't deploy to agent home, no config.yaml, no bridge/viewer)
      • That the npm tarball ships built artifacts only (dist/ + viewer/dist/), not source code
      • That install.sh/install.ps1 is the only supported installation path
    2. README.md: Added a Troubleshooting subsection with two FAQs:

      • Explains the "package not found" message users might see
      • Clarifies that web/ and site/ are stale names; viewer/ is the current directory for the runtime viewer source
    3. README.md: Mentioned install.ps1 for Windows users alongside install.sh

    4. CHANGELOG.md: Documented this fix as version 2.0.6 (unreleased) referencing issue fix: #1540

    Verification

    This is a documentation-only change with no code or runtime behavior modifications. The changes directly address both confusion points raised in issue #1540.

    Base branch: main
    Branch: autodev/MemOS-1540
    Commit: 4deacb9
    PR: #1878
    Assigned to: @MatthewZhuang, @CarltonXiang, @syzsunshine219
    Reviewers: @MatthewZhuang, @CarltonXiang, @syzsunshine219

  7. added
    ai:testingAI agent is running tests | AI 正在运行测试
    and removed
    ai:codingAI agent is coding | AI 正在编码
    ai:testingAI agent is running tests | AI 正在运行测试
    on Jun 3, 2026
  8. 2 remaining items

  9. added a commit that references this issue on Jun 4, 2026
    43fb2f0
  10. added a commit that references this issue on Jun 14, 2026
    38fbcfc
  11. added a commit that references this issue on Jul 2, 2026
    4e9bbce
  12. added a commit that references this issue on Jul 2, 2026
    ca75756
  13. added 2 commits that reference this issue on Jul 23, 2026
    21a27ed
    63ddb97
  14. added 3 commits that reference this issue on Jul 23, 2026
    d9130a7
    87b0738
    f8a887d
  15. added a commit that references this issue on Jul 24, 2026
    e820406
  16. added 4 commits that reference this issue on Sep 18, 2026
    36a195c
    8001941
    c9a80d5
    a447579
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:pluginOpenClaw & Hermestypes:bugSomething isn't working | 功能异常

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions