Changelog

New

• Ask it to bring your project up and it starts the processes and services your project defines. They appear in the workspace panel with their ports and their logs, exactly as they do when you start them yourself — instead of running somewhere nobody can see.
• It can stop the workspace when a job is finished, so a machine is not held by work that is already done. Your branch and your conversation are waiting when you start it again.

Fixed

• Your agent can comment on a Linear issue, move it to another state, attach a link to it, open a pull request, merge one, and start a GitHub Actions run. Every one of those used to come back as “I’m not able to do that”.

Improved

• Those two are named for the machine they move, so they are no longer easy to mistake for the buttons that start your project’s own services.

Fixed

• Start and stop a remote workspace from the Machine section. Stopping shrinks it back to its idle size and gives the capacity back to your team.

Improved

• EngineStarting a workspace again is faster. It no longer downloads the repository and reinstalls everything from scratch — your dependencies are where you left them.
• DesktopStarting or stopping a workspace only warns you about work that is genuinely at risk, and says nothing when there is none.

Fixed

• EngineA workspace keeps your uncommitted changes, your untracked files and a .env you wrote by hand when it stops, when you resize it, and when it restarts on its own.
• EngineA workspace that failed to open used to fail the same way every time you tried. It clears the problem out of the way and opens.
• EngineYour conversation comes back after a workspace restarts. It sometimes said the session could not be found, when nothing had been lost.

Improved

• DesktopThe agent keeps going through a brief disconnection. It used to lose the turn outright, and git would lose access to GitHub with it, if the connection dropped for a second.
• DesktopNew workspaces come in 1, 2 and 4 vCPU. Existing workspaces keep the size they already have.
• MobileA teammate you tag reads as a person on your phone rather than as raw text, and the notification opens the workspace they were tagged in.

Fixed

• DesktopYour other workspaces keep working when one stops responding. Requests to a workspace that has stopped answering now give up instead of waiting forever, so nothing else queues behind them.
• EngineA workspace that stops responding is rebuilt for you, in about a minute, instead of sitting there until someone notices. Anything you had not committed in it does not survive the rebuild — push before you step away.
• DesktopThe agent can tell when a message is addressed to a teammate rather than to it, and stays out of the way.

New

• Review a pull request inside the workspace. The Review tab shows the PR — its description, whether its checks are passing, and each reviewer's verdict — next to the code it is about, so you can catch up without switching to the browser.
• Comment on the diff, line by line. Review comments appear inline on the changed code, and you can post a new one, reply to a thread, or delete your own — all from the diff.
• Open a pull request from the app. Create PR pushes your branch and opens the PR for you, so a new review starts without leaving Padar.

Improved

• The Changes list tells you where each file stands. Filter by everything, files with comments, or what you have pushed and have not yet — and see at a glance whether the branch already has a PR open.

New

• Bring a workspace to your own localhost. A remote workspace's services — its app, its API, its database — show up on your machine on the same port numbers the project expects, so you can open and test the whole running stack from your own browser without leaving your laptop.
• Padar checks those ports before it forwards. If something on your machine is already using one, it names the program holding it and gives you the command to stop it — or frees it in a click, one port at a time. The ports that are free forward on their own, so a single port you are already using no longer holds up the rest.

Improved

• When another workspace already has these ports on your machine, the panel names it and forwarding here takes them over — instead of quietly offering to forward ports that were plainly in use.

Improved

• DesktopSearch, the command palette and the agent chat no longer suggest what you typed before, and no longer underline code as a spelling mistake.

Fixed

• MobileA branch name typed on your phone is the branch name you get. The keyboard was capitalising the first letter and swapping words as you went, so the workspace came out under a name you never typed.
• MobileQuotes and dashes in a message to the agent stay as you typed them, instead of being curled into characters that change the code you were quoting.

New

• Tag a teammate in the agent chat. Type @ and their name — a first name, a full name written with a dot, or their short handle — and they get a notification that opens the workspace on the conversation you tagged them in, whether or not they were following it.
• The @ list shows everyone on your team, each with their address beside their name, so two colleagues who go by the same name are easy to tell apart. Picking one always tags the person you picked.
• A name that could mean two people asks you which one you meant, rather than sending the message having reached neither.

Improved

• A connection that has been revoked says so and offers Reconnect, instead of showing as connected and failing everything you do with it.

Fixed

• Your projects load first time in the morning. The first thing you did each day could fail and then work when you tried it again.

New

• DesktopSign in to MCP servers that register themselves, Supabase among them. Press Connect and authorize in your browser — no token to find and paste.

Improved

• DesktopThe MCP list is there in a conversation even when nothing loaded, and says that the list is read once when a conversation starts — so a server you have just added arrives on the next one.
• DesktopA server that cannot connect says what went wrong instead of showing a number. In a teammate's workspace, their servers are labelled as theirs rather than as yours.
• DesktopDeclaring a server that no workspace could run warns you first — a command that is not there, an address that only exists on your own machine, a value your shell sets that a workspace has no way to know.
• EngineServers that run on bun work in a workspace. They had no way to run at all before.

Fixed

• DesktopPadar asks for a token only where a server wants one. A server that needs no credential used to show an empty field for one anyway, which read as something you had forgotten to fill in.
• DesktopA server that needs signing in now says so about itself. Beside a list of names, in an app you are already signed in to, "needs sign-in" looked like it meant you.
• DesktopImporting finds every server your plugins declare. Supabase's was missed completely, so the easiest way to add it was the one that did not work.