Vaiz Summer Update: time tracking, a smarter Inbox, bulk actions & memory for coding agents
Hey guys,
We shipped quite a few Vaiz updates this summer, covering versions 2.88 through 2.94. Here’s a quick rundown of the changes that should be most useful to project managers and their teams.
Time tracking and cost calculation
We introduced Power-ups, optional features you can enable for yourself or across the whole workspace.
The first two are Time Tracking and Cost Calculation. You can now start a timer from anywhere in Vaiz, add time manually, review tracked hours inside a task, and calculate costs using hourly rates.
So now you can check whether “this should only take an hour” was a realistic estimate or just optimism with a deadline.
Bulk updates for tasks
Bulk actions can now handle much more than before.
Select multiple tasks, including tasks in subtask and milestone tables, and update their:
- status and assignees;
- custom fields;
- board group;
- milestone.
You can also archive multiple tasks at once. Automations, notifications, and history still work as expected when you make changes in bulk.
It’s a small thing until you need to update 40 tasks five minutes before the Monday stand-up.
A simpler Inbox
We replaced the old Notification Center with a redesigned Inbox.
It opens as a side panel and separates notifications into Unread, Pinned, and Read. You can reply to comments, add reactions, and pin updates directly from the Inbox instead of opening each item.
You can also choose which notifications you want to receive in Vaiz, by email, through push notifications, or in Slack.
Your notifications are now organized, even if the rest of the project is currently “in progress.”
More useful search and history
Search results now include the task ID, board, and project, so it’s easier to tell similar tasks apart.
Changes to custom fields, including dates, estimates, members, and related tasks, are now recorded in Activities and History as well.
That should make investigating “Who changed this, and when?” a little less dramatic. The answer might still be you, but at least now you’ll know.
Memory for coding agents
Coding agents connected to Vaiz through MCP clients such as Cursor, Codex, and Claude Code can now create and search devlogs.
A devlog captures what the agent tried, what it changed, what didn’t work, and why. That context stays with the task and can be picked up in a later session.
In other words, the next agent doesn’t have to rediscover the same dead end from scratch. Humans have retrospectives. Agents have devlogs.
A few more things
We also:
- redesigned onboarding for new teams;
- added inline editing to subtask and milestone tables;
- improved workspace updates after reconnecting or returning to an idle tab;
- made assignee notifications more reliable;
- fixed issues across Smart Lists, Slack, GitHub, comments, documents, and billing.
That’s the short version of what we worked on this summer.
Which of these updates will be most useful for your team? What would you like us to improve next?
Full release notes: 2.88 · 2.89 · 2.90 · 2.91 · 2.92 · 2.93 · 2.94
We’re excited to hear your feedback!
The Vaiz Team
Posted Sep 2, 2026, 12:38 PM UTC