Skip to content

Fix #1540: fix:#1878

Open
Memtensor-AI wants to merge 1 commit into
dev-20260604-v2.0.19from
autodev/MemOS-1540
Open

Fix #1540: fix:#1878
Memtensor-AI wants to merge 1 commit into
dev-20260604-v2.0.19from
autodev/MemOS-1540

Conversation

@Memtensor-AI
Copy link
Copy Markdown
Collaborator

Description

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.

Related Issue (Required): Fixes #1540

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (does not change functionality, e.g. code style improvements, linting)
  • Documentation update

How Has This Been Tested?

Executor did not report tests.

  • Unit Test
  • Test Script Or Test Steps (please provide)
  • Pipeline Automated API Test (please provide)

Checklist

  • I have performed a self-review of my own code
  • I have commented my code in hard-to-understand areas
  • I have added tests that prove my fix is effective or that my feature works
  • I have created related documentation issue/PR in MemOS-Docs (if applicable)
  • I have linked the issue to this PR (if applicable)
  • I have mentioned the person who will review this PR

@MatthewZhuang, @CarltonXiang, @syzsunshine219 please review this PR.

Reviewer Checklist

  • closes fix: #1540
  • Made sure Checks passed
  • Tests have been provided

…1540)

The README's 'Quick start' section told users to use install.sh instead
of npm install, but the warning was buried and users still tried
'npm install -g @memtensor/memos-local-plugin' first. The reporter in
#1540 encountered this on a Hermes deployment.

This change:

- Promotes the 'do not run npm install -g' notice to a prominent
  IMPORTANT callout explaining why global install is wrong (no
  agent-home deploy, no config.yaml, no bridge/viewer) and that the
  tarball intentionally ships built artifacts only.
- Adds a Troubleshooting subsection covering the two specific symptoms
  in the bug report: the 'package not found' misread, and the stale
  web/ and site/ directory names (web/ is now viewer/, site/ was
  removed by commit 26e7e3d).
- Mentions install.ps1 for Windows alongside install.sh.
- CHANGELOG: record the docs fix and reference #1540.

Documentation-only change; no code or runtime behavior touched.
@Memtensor-AI
Copy link
Copy Markdown
Collaborator Author

✅ Automated Test Results: PASSED

All tests passed (35/-542 executed, 613 skipped). memos_local_plugin/smoke: 0 passed, 578 skipped, memos_local_plugin/contract: 35 passed, 35 skipped. Duration: 4s

Branch: autodev/MemOS-1540

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.

4 participants