Repository navigation
feat(notes): pin notes, each person's own, at the top of the tree and the Notes page - #414
Merged
Merged
Conversation
… the Notes page
Pin in a note's ⋯ menu in the tree pins it for that person: it shows under
Pinned at the top of the tree and first on the Notes page. Pins need only read
access and change nothing for anyone else (up to 50 per namespace).
PUT/DELETE /api/v1/notes/{pid}/pin; each page says whether you pinned it.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RrY2byt5BHVeBXJUyfwWpb
This was referenced Oct 15, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: there was no way to keep the notes you use most within reach; the tree is in its own order and the Notes page is newest first.
After: Pin in a note's ⋯ menu in the tree pins it for you. Pinned notes show under Pinned at the top of the tree (each with an Unpin button) and first on the Notes page with a pin mark. Pins are each person's own, so pinning changes nothing for anyone else and needs only read access; up to 50 per namespace.
How:
notebook.pin()keeps the people who pinned a page innote_page.pinned_by(added and removed witharray::union/array::complement, so pinning twice is harmless).PUTandDELETE /api/v1/notes/{pid}/pinpin and unpin; every page inGET /notesand each page read sayspinnedfor the caller, andpinned_byitself is never sent. On the web,components/notes/pin.ts(usePin) pins optimistically and takes it back with a notice when the server refuses.Motivation and Context
Part of the notes UI audit (Adeel: "notes ui is very bad and is missing tons of things"): favourites or pins are in every notes app.
Steps to reproduce (if appropriate):
Notes tree → ⋯ on a note → Pin. It shows under Pinned at the top of the tree and first on /notes. Unpin from its row under Pinned.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.## UnreleasedinCHANGELOG.md.Done questions (AGENTS.md)
PUT/DELETE /api/v1/notes/{pid}/pinwith any token;pinnedon every page read. No MCP tool, as pins are a person's own view.note_page(SCHEMALESS), read as empty when missing; no upgrade step needed.docs/notes.mdPinned notes,docs/api.md) updated;make openapiregenerated. Local: backend 1110 passed, web 912 passed.🤖 Generated with Claude Code
https://claude.ai/code/session_01RrY2byt5BHVeBXJUyfwWpb
Generated by Claude Code