Changelog

New

• Every workspace row shows a live status: its agent working or waiting for your reply, its environment starting or running, and whether its ports are forwarded to your machine — folded into one mark so a glance is enough.

Improved

• Local and remote workspaces read the same way, and a workspace whose environment is running shows a green plug so the live ones stand out.

Improved

• Sorting the workspace list by My activity now orders by when you last sent a prompt in each one, not the last time you opened it.
• Sorting by Global activity orders by the last prompt anyone sent, so the workspaces your team is actively working in rise to the top.

Fixed

• The agent in a new workspace starts again. After the last update it could stop before it began, so the agent pane never answered.

New

• DesktopWhile a workspace sets those plugins up, the agent pane says so. If one could not be installed, it tells you which.
• EngineA ticket started with a Padar label links to its workspace from its first Linear comment, and from the pull request it opens.

Improved

• DesktopPlugins your project turns on in its Claude settings, superpowers for example, now load for the agent in every workspace. They used to load only on a machine where somebody had installed them by hand.
• DesktopAn agent started from a Linear ticket that needs design researches it first and asks you every open question before it writes any code. A small, clear fix still goes straight in.
• MobileWhen the agent stops to ask you something, the notification shows the question itself, not that it is waiting on your approval.

Improved

• DesktopA workspace whose machine is asleep or shut down now says so, and is worth coming back to. It used to report that the workspace did not exist.

Fixed

• DesktopA workspace that lives on a teammate's machine opens when you go to it. Its name, branch, conversation and files all arrive, and you do not switch machines to get there.
• DesktopA machine that moves, gets renamed, or leaves the team no longer sits in your machine list as a row nothing can reach.
• EngineLosing access to a private workspace stops its notifications. Being removed from one used to leave your bell in place, so you kept receiving its updates and a preview of what the agent had said.

New

• Opus 5.5 is in the model picker, and a new conversation uses it without you choosing anything.

Improved

• If you pinned a model, you stay on it — a pin is a decision Padar will not quietly undo. Pick Opus 5.5 from the picker when you want to move.

New

• DesktopClick a screenshot in the conversation to open it full size.
• EngineTwo Linear labels instead of one. The "padar" label starts a run you can answer questions in; "padar auto" is the one that tells the agent nobody is watching, so it finishes the work, tests it, opens a pull request and pauses the machine on its own. A ticket carrying neither is left alone.

Improved

• DesktopSend the terminal to the centre column when you need the width, and back to the sidebar when you do not. Padar remembers where you put it for each workspace, ⌘J brings it up wherever it is, and your shells keep running as it moves.
• MobileThe working indication sits above the composer, so scrolling back through a long turn no longer hides the one thing telling you the agent is still going.

Fixed

• DesktopTables in the conversation keep their words whole — the first column no longer breaks words down the middle.

New

• Sort your workspaces from a new control under Workspaces: by date created, by your own recent activity, or by the last message from anyone. Padar remembers your choice.

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.