Views

A view is a saved way to see a list: as rows under headings, as a board with a column per value, or as a table with a column per field, grouped, sorted and filtered as you like. Views are tabs on the board, the same for everyone on the project, and agents can make them when you ask.

On the board

Above each list are its tabs: By section, the list as it is, under its headings; then each saved view by name.

+ New view opens a menu of ready-made views that fit the list, such as "Board by status", "Most important first", "Ready to start", "Waiting on something", "Who is on what" and "Recently done". Under them, "Or start from nothing" makes a blank List, Board or Table, with its name selected so you can type one.

The bar over an open view changes it, and every change is saved at once, for everyone and their agents:

• The name: click it and type.
• The layout: List ("Rows under group headings"), Board ("A column per value") or Table ("A column per field").
• Group: the field to group by; on a board, "Columns: prio".
• Sort: by any field, oldest or newest first, most or least important first, A to Z.
• + Filter: "Keep only the items where" a field has the values you tick. Each filter shows as a pill with an ×.
• Columns, on a table: which fields it shows.
• …: Duplicate, or Delete the view.

On a board view you drag a card to another column to change its field. A view that hides items says how many: "3 of 12 hidden by this view's filters."

Every list, the last tab in the left column, has no list of its own: only views that show tasks, requests and questions together, each with its list as a field, like "Everything open" or everything for one person.

How an agent makes one

The view tool makes, changes and removes views. Agents make one only when you ask to see the lists a certain way, and the reply says what it shows:

view(name: "Most urgent", layout: "table", sort: ["-prio"], show: ["prio", "area"])

V-ed8w@1  Most urgent: table of backlog, sorted by -prio, showing prio, area
  shows: Table of backlog: 8 of 8 tasks; sorted by prio high to low (most important or newest first); showing prio, area

view(name: "By priority", layout: "board", group: "prio", order: ["high", "medium", "low"])

V-yqtx@1  By priority: board of backlog, grouped by prio (high, medium, low)
  shows: Board of backlog: 8 of 8 tasks; columns by prio: high 1, medium 1, low 1, no prio 5

A view that shows nothing comes with a warning, so the agent can fix it: warning: it shows nothing right now: no task passes its filters. A field no item has is refused, with the fields in use and a guess at the one meant.

view() with nothing lists them all; key with changes edits one; delete: true removes one.

Suggested views

An agent may also suggest a view nobody asked for, with suggest saying why it helps:

view(name: "Waiting", filter: ["blocked=waiting"], suggest: "see what waits on your answers")

V-pcbf@1  Waiting: list of backlog, only blocked=waiting (suggested by codex, waiting for the human to keep or dismiss it: see what waits on your answers)

On the board it appears as a card above the tabs: "Codex suggests a view: Waiting", with what it shows and why, and three buttons: Look, Dismiss and Keep it. It becomes a tab only once you keep it.

The fields a view can use

Any of the items' own fields, and the built-in ones:

Field	Means
status	the list's status words
section	the heading it is under
done	done or not
blocked	whether it waits on something still open
claimed	who is on it
by, at	who added it, when
doneat	when it was done
needs	what it waits on
list	its list, in a view of every list

Filters are field=value, field!=value or field=a|b, and all of them must hold. A sort of -prio is high to low.

Limits

• A view's name is one line, up to 80 characters.
• Views belong to the project: everyone on it sees the same ones, and deleting one deletes it for everyone and their agents.
• On a read-only board you can look at views, but not make or change them.
• Views go out with an export in .hamloy/views.md.