Pages

Pages keep research and notes on your boards. A page can stand alone or link tickets. Open Pages below Table in the sidebar. You can also use Commands → Go to Pages.

What is a Page?

A page belongs to a board. Linking a ticket does not grant access. Pages follow their board’s existing permissions. Pages are:

Board-owned: Stand alone or link multiple tickets.
Markdown-first: Write in markdown; the editor renders rich HTML with TipTap.
Agent-friendly: Created, appended, updated, and archived programmatically via CLI, MCP, REST, and AI Chat.
RAG-indexed: Every write is indexed so the AI can search, summarize, and reason over page content.
Versioned: Every change is captured with history and restore capabilities.
Conflict-safe: Optimistic-lock guards return a 409 conflict if multiple agents try to write at once.

Create and find pages

Open Pages from the sidebar or Commands.
Choose This board or All boards.
Search by page title or content.
Choose New page to start a document.
Choose its board when prompted.

Your title and content save automatically. Archived pages lists documents removed from active lists.

Link tickets and pages

On a page, choose + Link ticket. Pick an existing ticket from the search window. Linked tickets shows the page’s visible ticket links. Choose Unlink to remove a link. Unlinking keeps the page and ticket.

On a ticket, open Commands → Link page. Pick an existing page from the list. The page appears in that ticket’s Pages. Existing page lists also offer + Link page. Commands also includes Link page and Link ticket.

Pages without visible tickets show Back to Pages.

Agent permissions for page operations

Security fix Hypertask now properly restricts page actions based on an agent's access mode. Depending on the agent's live configuration, it may be:

Normal (read/write): Can create, change, archive, and restore task pages.
Read-only: Can only read pages. Creating, changing, archiving, or restoring is refused.

Behavior before this fix: A read-only agent was able to perform all four page actions (create, change, archive, restore) on task pages, bypassing its access mode and effectively gaining write-like permissions despite being restricted to reading.

After this fix: The server checks an agent's access mode before each page action. A read-only agent now receives a secure refusal for all four write operations, and the page remains unchanged.

This change, verified live on the QA team's own board, ensures that agent permissions match the documented behavior.

Comments indexed for search

Fix Comments that are very long or empty now generate searchable search copies. Previously the AI service that creates these copies would reject such comments, leaving them invisible in results. Now they are compressed and indexed, keeping full search coverage for comment threads. This change is part of the broader Turbopuffer upsert optimization, which also affects page content indexing.