basic-memory 0.13.0b4__py3-none-any.whl → 0.13.0b6__py3-none-any.whl

basic_memory/mcp/tools/delete_note.py

@@ -1,5 +1,8 @@
+from textwrap import dedent
 from typing import Optional
 
+from loguru import logger
+
 from basic_memory.mcp.tools.utils import call_delete
 from basic_memory.mcp.server import mcp
 from basic_memory.mcp.async_client import client
@@ -7,8 +10,148 @@ from basic_memory.mcp.project_session import get_active_project
 from basic_memory.schemas import DeleteEntitiesResponse
 
 
+def _format_delete_error_response(error_message: str, identifier: str) -> str:
+    """Format helpful error responses for delete failures that guide users to successful deletions."""
+
+    # Note not found errors
+    if "entity not found" in error_message.lower() or "not found" in error_message.lower():
+        search_term = identifier.split("/")[-1] if "/" in identifier else identifier
+        title_format = (
+            identifier.split("/")[-1].replace("-", " ").title() if "/" in identifier else identifier
+        )
+        permalink_format = identifier.lower().replace(" ", "-")
+
+        return dedent(f"""
+            # Delete Failed - Note Not Found
+
+            The note '{identifier}' could not be found for deletion.
+
+            ## This might mean:
+            1. **Already deleted**: The note may have been deleted previously
+            2. **Wrong identifier**: The identifier format might be incorrect
+            3. **Different project**: The note might be in a different project
+
+            ## How to verify:
+            1. **Search for the note**: Use `search_notes("{search_term}")` to find it
+            2. **Try different formats**:
+               - If you used a permalink like "folder/note-title", try just the title: "{title_format}"
+               - If you used a title, try the permalink format: "{permalink_format}"
+
+            3. **Check if already deleted**: Use `list_directory("/")` to see what notes exist
+            4. **Check current project**: Use `get_current_project()` to verify you're in the right project
+
+            ## If the note actually exists:
+            ```
+            # First, find the correct identifier:
+            search_notes("{identifier}")
+
+            # Then delete using the correct identifier:
+            delete_note("correct-identifier-from-search")
+            ```
+
+            ## If you want to delete multiple similar notes:
+            Use search to find all related notes and delete them one by one.
+            """).strip()
+
+    # Permission/access errors
+    if (
+        "permission" in error_message.lower()
+        or "access" in error_message.lower()
+        or "forbidden" in error_message.lower()
+    ):
+        return f"""# Delete Failed - Permission Error
+
+You don't have permission to delete '{identifier}': {error_message}
+
+## How to resolve:
+1. **Check permissions**: Verify you have delete/write access to this project
+2. **File locks**: The note might be open in another application
+3. **Project access**: Ensure you're in the correct project with proper permissions
+
+## Alternative actions:
+- Check current project: `get_current_project()`
+- Switch to correct project: `switch_project("project-name")`
+- Verify note exists first: `read_note("{identifier}")`
+
+## If you have read-only access:
+Send a message to support@basicmachines.co to request deletion, or ask someone with write access to delete the note."""
+
+    # Server/filesystem errors
+    if (
+        "server error" in error_message.lower()
+        or "filesystem" in error_message.lower()
+        or "disk" in error_message.lower()
+    ):
+        return f"""# Delete Failed - System Error
+
+A system error occurred while deleting '{identifier}': {error_message}
+
+## Immediate steps:
+1. **Try again**: The error might be temporary
+2. **Check file status**: Verify the file isn't locked or in use
+3. **Check disk space**: Ensure the system has adequate storage
+
+## Troubleshooting:
+- Verify note exists: `read_note("{identifier}")`
+- Check project status: `get_current_project()`
+- Try again in a few moments
+
+## If problem persists:
+Send a message to support@basicmachines.co - there may be a filesystem or database issue."""
+
+    # Database/sync errors
+    if "database" in error_message.lower() or "sync" in error_message.lower():
+        return f"""# Delete Failed - Database Error
+
+A database error occurred while deleting '{identifier}': {error_message}
+
+## This usually means:
+1. **Sync conflict**: The file system and database are out of sync
+2. **Database lock**: Another operation is accessing the database
+3. **Corrupted entry**: The database entry might be corrupted
+
+## Steps to resolve:
+1. **Try again**: Wait a moment and retry the deletion
+2. **Check note status**: `read_note("{identifier}")` to see current state
+3. **Manual verification**: Use `list_directory()` to see if file still exists
+
+## If the note appears gone but database shows it exists:
+Send a message to support@basicmachines.co - a manual database cleanup may be needed."""
+
+    # Generic fallback
+    return f"""# Delete Failed
+
+Error deleting note '{identifier}': {error_message}
+
+## General troubleshooting:
+1. **Verify the note exists**: `read_note("{identifier}")` or `search_notes("{identifier}")`
+2. **Check permissions**: Ensure you can edit/delete files in this project
+3. **Try again**: The error might be temporary
+4. **Check project**: Make sure you're in the correct project
+
+## Step-by-step approach:
+```
+# 1. Confirm note exists and get correct identifier
+search_notes("{identifier}")
+
+# 2. Read the note to verify access
+read_note("correct-identifier-from-search")
+
+# 3. Try deletion with correct identifier
+delete_note("correct-identifier-from-search")
+```
+
+## Alternative approaches:
+- Check what notes exist: `list_directory("/")`
+- Verify current project: `get_current_project()`
+- Switch projects if needed: `switch_project("correct-project")`
+
+## Need help?
+If the note should be deleted but the operation keeps failing, send a message to support@basicmachines.co."""
+
+
 @mcp.tool(description="Delete a note by title or permalink")
