Describe how your work should feel

The shortest path

1. Open Home and choose Build an item type.
2. Describe a publication, project board, notes system, or your own idea.
3. Refine the result in conversation or adjust its visual direction, properties, and folder view.
4. Inspect the Item and Folder previews with real, sample, empty, or stress-test content.
5. Choose Done once. New items in that folder inherit the type.

Refine without losing a direction

Every starter, agent refinement, and manual edit becomes a design version. Undo and Redo move between complete versions, the history menu jumps to any earlier direction, and Compare places the current design beside the previous one. Nothing is saved to the workspace until you choose Done.

The preview uses the same renderer as finished documents. Check a selected folder's existing items, built-in sample content, a blank state, or deliberately long stress-test content. Wide, tablet, and phone frames make narrow-layout problems visible before saving. A deterministic preflight names important structural issues and prevents an incomplete type from being saved.

Start without connecting AI

Editorial publication, Project board, and Quick notes are complete starters. They work immediately, remain fully editable, and need no provider connection. Prompt-based generation in the App Store and browser editions uses a workspace Anthropic or OpenAI provider key. The standalone Mac edition may instead use an eligible connected ChatGPT or Codex account.

Prompts that work well

• “A Medium-like publication with headline, subtitle, hero image, author, and date.”
• “A calm Notion-like project board grouped by status, with priority and due dates.”
• “Fast Apple Notes-like notes with a title, body, tags, and modified date.”

Name the information you need, the reference you like, and how the folder should organize its items. You can rename, add, or remove fields before saving.

Model the information, not just the page

Item types can declare text, rich text, images, dates, URLs, selects, numbers, checkboxes, relations, people records, recurrence, and repeating rows. People are ordinary linked TextText records, not workspace accounts. Status fields can define allowed transitions, and recurrence uses safe named presets.

Computed values are read-only. They can count rows, sum a numeric row property, show completed rows, or compare current and target numbers. Text and number properties can carry validation limits, while secondary properties can appear conditionally after a checkbox or single-select choice is set.

Give one folder several useful views

A type can include named folder views such as All work, My tasks, Due soon, Board, or Calendar. Each view can change the safe filters, grouping, sort, columns, and layout while keeping the same items, fields, and renderer. The folder's View menu switches between the declared views without duplicating or rewriting any document.

Keep and share the looks that work

The Look library can be searched and filtered across your own, workspace, and built-in looks. A preview shows how many items and folders use a look before you apply it. Remix creates an independent personal copy, and Export writes a validated TextText look file.

Import can keep that file as a new look or, when its identifier matches a workspace look, create the next immutable version. Version history remains available, and restoring an earlier design copies it forward as a new version instead of rewriting history. Documents already using an older version keep their exact appearance.

Build through your agent

The App Store and browser editions use a workspace provider key to design the preview inside the focused builder. The standalone Mac edition may instead use an eligible connected ChatGPT or Codex account. A bearer-authenticated hosted MCP agent can also create the same complete item type through TextText tools. Tell the agent the destination folder and whether existing items should change. The saved type appears in the Look gallery like one made in the app.

Keep control

The preview is real, fields and views are validated, and Done is the only save action. Updating existing items is optional. Saved types are versioned, so later changes never silently rewrite earlier work.

Next, connect an agent or review the exercised feature inventory.