What's new

Insights now has one row per project with work left or recent activity: progress, tasks in review and not started, pace, estimated end, share of reopened tasks and last activity. Sort it by progress, end date or activity, filter by project label and jump to the project's Team tab in one click.

The Team tab has a chart with the tasks done day by day, the ones in review and the project's scope, extended to the estimated end date. Above it you see the maths: tasks per working day, how many are left and how many weekdays remain at that pace.

Pick Daily in Insights to see, day by day over the last two weeks, what was closed, sent to review and reopened across all projects and who did it, with a summary per person that includes logged hours. You can narrow it to one project or label.

The workspace_stats tool gives an agent the same figures as Insights: each project's progress, pace and estimated end, plus activity by day and by person. Your agent can put together the daily report without recalculating anything.

If someone else moves one of your issues from Done or In Review back to an earlier status, for instance after reviewing it, your bell shows that they sent it back to you. It works the same when an agent makes the change over MCP.

The MCP's estado_proyecto prompt (with the plugin, /hilbana:estado-proyecto) puts together a project's report: Team tab figures, who did what each day, the team's decisions and what's waiting for an answer, in one panel. It offers to send issues back or tell someone, and only does it once you say yes.

The project_team_stats tool gives an agent the same as a project's Team tab: progress, forecast, activity by day and by person, and progress by group, with readable names and identifiers.

A new guide explains how to run a project with agents in Hilbana, from decisions to the morning report: decide, specify, plan, build, audit by blocks and follow it. Each phase has its prompt in the MCP and its shortcut in the plugin.

The especificar prompt (with the plugin, /hilbana:especificar) writes one spec per area as a project doc, with acceptance criteria you can check, and reviews them against the decisions. When planning, each issue links its spec and takes its Definition of Done from it.

The auditar_bloque prompt (with the plugin, /hilbana:auditar-bloque) checks each issue in a block or milestone against its spec, its Definition of Done and the project's decisions, and offers to send back what doesn't pass with a clear comment. It only does it once you say yes.

The bandeja prompt (with the plugin, /hilbana:bandeja) goes through your unread messages and suggests what they mean for your issues: a comment, a status or assignee change, a new issue or a reply. It applies only what you confirm.

In Progress by group on the Team tab, each group shows who's behind it and the hours logged in the period. When grouping by parent issue you also see each block's status. Click any header to sort by that column.

If closing an issue involves deciding something that changes what was agreed, the closing comment records it in a decisions section. The daily report checks them against the project's Decisions doc, flags the ones that clash with something already accepted and adds the ones you approve to the doc.

When you set a milestone in bulk from a product view, the tasks an initiative delivers to it get the product's milestone and keep their own. Before, they lost the initiative's milestone and stopped showing up there.

If an agent over MCP or an integration through the API assigns you an issue or changes its status or priority, you get the same alert as when someone does it in the app. Before, for instance, an assignment made by an agent didn't alert anyone.

The new Team tab shows what each person closed each day, how many tasks are waiting for review and how each milestone, label or parent issue is moving. Pick the period (today, last week, 30 days, current cycle or any dates) and filter by person: the link keeps the view. Guests can't see it.

Write to anyone in the workspace from New message in the notification center, or from their card in Settings › Members. It lands in their bell, opens in a dialog, and they can reply in one click. You can also send and read them through MCP.

An agent can create a project's cycle or change its name and dates with the save_cycle tool, numbered the same way as from the app.

When a task is in In Review, the tasks waiting on it can be started and agents can claim them. Every status has an “Unblocks the tasks it blocks” checkbox in Settings › States, which only the owner and admins can change.

Copying an API key, an invitation link, webhook secrets and URLs, the mailbox address or recovery codes now shows a “Copied” notice at the bottom, like when you delete a task. It only appears if the clipboard accepted the text.

The help agent no longer claims something is impossible unless the documentation says so, and it checks other pages when one fits only partly. It used to say, for example, that you couldn't share the whole workspace.

On each project's Overview, the Updates section keeps its status history. “Draft with AI” prepares a draft from what happened since the last update; you review it, edit it and publish it yourself, and nothing goes out on its own.

Type / and pick Collapsible block to tuck away a log, some notes or an analysis. It is open while you edit; when you read it starts folded and opens when you click its title. It works in tasks, documents and comments.

