Views and search

Intabula shows a collection as a sortable, filterable table or a Kanban board grouped by a select field. You can save a view to the sidebar yourself, or ask the agent for one in a sentence.

Table and Kanban

The table view shows records as rows with their typed fields as columns, and you can sort and filter on any of them. The Kanban view groups records by a select field, such as a status. Both views read the same Markdown files, and clicking a card or row opens the full note.

On a saved Kanban view you can drag cards to reorder them inside a column. The order is stored with the view in .intabula/views.json, and the record files don't change. With no sort set, a view uses this manual order, and cards you haven't dragged follow the placed ones, oldest first.

Created and updated dates

Every record has two dates that Intabula tracks outside its frontmatter. createdAt is stamped the first time Intabula indexes the record and kept in .intabula/tracking.json, so sync tools that reset file times don't change it. updatedAt is the file's modification time, so edits made in any app count. The record panel shows both, and saved views and the agent's query_records can sort by either.

Saved views

A configured view (collection, filters, sort, grouping) can be saved to the sidebar and reopened any time. The agent creates them with the create_view operation, so "show me a board grouped by status" becomes a permanent sidebar entry. Records and collections can also be pinned to Home; see Getting started.

Full-text search

Search covers titles, frontmatter fields, and note bodies across the whole vault, and it is accent-insensitive: searching "Lodz" finds "Łódź". The command palette opens with ⌘K or ⌘O. With an empty query it lists your recent drafts and recently opened records. As you type, it shows matching drafts, collections, records, and past agent conversations, and its last row sends the query to the agent as a question. The agent uses the same index through search_vault.

Backlinks

Every wikilink is indexed both ways. "What links here" is available in the UI for any record, and to the agent as the get_backlinks operation, so it can trace relationships before renaming or reorganizing.