Padar

Changelog

1.3.23

Decide what the agent may do before it does it

Every session used to run everything without asking, and that was the only way it ran. Now you pick — plan first, ask before each edit, or keep going as before — and when the agent needs you, you answer it on the card that asked.

New

  • DesktopChoose how a session runs, from the pill under the composer. Plan explores and proposes before writing anything. Manual asks before every edit and command. Edit automatically works inside the worktree and asks before anything wider. Auto approves what passes a safety check and pauses on anything risky. Bypass permissions is still there — it is just no longer the only option. ⇧Tab cycles them without leaving the composer, and the mode you pick sticks to that conversation.
  • DesktopWhen the agent needs permission, you answer on the tool card that asked for it, rather than hunting for a separate prompt. It can also stop and ask you a real question mid-run, and wait for your pick before it carries on.
  • MobilePermissions and questions reach the phone too. Answer them from a sheet, and change the mode of a running session without going back to the desktop.
  • DesktopA run in a workspace you made tells you when it finishes or fails, with nothing to switch on first. It stays quiet only while you are actually looking at that workspace — an app left open on a long run was the one case guaranteed to tell you nothing. Switch it off per device in Settings under Account.

Improved

  • DesktopThe model menu says when it is offering built-in defaults instead of the models your account can actually use, and it goes and fetches the real list when you open a workspace. It used to stop trying shortly after the app started, and never say which list you were looking at.

Fixed

  • EngineSigning a workspace in takes effect straight away. It could carry on using the previous credential indefinitely, with nothing to tell you it had.
  • EngineOne workspace failing to start a session no longer stops every other workspace starting one.
1.3.22

How long has it actually been working?

The count beside a working agent belongs to the turn now, not to how long you have been watching it. Leave the workspace, come back, and it is still counting.

New

  • EngineThe agent can put a screenshot on a Linear ticket. It uploads the picture and hands back a link that renders in a comment or in the ticket description.

Fixed

  • DesktopThe timer beside a working agent keeps counting when you leave a workspace and come back. It used to start again from zero, so you could not tell a turn that had been running ten seconds from one that had been running ten minutes — which is usually why you left it in the first place.
1.3.21Desktop

Your whole team’s tickets, narrowed to yours

A project can follow an entire Linear team now, so the tickets nobody filed under a project stop being invisible. Your queues open on the ones assigned to you.

New

  • Your queues open on the tickets assigned to you. Pick a teammate to see theirs, or Everyone for the whole board — which is also where unassigned tickets live, since they belong to nobody.
  • When a project follows a whole team, a project picker sits above your queues and narrows them to one board for as long as you want it, without changing what the project is linked to.

Improved

  • Link a project to a Linear team, then pick one of its projects — or all of them. All projects covers everything the team owns, including the tickets that were never filed under a project and that no board could show you before.
1.3.20Engine

Your agent can act on the ticket

Ask it to comment on a Linear issue, move it along, or open a pull request, and it does. It had been answering that it was not able to — every time, for everyone.

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”.
1.3.19Desktop

Stop a machine you have finished with

A remote workspace could be started and then never stopped — the control was not on screen anywhere. A machine that had grown to full size stayed there, holding capacity nobody was using. It is back, next to the machine it acts on.

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.
1.3.18

Your uncommitted work survives a restart

The last release asked you to push before stepping away, because a workspace that restarted came back with only what you had pushed. You do not have to any more. Your changes, your untracked files and everything you installed are still there when it comes back.

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.
1.3.17

One stuck workspace no longer stops the rest

A workspace that stopped responding used to take the whole app down with it — every other workspace slowed to a crawl, and the stuck one stayed stuck until somebody noticed. Now the rest keep working, and the stuck one comes back on its own.

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.
1.3.16Desktop

Review a pull request without leaving Padar

See a branch's pull request, its checks and its review comments in the workspace you built it in. Comment on the diff line by line, reply to a thread right where the change is, and open a new PR straight from the app — no browser.

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.
1.3.15Desktop

Bring a workspace to your own localhost

Forward a running workspace to your machine on the exact port numbers its code expects, so its app, API and database answer on your own localhost. Padar checks what is already using those ports first, tells you what is holding each one, and the ports that are free come across without waiting on the ones that are not.

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.
1.3.14

What you type is what you typed

Text boxes on the desktop and on your phone have stopped completing, correcting and capitalising for you. A branch name typed on a phone arrives as the branch name you typed, quotes in a message to the agent stay straight, and no search box offers you what you were looking for last week.

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.

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