When you read a description or a document, every heading has an arrow that folds its section up to the next heading of the same level. While editing, everything shows.

A button next to History switches between the reading width and all the available width, handy for wide tables. It remembers your choice in your browser.

Project updates can now be corrected and deleted, and publishing one notifies the project's members with a notification. Agents read them over MCP.

From the account overview you can turn on an email that arrives on Monday mornings with the week's activity, only when there was some. Send yourself a test one right away, and unsubscribe in one click from the email itself.

In the workspace switcher, «Leave this workspace…» takes you out of one you were invited to, after you confirm. The owner and the only admin can't leave, and neither can you if it's your only workspace.

Besides daily, weekly and monthly, a recurring task can now repeat every three months. When the target month is shorter, it lands on its last day.

In the project summary, drag each milestone by its handle (or move it with the keyboard) to put them in order. Every picker follows that order, and new milestones go to the end.

Collapse any milestone in the summary from its header to hide its tasks; the name, date and progress stay in view. Hilbana remembers which ones you collapsed.

Anyone can download their data or delete their account from Profile, including people who only joined by invitation and don't admin any workspace.

When an agent works on an initiative task that's delivered to a product, the sidebar shows the activity on both projects, not just the initiative.

Scrolling through a group of more than 60 tasks in the list could break the view. Not anymore.

In the help menu (?), «What's new» opens this changelog in the app's language. A dot on the button tells you when there's something new you haven't seen yet.

Drag the sidebar's right edge to make it wider or narrower, and Hilbana remembers your choice. Double-click the edge to go back to the default width.

Your agent can edit or delete comments under the same rules as the app: only a comment's author can change it. Editing doesn't notify anyone again.

Your agent can look up project labels and, if you own the workspace, create, change and delete them.

Every milestone in the Versions tab has its own version picker, so you can sort them out without opening each one.

A milestone's summary and a version's changelog are written in the language you use Hilbana in.

Tag each milestone with the version it ships in and see them grouped, with their progress, in the project's new Versions tab. From there, Hilbana writes the changelog for a version out of its milestone summaries, ready to copy as Markdown.

The bell now gathers what reaches you across all your workspaces, not just the one you have open. «See all» opens the full history, with unread and workspace filters and multi-select to mark or delete.

In Settings › States you decide whether the agent hands its work over for review or marks it complete. The workspace owner and admins can change it, and admins can now manage states and automations too.

A commit that mentions a task's identifier (DRAPPS-123, say) appears on the task, and GitHub shows a check on the commit that links back to it.

Settings are now grouped into Your account, Workspace, How you work, Agents & AI and Integrations. Groups collapse and remember which ones you left open.

Don't need it? Archive or delete it and pick where its tasks go. A workspace can now have no projects at all; in that case, creating or moving a task asks you for one.

The context menu on an initiative's tasks lets you set, change or clear the product, and a task opened from its product keeps that context. Projects in menus are listed alphabetically.

Opening a link to a task in another of your workspaces switches to it and takes you to the task. If you weren't signed in, you land back on the link after logging in.

Repositories covered by the integration are re-read from GitHub when you connect, when permissions change and when you open Settings. With «All repositories», the label says so.

The six states every workspace starts with now come with their colors instead of plain grey.

People with read-only access to a shared project can comment from the API and MCP, just like in the app.

A project can now be an initiative (work with an end) or a product (the repository where it gets built). Tasks in an initiative are delivered to a product and one of its milestones, and whoever sees the product sees what lands there without seeing the rest of the initiative.

Each product lists its repositories. When a PR from one of them mentions an initiative's task, the task is delivered to that product on its own. When you create a task in an initiative, you can split it by repository.

A moved task brings its sub-tasks at every level and leaves the old project's cycle behind. Its previous identifier keeps working in links, mentions, search and the MCP, even if you change the project's prefix.

If it goes to the same product it keeps its version, and sub-tasks delivered to another product stay in the initiative. You're asked to confirm first, on the task and in bulk.

A task's relations show the other task's state, and an agent can't start a task while an unfinished one blocks it. When closing a task, the MCP also reminds the agent to leave a comment for the reviewer.

The comment a PR leaves when it delivers a task to its product no longer shows up as «Deleted user».

It no longer opens the keyboard by itself and, with the keyboard open, fits the visible part of the screen.

