A view is one of the fundamental structures in Craft.io, and it carries more than a layout. Its filters, grouping and sort order define a slice of the product with a specific meaning: what the team committed to this quarter, or which requests are still unanswered. That meaning is exactly the context an agent needs, and until now none of it reached the agent. It had to be re-described in every prompt.

With this update, naming a view is enough. An agent can pick up that view's full setup: its filters, its sort-by, group-by and swim-lanes-by controllers, and its columns or card layout. An agent can then do the work on that same set of items: analyze it, report on it, or update the items in it. It can also list the views a workspace or portfolio holds, by category and owner type, the same list the views menu shows.

A "Delivery Risk" view might carry a dozen filters the team settled on together. Pointed at that view, an agent works on the same items the team does, rather than on a set reassembled from a prompt.

To use it, name a view in any MCP-compatible tool, such as Claude, Cursor or VS Code.

An agent could already produce a genuinely useful result: the right items, filtered, sorted and grouped. That result then stayed in the chat. Handing it to the team meant rebuilding it by hand in Craft.io.

With this update, an agent can create a table, kanban, timeline or swimlanes view and return a link that opens it. It sets the filters, the controllers, and the columns or card layout, and saves the view as a personal view or a workspace view in the category you name.

"Build a table of every Q3 epic with no owner, sorted by importance, and save it to the team's Planning category" produces a view the whole team can open, not a list in a chat window.

To create one, describe the view you want and ask the agent to save it.

A saved view does not stay accurate on its own. A "Current Sprint" view stops being current the moment the sprint ends. Keeping views right is a steady trickle of small edits.

With this update, an agent can edit a saved view's filters and controllers in place. It stays the same view, so everyone already using it sees the change.

"Point my Current Sprint view at Sprint 180" moves the sprint filter on the view the team already has open, instead of leaving a second, near-identical view beside it.

To update a view, name it and say what should change.