Padar

Changelog

Older releases — page 5 of 10.

1.4.26

Decide how much the agent asks

Change the mode on a workspace that is already running, from any device — and it is remembered the next time you start one. When the agent finishes planning, it asks what to do next in words that say what agreeing will do, and the plan itself is something you can read.

New

  • DesktopA finished plan opens in its own tab, formatted, and stays readable afterwards on the step that proposed it. It used to collapse into a line of raw data the moment you answered.
  • DesktopThe mode you work in is remembered, so a new conversation or a new workspace opens in it instead of starting over. It follows you to your other machines and to the phone.

Improved

  • DesktopWhen anyone changes the mode, everyone in the workspace sees it change.
  • DesktopFinishing a plan asks which mode to continue in — edit without asking, or ask before each change — instead of a plain Allow that said nothing about what agreeing would do. Declining leaves the agent planning rather than stopping the turn.
  • MobileThe plan card on the phone reads the same way: the plan is formatted, and each choice names the mode it continues in.

Fixed

  • DesktopChange the agent’s permission mode on a workspace that is already running. The picker was locked unless you happened to be the one who had just started the conversation — so reopening a workspace, restarting Padar, or joining from a second device left it stuck.
  • DesktopA mode the agent moved into itself now sticks. Approving a plan and coming back later used to put the conversation back in the mode it had left, with nothing saying why.
  • DesktopA new conversation no longer starts by running everything without asking. That was the fallback whenever a conversation had no mode of its own — a new workspace, or one whose agent had been reclaimed — and the only sign was the mode pill.
  • DesktopThe row of controls under the composer stays still when you move between workspaces. The mode, the MCP button and the meters used to blink out and shuffle sideways for a moment while the new conversation came up.
1.4.25

Compact a conversation and it stays readable

Compacting filled the chat with thousands of blank rows and left it slow to scroll. It does not any more — and the markers that punctuate a conversation stay put instead of vanishing the moment the agent answers next.

Fixed

  • DesktopCompacting a conversation no longer fills it with rows you cannot read. Opening and scrolling a long chat is quick again, and scrolling stays where you put it.
  • DesktopConversation cleared, Context compacted and what a slash command answered all stay in the conversation. They used to disappear as soon as the agent said anything after them, including every time you reopened the chat.
  • DesktopConversations you have already had are put right when you reopen them, not only new ones.
  • MobileThe phone keeps those same markers, and no longer skips a message it was not built to draw.
1.4.24Engine

Your agent can work Linear tickets from a remote workspace

Ask the agent to comment on a ticket, move it, or link a pull request while you are in a remote workspace and it said the workspace did not exist. It does the work now — tell it which ticket, and it will.

Improved

  • In a remote workspace, tell the agent which ticket you mean. It cannot yet pick up the one the workspace was created from, and it now says so plainly instead of reporting the ticket as missing.

Fixed

  • The agent can create Linear issues, comment on them, move them between states and link pull requests from a remote workspace. All four refused, saying the workspace could not be found, while the same requests worked in a workspace on your own machine.
1.4.23Desktop

The agent answers again in workspaces on your own Mac

On some Macs a workspace on your own machine would take your message and never reply. It answers — and on the rare occasion the agent genuinely cannot start, the conversation now tells you why instead of going quiet.

Improved

  • An agent that cannot start now says so in the conversation, and says what went wrong, instead of leaving you watching a reply that never comes.

Fixed

  • The agent starts in workspaces on your own machine. On Macs without a developer copy of Node installed it could not start at all, which showed up as a conversation that accepted your message and never answered — while files, diffs and terminals in the same workspace worked normally.
1.4.22Desktop

Resize a workspace without losing your place

Changing a workspace’s size or setting it idle now happens while it keeps running, so your terminals, agent conversations and files stay exactly where they were.

New

  • Starting a process, task, service or the environment on an idle workspace wakes it and runs what you asked for once it is back. The row says Queued until then.

Improved

  • Growing, shrinking, idling and waking a workspace happen in place on most machines. Nothing restarts, and there is no confirmation step before the change begins.
  • While a change lands, the memory and CPU gauges say what is happening in their place. If the workspace is waiting for memory to free before it can shrink, Free memory stops what can be started again and lets the shrink finish.
  • New workspaces start idle, so they cost nothing until you start something in them.
  • Memory and CPU readings refresh every two seconds, and CPU is averaged over a few seconds so it no longer jumps around.