The preview of a mentioned task closes when you open the link instead of staying on screen.

The «?» menu now has a chat that answers from the docs, plays the short video for what you ask without leaving the app and, if that's not enough, hands you to support with the conversation already written. Each plan has a daily question allowance, shown as a bar.

If you own one or more workspaces, you get one view with the numbers, the agents and what needs attention across all of them: stuck tasks, failed agent runs, milestones and cycles at risk and stalled projects. It updates live and comes with the paid plans.

From a sub-task's context menu or its page, detach it from its parent and make it a standalone task.

Billing, the audit log, integrations, imports and workspace configuration are managed by the owner, and Settings no longer shows them to people who can't change them.

Long text fields open with a double-click or the «Edit» button that appears on hover. A single click no longer starts editing.

Through the MCP, an agent can list, create and delete documentation folders and move documents between them.

If you can't edit a task, its context menu only offers to copy its identifier and its link.

Mentioning a task with its project's own prefix now creates the link, the preview card and the backlink, and shows up in autocomplete.

When listing projects, an agent sees exactly the ones you would, General included.

When a change or comment comes through the MCP or the API, the history signs it as «Ana (via laptop)», with the name of the key that was used.

Type a saved view's name in the command palette and open it with its filters applied, even if you're already on the list.

Each action is translated, with a summary of the details and names instead of IDs. A sign-in attempt with an unknown email no longer shows up as «deleted account».

The report the AI writes, and its error messages, come out in the language you use the app in.

The catalog in Settings › Agents lists all 38 MCP tools, with none missing.

Search in a project's docs finds the word you're typing before you finish it, shows that it's searching and displays clean snippets.

When a PR moves a task to another state, the history says «GitHub PR #42» instead of «Someone».

When you create a new label from a task, it's applied to that task.

When you create a project or an epic from a template, its sub-tasks come out in the order they have in the template.

Tasks from people who couldn't be matched to a member count as «Unassigned» in the summary.

Guests no longer see the PR section or the prompt to connect GitHub.

In velocity, each number sits right above its bar. The «At risk» or «Overdue» tag wraps under the date instead of being cut off. In the calendar, the selected day and the month arrows are readable.

A pending invitation says it «will take a seat once accepted», your row in Members shows your role translated, plan cards say «Unlimited projects» and the project page says «Delete project».

With the Odoo invoicing module, the client report takes unbilled hours to a draft invoice in your Odoo, with the right customer and service, and marks them as invoiced. It works with Odoo 16 and later.

Through the MCP, an agent can create, edit and delete labels, on top of adding and removing them on tasks.

If you use the app in English, MCP messages and the screens for connecting Claude are in English too.

Subscribing to a plan with modules happens in one go, and a module that needs another one adds it for you.

The timesheet has a button in its header that opens the client report for the same project and period, and tells you how many hours are still unbilled.

When you scroll down a long table, the header row stays at the top so you can still tell what each column is.

They were created without a team and didn't behave like the ones made in the app. They now get the workspace's team, and existing ones have been fixed.

Creating, editing and deleting labels now checks the person's role on the server as well.

Connect your Bitbucket Cloud account in Settings › Bitbucket and PRs that mention a task show up on it, just like with GitHub. A milestone's AI summary takes them into account too.

When you log or edit time, you can mark it as billable to the client or as internal work. By default, every hour is billable.

The button stays busy while it takes you to GitHub and no longer accepts a double click.

The list of Settings sections scrolls on its own, on mobile and desktop, even when it doesn't fit on the screen.

Bring an Asana project into Hilbana with its tasks, states, labels and comments. Connect it with a token from Settings › Import.

Your subscription now belongs to your account, not to each workspace: you pay once and the plan covers all of yours. People count once even if they're in several, and storage adds up. Only the account owner manages billing.

In Settings › Members, the «Whole account» view lists each person across your workspaces once, where they are and whether they take a seat on your plan.

The board has the same filters as the issue list, milestone and assignee included.

The Team plan includes 10 people, and the limit notice now says so.

Authorizing the connection failed at the confirm step. And with desktop apps that pick the session up on their own, you now get a page confirming you're connected.

The help menu («?») now lets you write to support without leaving Hilbana. Your message reaches us with the context we need, and we reply by email.