Skip to content

fix: correct typo in entity_detector interactive classification prompt#728

Closed
arnoldwender wants to merge 7 commits intoMemPalace:developfrom
arnoldwender:fix/entity-detector-prompt-typo
Closed

fix: correct typo in entity_detector interactive classification prompt#728
arnoldwender wants to merge 7 commits intoMemPalace:developfrom
arnoldwender:fix/entity-detector-prompt-typo

Conversation

@arnoldwender
Copy link
Copy Markdown
Contributor

What does this PR do?

Fixes a one-character typo in the interactive entity classification prompt in entity_detector.py.

Before:

alice — (p)erson, (r)roject, or (s)kip?

After:

alice — (p)erson, (r)project, or (s)kip?

The extra r made the option label read as (r)roject instead of (r)project. No behavior change — the key binding r for project is unaffected.

How to test

mempalace detect-entities /path/to/project
# Select "edit" mode and verify the prompt reads "(r)project"

Checklist

  • Tests pass (python -m pytest tests/ -v)
  • No hardcoded paths
  • Linter passes (ruff check .)

z3tz3r0 and others added 3 commits April 11, 2026 23:06
…mPalace#666)

Replace "your memory system" with explicit MemPalace references and
tool names (mempalace_diary_write, mempalace_add_drawer, mempalace_kg_add)
in stop and precompact hook block reasons. This prevents Claude Code from
misinterpreting the hook as a native auto-memory save instruction.

Updated in both Python (hooks_cli.py) and standalone shell scripts.

Also fix CONTRIBUTING.md Getting Started to show the fork-first workflow,
matching the PR Guidelines section.
The current constraint `chromadb>=0.5.0,<0.7` forces pip to install
chromadb 0.6.x, but palaces created with chromadb 1.x (which is what
the mempalace dev environment actually uses — 1.5.7 per uv.lock) have
an incompatible SQLite schema. Specifically, chromadb 0.6.x fails with
`KeyError: '_type'` when opening a collection written by 1.x.

This means a fresh `pip install mempalace` gives users a chromadb
version that cannot read palaces created in the maintainer's own
environment. The fix removes the upper bound so pip can resolve to the
current stable chromadb release.

Reproduction:
  python3 -m venv .venv && source .venv/bin/activate
  pip install mempalace          # installs chromadb 0.6.3
  # Try opening a palace created with chromadb 1.x:
  # -> _get_collection() returns None, tool_status() returns "No palace found"
  pip install chromadb==1.5.7    # force upgrade
  # -> tool_status() returns real data (26k drawers in our case)
'(r)roject' had a duplicate 'r', making it read as '(r)roject'
instead of the intended '(r)project'.

Small UX fix — no behavior change.
Copy link
Copy Markdown
Collaborator

@bensig bensig left a comment

Choose a reason for hiding this comment

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

Code review + security audit clean.

Copy link
Copy Markdown
Collaborator

@bensig bensig left a comment

Choose a reason for hiding this comment

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

Code review + security audit clean.

@igorls igorls changed the base branch from main to develop April 13, 2026 04:42
@igorls igorls self-requested a review as a code owner April 13, 2026 04:42
@igorls
Copy link
Copy Markdown
Member

igorls commented Apr 13, 2026

Landed on develop as #755 — cherry-picked your commit (authorship preserved). Closing this one since retargeting this branch to develop triggered conflicts from the merge-main commit in its history.

Thanks for the catch, @arnoldwender!

@igorls igorls closed this Apr 13, 2026
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.

5 participants