You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
FEAT: Support bulk/batch tag editing or renaming #6166
I have searched existing issues and confirmed this has not already been requested
This is a feature request, not a bug report or support question
Area
Tags / organization
Problem or Use Case
Currently, managing and updating tags becomes extremely tedious as the number of Memos grows.
When a user's taxonomy changes over time (e.g., wanting to merge #todo into #tasks, or fix a typo in a tag), there is no way to rename or edit a tag globally. The user is forced to manually search for every single Memo with that tag and edit the text one by one. This manual process is time-consuming, prone to human error, and creates friction for long-term knowledge management.
Who Would Use This?
Power users who have accumulated hundreds or thousands of Memos and need to reorganize their tag structure.
Daily note-takers and journaling users who rely heavily on tags for quick categorization and filtering.
Anyone who wants to merge duplicate/similar tags or maintain a clean tag taxonomy.
Proposed Solution
Global Tag Rename/Delete in Tag Management:
Allow users to right-click or click an edit/delete button next to a tag in the sidebar (or settings page).
Renaming #tagA to #tagB should automatically update the text/tag reference across all Memos containing #tagA.
Support a multi-select mode in the Memo list view to add or remove tags from multiple selected Memos at once.
Alternatives Considered
Currently, the only workaround is manually searching for a tag and editing each Memo individually. Another hack is exporting/modifying the underlying SQLite database directly, which is dangerous for regular users and inaccessible for non-technical users.
This issue has been automatically marked as stale because it has had no activity for 30 days. It will be closed in 7 days if no further activity occurs. Comment with any relevant updates to keep it open.
This issue has been automatically closed because it remained inactive for 7 days after being marked stale. If it is still relevant, comment with updated details so it can be reconsidered.
Activity
github-actions commentedon Sep 9, 2026
This issue has been automatically marked as stale because it has had no activity for 30 days. It will be closed in 7 days if no further activity occurs. Comment with any relevant updates to keep it open.
github-actions commentedon Sep 16, 2026
This issue has been automatically closed because it remained inactive for 7 days after being marked stale. If it is still relevant, comment with updated details so it can be reconsidered.