Fixed

  • Setting a workspace idle keeps your services’ data. A database comes back with everything it had when the workspace wakes.
  • New files show up in the file tree and in ⌘P straight away.
1.4.21

Your first workspace comes up working

Spinning one up before you had connected Claude or GitHub used to give you a workspace that failed at the first thing it tried. Now it says which connection is missing and takes you straight to it.

Improved

  • DesktopThe setup checklist counts GitHub among the steps that block your first workspace, so the number of steps left is the number that actually stands between you and one.

Fixed

  • DesktopSpinning up a workspace names the connection you are still missing — Claude, GitHub, or both — and offers to go and make it. Before, it let you through and handed you a workspace with no agent to run it and no repository in it, with nothing on screen saying why.
  • MobileThe phone stops before it creates one too. Connections are made in the desktop app, so it says which is missing, where to make it, and lets you check again without restarting anything.
1.4.20Engine

Your agent can see the screenshots on the ticket

Start a workspace from a Linear ticket and the agent now sees the pictures on it, not just the words. Until now a screenshot reached it as a link it could not open — so on the tickets where the picture is the clearest part of the description, it was the only one working blind.

New

  • A workspace started from a Linear ticket opens with that ticket’s screenshots in front of the agent, alongside the description and recent comments — on its first turn, without being asked.
  • Pictures in the ticket’s recent comments come along too, not just the ones in the description.

Improved

  • It reads the same whether the workspace is on your own machine or a remote one, and a ticket with no pictures opens exactly as it did before.
1.4.19Desktop

Start a workspace exactly where you want

Creating a workspace now lets you choose what it forks from — a branch, a Linear issue, or an open pull request — and which branch it compares against. And Padar can reach your repositories through a GitHub App installed on your organisation.

New

  • Start a new workspace from an open pull request. It lands on the PR’s branch, with its commits and its base, ready to pick up the review.
  • Start from an existing branch or a Linear issue too, not only a fresh branch off the default.
  • Choose which branch a new workspace forks from when you create it, rather than always taking the default.
  • Install the Padar GitHub App on your organisation, and project setup shows at a glance whether it can reach the repository you are pointing at. Manage the installation — Sync or Install — from Settings.

Improved

  • When the branch name you pick already exists, you choose what happens — work in it, start a new branch, or rename — instead of Padar quietly adding a “-v2”.
  • The Changes tab remembers the branch you are comparing against, per workspace, so it survives closing and reopening — and starts from the base your project is set to rather than a stale one.
1.4.18

Padar tells you when it needs you

Desktop notifications asked for permission in the middle of tagging somebody, and then went quiet at the moments that mattered. They arrive now — and a new inbox keeps hold of anything you missed.

New

  • DesktopYou are told when an agent finishes, when it stops to ask you something or wants your approval to run a tool, and when a teammate tags you — whether Padar is behind another window or minimised. Clicking the notification opens that workspace on the conversation it came from.
  • DesktopA bell in the title bar holds everything that has asked for you, so a notification you missed is still there to find. ⌘⇧I opens it from anywhere.
  • DesktopBeing tagged, an agent waiting on you, and an agent finishing are three separate switches in Settings. Turn off the constant one and the rare one still reaches you. They follow your account to every device you sign in on.
  • DesktopFollow a workspace, or go quiet on one, from its row in the sidebar — without going quiet on all the others.

Fixed

  • DesktopPadar asks for notification permission once, when you first open it, rather than the first time somebody tags you.
  • DesktopEvery workspace can notify you, not only the ones running on your own machine. Agents working anywhere else finished in silence.
  • DesktopThe @ picker offers only people who can actually open that workspace, so a tag cannot quietly reach nobody. Invite somebody to the workspace and they appear in it.
  • EngineA tag naming somebody Padar could not place reaches nobody, rather than notifying everyone else on the workspace instead.
1.4.17Desktop

Machines you can tell apart

One of the machines running your workspaces was going by an unreadable name nobody chose. It has a real one now, everywhere Padar mentions it.

Improved

  • Machines show the name they were given rather than whatever they registered themselves under. A machine nobody has renamed looks exactly as it did.
  • When a project runs out of room on a machine, the message names that machine the way the rest of the app does, so you can tell which one is full.

Three hours of work.Two days to ship.

Agents made writing code fast. Deciding is what’s left.Padar puts the whole team in the same workspace. Upgrade your collaboration now.

Also on
Or talk to us