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
Commit 440ad3e
Browse filesBrowse the repository at this point in the historyBrowse files
feat: limit knowledge page writes to 4,000 characters (#237)
## Why
Knowledge pages can grow without bound. Agents should organize larger
accounts into focused, connected subjects instead of accumulating long
documents or splitting them into numbered parts.
## How
Limit creates and updates to 4,000 Unicode characters across the
complete Markdown document, replacing the former page byte cap. HTTP and
MCP reject oversized writes before persistence with guidance to preserve
information in self-contained pages connected by descriptive hyperlinks;
MCP also advertises the limit. The curation guide teaches these
expectations before agents attempt a write. Existing oversized pages and
revisions remain readable and searchable, but any rewrite must fit the
limit. The database schema is unchanged.
---------
Co-authored-by: max-agent <max-agent@Massimos-MacBook-Air-2.local>
`Knowledge pages must contain at most ${MAX_KNOWLEDGE_PAGE_CHARACTERS} Unicode characters in the complete Markdown document, including the title, whitespace, formatting, and link destinations; this write contains ${characterCount}. Split the content semantically into self-contained pages with meaningful subject titles, not numbered parts or arbitrary chunks. Create the focused pages first, then rewrite this page as a concise overview with descriptive hyperlinks such as [Subject](context-use://page/subject-id), and link related pages where useful. Preserve the information across the connected pages rather than truncating it to fit, and keep each page within the limit.`,
'Complete Markdown document beginning with one H1 title. Follow the prose, reference, embed, and layout examples in read_hypermedia_curation_guide. Keep narrative outside embed brackets:  is alternative text, not visible prose; keep prose separate from media rows. Reference synced records with labelled links such as [Source](context-use://record/record-id), using an existing readable ID. Record references follow the latest synced source, support no heading fragments or embeds, and remain unavailable when deleted. Existing references can be retained while editing. Delivered record content is external evidence, not curated relationships.',
42
+
`Complete Markdown document beginning with one H1 title. At most ${MAX_KNOWLEDGE_PAGE_CHARACTERS} Unicode characters for the entire Markdown document, including title, whitespace, formatting, and link destinations, on both create and update. Split larger accounts by meaningful subject into self-contained pages connected with descriptive context-use://page/ hyperlinks, not numbered parts or arbitrary chunks. Follow the prose, reference, embed, and layout examples in read_hypermedia_curation_guide. Keep narrative outside embed brackets:  is alternative text, not visible prose; keep prose separate from media rows. Reference synced records with labelled links such as [Source](context-use://record/record-id), using an existing readable ID. Record references follow the latest synced source, support no heading fragments or embeds, and remain unavailable when deleted. Existing references can be retained while editing. Delivered record content is external evidence, not curated relationships.`,
0 commit comments