-async def delete_note(identifier: str, project: Optional[str] = None) -> bool:
+async def delete_note(identifier: str, project: Optional[str] = None) -> bool | str:
     """Delete a note from the knowledge base.
 
     Args:
@@ -31,6 +174,18 @@ async def delete_note(identifier: str, project: Optional[str] = None) -> bool:
     active_project = get_active_project(project)
     project_url = active_project.project_url
 
-    response = await call_delete(client, f"{project_url}/knowledge/entities/{identifier}")
-    result = DeleteEntitiesResponse.model_validate(response.json())
-    return result.deleted
+    try:
+        response = await call_delete(client, f"{project_url}/knowledge/entities/{identifier}")
+        result = DeleteEntitiesResponse.model_validate(response.json())
+
+        if result.deleted:
+            logger.info(f"Successfully deleted note: {identifier}")
+            return True
+        else:
+            logger.warning(f"Delete operation completed but note was not deleted: {identifier}")
+            return False
+
+    except Exception as e:  # pragma: no cover
+        logger.error(f"Delete failed for '{identifier}': {e}")
+        # Return formatted error message for better user experience
+        return _format_delete_error_response(str(e), identifier)

basic_memory/mcp/tools/edit_note.py

@@ -24,14 +24,14 @@ def _format_error_response(
     if "Entity not found" in error_message or "entity not found" in error_message.lower():
         return f"""# Edit Failed - Note Not Found
 
-The note with identifier '{identifier}' could not be found.
+The note with identifier '{identifier}' could not be found. Edit operations require an exact match (no fuzzy matching).
 
 ## Suggestions to try:
