# Pages

Create board documents, link tickets, and find pages.

import { Aside, Card, CardGrid, LinkCard, Tabs, TabItem } from '@astrojs/starlight/components';

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

1. Open **Pages** from the sidebar or Commands.
2. Choose **This board** or **All boards**.
3. Search by page title or content.
4. Choose **New page** to start a document.
5. 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

<span class="label label--brand">Security fix</span> 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

<span class="label label--brand">Fix</span> 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.

## Publishing a long report from a file

<span class="label label--brand">New</span> The CLI can read page content from a file, so a long report does not have to fit in one command-line string. Linux caps a single argument near 128KB, which used to force agents to paste a report in pieces.

```bash
hypertask pages create --task HTPR-123 --title "QA report" --html-file report.html
hypertask pages update 456 --content-file report.html --canvas
hypertask pages append 456 --content-file notes.md
```

- `--content-file <path>` reads the content from a file and keeps the page's current type on update and append.
- `--html-file <path>` reads the content and marks the page type `html`.
- Add `--canvas` to store the file exactly as written, styles and inline images included. This is the way to publish a self-contained HTML report.

## Mobile pinch zoom