Release notes

A selection of what changed for users, newest first. It covers versions 0.8.1 down to 0.7.3 and leaves out internal changes and small fixes. Earlier versions are not listed.

• What you may do comes from your Vartari plan. After you sign in, DevHub reads the permissions your account carries for each area, at the level read, write or manage. Anything your account does not include stays visible but disabled, with the permission it needs. Nothing on your disk is removed because a permission is missing. See Plans and tiers.
• The MCP server follows the same permissions. It starts only when your account may run it, and each tool is offered only at the level it needs. Deleting files, running scripts, starting agents and taking screenshots need the manage level.
• An account without a plan is shown as “Unsubscribed”.
• Without a network, DevHub uses the permissions it last received, for at most 72 hours. A version installed while offline has no permissions until it has been online once.

• Sign in with Vartari ID in your browser. DevHub never sees your password. A session lasts seven days, and from 24 hours before its end the main window warns you and offers Sign in again. See Sign in.
• Signing in is required. When the session ends or you sign out, DevHub returns to the sign-in screen and the MCP server stops. Without a network it keeps working for at most 72 hours after it last reached Vartari ID.
• Each Vartari account works in its own workspace profile. After signing in you choose an existing one or create a new one. Settings lists the profiles on this computer, with Rename, Duplicate and Remove entry. See Workspace profile.
• A new look and shell: a title bar, a status bar, a sidebar that folds to icons and a command palette on ⌘K. Settings has eight sections with a Save bar. See Settings.
• The interface speaks Polish and English. Choose the language in Settings > General, or follow the system.
• The Dashboard shows how long the MCP server has been running next to its status.
• Plans, Analyses, Vartari Agents and the library pages were rebuilt. Vartari Agents has a Sessions tab with a live view of what runs.
• Text size now scales the whole window, and the layout reflows at the largest size. The Vault Viewer and Repository Index windows no longer break at 200% text size or in a narrow window. See Accessibility.
• Your Vartari account picture shows in the title bar, the account menu, Settings and the tray.

• A new look in light and dark. Choose Match system, Dark or Light in Settings > Appearance, or with the button in the title bar.
• Accessibility settings: text size, interface zoom, font, contrast, reduced motion and underlined links. See Accessibility.
• A new Dashboard: server status, calls, latency, a 24-hour activity chart, a “Needs attention” list and quick actions.
• Pages are easier to read: Activity has one toolbar with filters and search, library pages share one toolbar, and empty pages say what to do.
• Graphs are drawn on a canvas and are much faster, and can be used from the keyboard.
• One Vault Viewer for the whole organization: a vault opened from an organization shows its sibling vaults, and [[Vault Name:note]] links into another vault. Graph can show all vaults at once.
• Export a note to PDF or print it.
• A better Canvas: your file is saved without losing unknown fields, with link previews, drag and drop, ten card shapes, HTML cards, undo and redo, and keyboard navigation.
• The desktop pets are redrawn and the pet scales as one piece with its speech bubble. See Desktop Pet.

• Agents can see their own vaults and get the DevHub tools their skills send them to. A read-only agent writes nothing. Every agent works only in its own repository.
• Long agent runs keep their answer. You can watch a Codex or Claude Code run live in Sessions, or replay it afterwards.
• A run can be given leave to start other agents. It is off by default.
• An agent can have a name and an avatar.
• DevHub checks for updates half a minute after start and every six hours. Nothing is downloaded or installed until you ask.
• Agent calls no longer fail with “connection failed” after a long model turn.

• Agent runs start in repositories where DevHub detected a stack. They used to fail at once.
• One agent per role: an agent has a default model and effort, plus a list of other models and efforts it may be called with.
• An agent can be set up completely over MCP, without the dialog.
• A run no longer leaves the repository with a modified file.
• Harnesses > Manage has a Copy command button for every folder set up for a terminal client. See Harnesses.