-1. **Search for the note first**: Use `search_notes("{identifier.split("/")[-1]}")` to find similar notes
-2. **Try different identifier formats**:
-   - If you used a permalink like "folder/note-title", try just the title: "{identifier.split("/")[-1].replace("-", " ").title()}"
-   - If you used a title, try the permalink format: "{identifier.lower().replace(" ", "-")}"
-   - Use `read_note()` first to verify the note exists and get the correct identifiers
+1. **Search for the note first**: Use `search_notes("{identifier.split("/")[-1]}")` to find similar notes with exact identifiers
+2. **Try different exact identifier formats**:
+   - If you used a permalink like "folder/note-title", try the exact title: "{identifier.split("/")[-1].replace("-", " ").title()}"
+   - If you used a title, try the exact permalink format: "{identifier.lower().replace(" ", "-")}"
+   - Use `read_note()` first to verify the note exists and get the exact identifier
 
 ## Alternative approach:
 Use `write_note()` to create the note first, then edit it."""
@@ -142,7 +142,9 @@ async def edit_note(
     It supports various operations for different editing scenarios.
 
     Args:
-        identifier: The title, permalink, or memory:// URL of the note to edit
+        identifier: The exact title, permalink, or memory:// URL of the note to edit.
+                   Must be an exact match - fuzzy matching is not supported for edit operations.
+                   Use search_notes() or read_note() first to find the correct identifier if uncertain.
         operation: The editing operation to perform:
                   - "append": Add content to the end of the note
                   - "prepend": Add content to the beginning of the note
@@ -179,10 +181,14 @@ async def edit_note(
         # Replace subsection with more specific header
         edit_note("docs/setup", "replace_section", "Updated install steps\\n", section="### Installation")
 
-        # Using different identifier formats
-        edit_note("Meeting Notes", "append", "\\n- Follow up on action items")  # title
-        edit_note("docs/meeting-notes", "append", "\\n- Follow up tasks")       # permalink
-        edit_note("docs/Meeting Notes", "append", "\\n- Next steps")           # folder/title
+        # Using different identifier formats (must be exact matches)
+        edit_note("Meeting Notes", "append", "\\n- Follow up on action items")  # exact title
+        edit_note("docs/meeting-notes", "append", "\\n- Follow up tasks")       # exact permalink
+        edit_note("docs/Meeting Notes", "append", "\\n- Next steps")           # exact folder/title
+
+        # If uncertain about identifier, search first:
+        # search_notes("meeting")  # Find available notes
+        # edit_note("docs/meeting-notes-2025", "append", "content")  # Use exact result
 
         # Add new section to document
         edit_note("project-plan", "replace_section", "TBD - needs research\\n", section="## Future Work")

basic_memory/mcp/tools/move_note.py

@@ -1,5 +1,6 @@
 """Move note tool for Basic Memory MCP server."""
 
+from textwrap import dedent
 from typing import Optional
 
 from loguru import logger
@@ -11,6 +12,203 @@ from basic_memory.mcp.project_session import get_active_project
 from basic_memory.schemas import EntityResponse
 
 
+def _format_move_error_response(error_message: str, identifier: str, destination_path: str) -> str:
+    """Format helpful error responses for move failures that guide users to successful moves."""
+
+    # Note not found errors
+    if "entity not found" in error_message.lower() or "not found" in error_message.lower():
+        search_term = identifier.split("/")[-1] if "/" in identifier else identifier
+        title_format = (
+            identifier.split("/")[-1].replace("-", " ").title() if "/" in identifier else identifier
+        )
+        permalink_format = identifier.lower().replace(" ", "-")
+
+        return dedent(f"""
+            # Move Failed - Note Not Found
+
+            The note '{identifier}' could not be found for moving. Move operations require an exact match (no fuzzy matching).
+
+            ## Suggestions to try:
+            1. **Search for the note first**: Use `search_notes("{search_term}")` to find it with exact identifiers
+            2. **Try different exact identifier formats**:
+               - If you used a permalink like "folder/note-title", try the exact title: "{title_format}"
+               - If you used a title, try the exact permalink format: "{permalink_format}"
+               - Use `read_note()` first to verify the note exists and get the exact identifier
+
+            3. **Check current project**: Use `get_current_project()` to verify you're in the right project
+            4. **List available notes**: Use `list_directory("/")` to see what notes exist
+
+            ## Before trying again:
+            ```
+            # First, verify the note exists:
+            search_notes("{identifier}")
+
+            # Then use the exact identifier from search results:
+            move_note("correct-identifier-here", "{destination_path}")
+            ```
+            """).strip()
+
+    # Destination already exists errors
+    if "already exists" in error_message.lower() or "file exists" in error_message.lower():
+        return f"""# Move Failed - Destination Already Exists
+
+Cannot move '{identifier}' to '{destination_path}' because a file already exists at that location.
+
+## How to resolve:
+1. **Choose a different destination**: Try a different filename or folder
+   - Add timestamp: `{destination_path.rsplit(".", 1)[0] if "." in destination_path else destination_path}-backup.md`
+   - Use different folder: `archive/{destination_path}` or `backup/{destination_path}`
+
+2. **Check the existing file**: Use `read_note("{destination_path}")` to see what's already there
+3. **Remove or rename existing**: If safe to do so, move the existing file first
+
+## Try these alternatives:
+```
+# Option 1: Add timestamp to make unique
+move_note("{identifier}", "{destination_path.rsplit(".", 1)[0] if "." in destination_path else destination_path}-backup.md")
+
+# Option 2: Use archive folder  
+move_note("{identifier}", "archive/{destination_path}")
+
+# Option 3: Check what's at destination first
+read_note("{destination_path}")
+```"""
+
+    # Invalid path errors
+    if "invalid" in error_message.lower() and "path" in error_message.lower():
+        return f"""# Move Failed - Invalid Destination Path
+
+The destination path '{destination_path}' is not valid: {error_message}
+
+## Path requirements:
+1. **Relative paths only**: Don't start with `/` (use `notes/file.md` not `/notes/file.md`)
+2. **Include file extension**: Add `.md` for markdown files
+3. **Use forward slashes**: For folder separators (`folder/subfolder/file.md`)
+4. **No special characters**: Avoid `\\`, `:`, `*`, `?`, `"`, `<`, `>`, `|`
+
+## Valid path examples:
+- `notes/my-note.md`
+- `projects/2025/meeting-notes.md`
+- `archive/old-projects/legacy-note.md`
+
+## Try again with:
+```
+move_note("{identifier}", "notes/{destination_path.split("/")[-1] if "/" in destination_path else destination_path}")
+```"""
+
+    # Permission/access errors
+    if (
+        "permission" in error_message.lower()
+        or "access" in error_message.lower()
+        or "forbidden" in error_message.lower()
+    ):
+        return f"""# Move Failed - Permission Error
+
+You don't have permission to move '{identifier}': {error_message}
+
+## How to resolve:
+1. **Check file permissions**: Ensure you have write access to both source and destination
+2. **Verify project access**: Make sure you have edit permissions for this project
+3. **Check file locks**: The file might be open in another application
+
+## Alternative actions:
+- Check current project: `get_current_project()`
+- Switch projects if needed: `switch_project("project-name")`
+- Try copying content instead: `read_note("{identifier}")` then `write_note()` to new location"""
+
+    # Source file not found errors
+    if "source" in error_message.lower() and (
+        "not found" in error_message.lower() or "missing" in error_message.lower()
+    ):
+        return f"""# Move Failed - Source File Missing
+
+The source file for '{identifier}' was not found on disk: {error_message}
+
+This usually means the database and filesystem are out of sync.
+
+## How to resolve:
+1. **Check if note exists in database**: `read_note("{identifier}")`
+2. **Run sync operation**: The file might need to be re-synced
+3. **Recreate the file**: If data exists in database, recreate the physical file
+
+## Troubleshooting steps:
+```
+# Check if note exists in Basic Memory
+read_note("{identifier}")
+
+# If it exists, the file is missing on disk - send a message to support@basicmachines.co
+# If it doesn't exist, use search to find the correct identifier
+search_notes("{identifier}")
+```"""
+
+    # Server/filesystem errors
+    if (
+        "server error" in error_message.lower()
+        or "filesystem" in error_message.lower()
+        or "disk" in error_message.lower()
+    ):
+        return f"""# Move Failed - System Error
+
+A system error occurred while moving '{identifier}': {error_message}
+
+## Immediate steps:
+1. **Try again**: The error might be temporary
+2. **Check disk space**: Ensure adequate storage is available
+3. **Verify filesystem permissions**: Check if the destination directory is writable
+
+## Alternative approaches:
+- Copy content to new location: Use `read_note("{identifier}")` then `write_note()` 
+- Use a different destination folder that you know works
+- Send a message to support@basicmachines.co if the problem persists
+
+## Backup approach:
+```
+# Read current content
+content = read_note("{identifier}")
+
+# Create new note at desired location  
+write_note("New Note Title", content, "{destination_path.split("/")[0] if "/" in destination_path else "notes"}")
+
+# Then delete original if successful
+delete_note("{identifier}")
+```"""
+
+    # Generic fallback
+    return f"""# Move Failed
+
+Error moving '{identifier}' to '{destination_path}': {error_message}
+
+## General troubleshooting:
+1. **Verify the note exists**: `read_note("{identifier}")` or `search_notes("{identifier}")`
+2. **Check destination path**: Ensure it's a valid relative path with `.md` extension
+3. **Verify permissions**: Make sure you can edit files in this project
+4. **Try a simpler path**: Use a basic folder structure like `notes/filename.md`
+
+## Step-by-step approach:
+```
+# 1. Confirm note exists
+read_note("{identifier}")
+
+# 2. Try a simple destination first
+move_note("{identifier}", "notes/{destination_path.split("/")[-1] if "/" in destination_path else destination_path}")
+
+# 3. If that works, then try your original destination
+```
+
+## Alternative approach:
+If moving continues to fail, you can copy the content manually:
+```
+# Read current content
+content = read_note("{identifier}")
+
+# Create new note
+write_note("Title", content, "target-folder") 
+
+# Delete original once confirmed
+delete_note("{identifier}")
+```"""
+
+
 @mcp.tool(
     description="Move a note to a new location, updating database and maintaining links.",
 )
@@ -22,7 +220,9 @@ async def move_note(
     """Move a note to a new file location within the same project.
 
     Args:
-        identifier: Entity identifier (title, permalink, or memory:// URL)
+        identifier: Exact entity identifier (title, permalink, or memory:// URL).
+                   Must be an exact match - fuzzy matching is not supported for move operations.
+                   Use search_notes() or read_note() first to find the correct identifier if uncertain.
         destination_path: New path relative to project root (e.g., "work/meetings/2025-05-26.md")
         project: Optional project name (defaults to current session project)
 
@@ -30,9 +230,18 @@ async def move_note(
         Success message with move details
 
     Examples:
-        - Move to new folder: move_note("My Note", "work/notes/my-note.md")
-        - Move by permalink: move_note("my-note-permalink", "archive/old-notes/my-note.md")
-        - Specify project: move_note("My Note", "archive/my-note.md", project="work-project")
+        # Move to new folder (exact title match)
+        move_note("My Note", "work/notes/my-note.md")
+
+        # Move by exact permalink
+        move_note("my-note-permalink", "archive/old-notes/my-note.md")
+
+        # Specify project with exact identifier
+        move_note("My Note", "archive/my-note.md", project="work-project")
+
+        # If uncertain about identifier, search first:
+        # search_notes("my note")  # Find available notes
+        # move_note("docs/my-note-2025", "archive/my-note.md")  # Use exact result
 
     Note: This operation moves notes within the specified project only. Moving notes
     between different projects is not currently supported.
@@ -49,39 +258,42 @@ async def move_note(
     active_project = get_active_project(project)
     project_url = active_project.project_url
 
-    # Prepare move request
-    move_data = {
-        "identifier": identifier,
-        "destination_path": destination_path,
-        "project": active_project.name,
-    }
-
-    # Call the move API endpoint
-    url = f"{project_url}/knowledge/move"
-    response = await call_post(client, url, json=move_data)
-    result = EntityResponse.model_validate(response.json())
-
-    # 10. Build success message
-    result_lines = [
-        "✅ Note moved successfully",
-        "",
-        f"📁 **{identifier}** → **{result.file_path}**",
-        f"🔗 Permalink: {result.permalink}",
-        "📊 Database and search index updated",
-        "",
-        f"<!-- Project: {active_project.name} -->",
-    ]
-
-    # Return the response text which contains the formatted success message
-    result = "\n".join(result_lines)
-
-    # Log the operation
-    logger.info(
-        "Move note completed",
-        identifier=identifier,
-        destination_path=destination_path,
-        project=active_project.name,
-        status_code=response.status_code,
-    )
-
-    return result
+    try:
+        # Prepare move request
+        move_data = {
+            "identifier": identifier,
+            "destination_path": destination_path,
+            "project": active_project.name,
+        }
+
+        # Call the move API endpoint
+        url = f"{project_url}/knowledge/move"
+        response = await call_post(client, url, json=move_data)
+        result = EntityResponse.model_validate(response.json())
+
+        # Build success message
+        result_lines = [
+            "✅ Note moved successfully",
+            "",
+            f"📁 **{identifier}** → **{result.file_path}**",
+            f"🔗 Permalink: {result.permalink}",
+            "📊 Database and search index updated",
+            "",
+            f"<!-- Project: {active_project.name} -->",
+        ]
+
+        # Log the operation
+        logger.info(
+            "Move note completed",
+            identifier=identifier,
+            destination_path=destination_path,
+            project=active_project.name,
+            status_code=response.status_code,
+        )
+
+        return "\n".join(result_lines)
+
+    except Exception as e:
+        logger.error(f"Move failed for '{identifier}' to '{destination_path}': {e}")
+        # Return formatted error message for better user experience
+        return _format_move_error_response(str(e), identifier, destination_path)

basic_memory/mcp/tools/project_management.py

@@ -4,6 +4,8 @@ These tools allow users to switch between projects, list available projects,
 and manage project context during conversations.
 """
 
+from textwrap import dedent
+
 from fastmcp import Context
 from loguru import logger
 
@@ -94,7 +96,11 @@ async def switch_project(project_name: str, ctx: Context | None = None) -> str:
 
         # Get project info to show summary
         try:
-            response = await call_get(client, f"{project_config.project_url}/project/info")
+            response = await call_get(
+                client,
+                f"{project_config.project_url}/project/info",
+                params={"project_name": project_name},
+            )
             project_info = ProjectInfoResponse.model_validate(response.json())
 
             result = f"✓ Switched to {project_name} project\n\n"
@@ -115,7 +121,29 @@ async def switch_project(project_name: str, ctx: Context | None = None) -> str:
         logger.error(f"Error switching to project {project_name}: {e}")
         # Revert to previous project on error
         session.set_current_project(current_project)
-        raise e
+
+        # Return user-friendly error message instead of raising exception
+        return dedent(f"""
+            # Project Switch Failed
+
+            Could not switch to project '{project_name}': {str(e)}
+
+            ## Current project: {current_project}
+            Your session remains on the previous project.
+
+            ## Troubleshooting:
+            1. **Check available projects**: Use `list_projects()` to see valid project names
+            2. **Verify spelling**: Ensure the project name is spelled correctly
+            3. **Check permissions**: Verify you have access to the requested project
+            4. **Try again**: The error might be temporary
+
+            ## Available options:
+            - See all projects: `list_projects()`
+            - Stay on current project: `get_current_project()`
+            - Try different project: `switch_project("correct-project-name")`
+
+            If the project should exist but isn't listed, send a message to support@basicmachines.co.
+            """).strip()
 
 
 @mcp.tool()
@@ -139,7 +167,11 @@ async def get_current_project(ctx: Context | None = None) -> str:
     result = f"Current project: {current_project}\n\n"
 
     # get project stats
-    response = await call_get(client, f"{project_config.project_url}/project/info")
+    response = await call_get(
+        client,
+        f"{project_config.project_url}/project/info",
+        params={"project_name": current_project},
+    )
     project_info = ProjectInfoResponse.model_validate(response.json())
 
     result += f"• {project_info.statistics.total_entities} entities\n"

basic_memory/mcp/tools/read_note.py

@@ -52,6 +52,13 @@ async def read_note(
         read_note("Meeting Notes", project="work-project")
     """
 
+    # Check migration status and wait briefly if needed
+    from basic_memory.mcp.tools.utils import wait_for_migration_or_return_status
+
+    migration_status = await wait_for_migration_or_return_status(timeout=5.0)
+    if migration_status:  # pragma: no cover
+        return f"# System Status\n\n{migration_status}\n\nPlease wait for migration to complete before reading notes."
+
     active_project = get_active_project(project)
     project_url = active_project.project_url
 
@@ -74,7 +81,7 @@ async def read_note(
 
     # Fallback 1: Try title search via API
     logger.info(f"Search title for: {identifier}")
-    title_results = await search_notes(query=identifier, search_type="title", project=project)
+    title_results = await search_notes.fn(query=identifier, search_type="title", project=project)
 
     if title_results and title_results.results:
         result = title_results.results[0]  # Get the first/best match
@@ -98,7 +105,7 @@ async def read_note(
 
     # Fallback 2: Text search as a last resort
     logger.info(f"Title search failed, trying text search for: {identifier}")
-    text_results = await search_notes(query=identifier, search_type="text", project=project)
+    text_results = await search_notes.fn(query=identifier, search_type="text", project=project)
 
     # We didn't find a direct match, construct a helpful error message
     if not text_results or not text_results.results:
@@ -114,7 +121,7 @@ def format_not_found_message(identifier: str) -> str:
     return dedent(f"""
         # Note Not Found: "{identifier}"
         
-        I couldn't find any notes matching "{identifier}". Here are some suggestions:
+        I searched for "{identifier}" using multiple methods (direct lookup, title search, and text search) but couldn't find any matching notes. Here are some suggestions:
         
         ## Check Identifier Type
         - If you provided a title, try using the exact permalink instead
@@ -160,7 +167,7 @@ def format_related_results(identifier: str, results) -> str:
     message = dedent(f"""
         # Note Not Found: "{identifier}"
         
-        I couldn't find an exact match for "{identifier}", but I found some related notes:
+        I searched for "{identifier}" using direct lookup and title search but couldn't find an exact match. However, I found some related notes through text search:
         
         """)