Padar

Changelog

Older releases — page 6 of 10.

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

The agent stops losing its own messages

Some of what the agent had to say never reached the conversation — including the reason a command was stopped. It arrives now, on the call it belongs to.

Improved

  • DesktopAnything the conversation cannot read shows as a card you can open and look inside, rather than being dropped. Padar never discards a message it cannot display.

Fixed

  • DesktopA command the agent was not allowed to run now says it was stopped, and what stopped it. It used to look identical to a command that simply failed, so there was no way to tell a refusal from a broken command.
  • DesktopNotices from the agent reach the conversation instead of disappearing — when it declines to answer, when it cannot keep your files in step, and when it has something to pass on mid-run.
  • MobileThe same on your phone, which was losing exactly the same messages.
1.4.15Desktop

The Compute tab opens again

On 1.4.14 it failed the moment you opened it and showed an error in place of the panel, which put the whole of that release out of reach. It opens.

Fixed

  • The Compute tab opens without erroring. On 1.4.14 it failed immediately every time, so the processors bar and the reserved-memory reading that release was for could not be seen at all. Nothing else in the app was affected.
1.4.14

Your machines hold far more

An idle workspace costs a fraction of what it used to, so a machine fits many more of them. The Compute tab now shows what each one has actually set aside — processors included — and a machine that is genuinely full reads as full.

New

  • DesktopThe Compute tab has a processors bar, beside memory and disk. It shows what each workspace has set aside on its machine, and how much is left for anybody.
  • DesktopPaste a whole env file into New project. Its variables are read out of what you paste and shown as rows you can edit, so there is no need to write the file out to disk first just to hand it over.

Improved

  • EngineAn idle workspace holds about a third of the memory it did, and a small fraction of the processor. A machine that fit eleven workspaces now fits dozens, and idling one gives back most of what it was holding rather than a little of it.

Fixed

  • DesktopThe Compute tab reads what is set aside rather than what is being used. A machine could look like it had plenty of room while refusing to start anything new on it; the bars now match what you can actually do.
1.4.13Desktop

Nothing falls off the bottom

On a short window, New project ran past the bottom of the screen and took its Create project button with it. The dialog scrolls now, so all of it is reachable whatever height your window is.

Fixed

  • New project scrolls when it does not fit. On a laptop screen its lower half — Summary, Base branch and the Create project button — was cut off the bottom with no way to reach it, so the only way to add a project was to make the window taller first.
1.4.12Desktop

The size you pick, and what it is doing

A workspace starts at the size you chose instead of coming up small and making you wait twice. While it starts, the steps move — and if no machine has room, it says so rather than sitting there looking asleep.

New

  • Two larger workspaces to choose from, 20 GB and 24 GB. Every size now states what it takes off the machine, with the memory your VM actually gets shown underneath it.
  • While a workspace is starting, the list of steps moves — queued, finding a machine, then preparing it — instead of standing still. If no machine has room for it, that step fails and says so, where before it looked the same as a workspace that was simply asleep.
  • Every workspace on the Compute tab shows the disk it is using — what it has written, and how much of that comes back when you stop it — and the machine’s own disk bar now breaks down by workspace instead of showing one total.
  • Change a workspace’s size from the Compute tab: click its memory bar and pick one. Each size says what it would cost you on that machine, and you get told the workspace restarts before anything happens.

Improved

  • A workspace you have idled shows the memory it is actually holding rather than the size it was created at, so the Compute tab adds up to what the machine has really given out.
  • The Compute tab reads as a ledger. The bars carry their own figures and explain themselves when you point at them, instead of standing under paragraphs of small print, and the part of a machine your project cannot use is drawn as unavailable rather than as somebody else’s.

Fixed

  • A workspace you create starts at the size you picked, rather than at the smallest one and waiting to be grown. Start environment no longer has to rebuild the machine first, so you wait once instead of twice.
1.4.11Desktop

Take a file with you

Any file in a workspace can now be saved onto the machine in front of you. Hover a row in Files, press the download button, pick where it goes — including the build artifacts, screenshots and dumps the editor could only ever describe.

New

  • Every file row in Files has a download button. It saves the file to wherever you choose on this computer, however large it is and whatever is in it.
  • An open file has the same button in its header — which is the only way to get at one the editor cannot show you, like an image too big to preview or anything it calls a binary.
1.4.10Desktop

Files keep up

The Files tree refreshes itself while you work, so a file the agent wrote a moment ago is in the list without you having to switch tabs and back. There is a refresh button beside the search box for when you want it sooner.

New

  • A refresh button sits beside Search files and re-reads the worktree the moment you press it.

Fixed

  • Files created after you opened a workspace show up in the Files tree on their own. The list used to be frozen as it stood when you opened the tab, so anything added after that was missing until you reopened it.
1.4.9

Press what you mean

The Environment panel is three lists now — ports, processes and tasks — under one row of actions, and every row says what pressing it does. Memory, CPU and disk read as bars you can act on, and a port your own machine is holding tells you which program has it.

New

  • DesktopStart and stop one port at a time, or bring the whole stack up from the list header.
  • DesktopA port already taken on your machine names the program holding it and offers to free it, on the row. Copy the command instead if you would rather look first.
  • DesktopMemory, CPU and disk sit at the top of the panel as filled bars with the numbers in them. Disk is new.
  • DesktopResize a cloud workspace from its memory bar. It asks first: the machine is rebuilt and your checkout comes back from the remote, so anything uncommitted is lost.

Improved

  • DesktopEnvironment is Ports, Processes and Tasks, under one row of actions. Every port row carries its verb — Open, or Start — so nothing is hidden behind knowing where to click.
  • DesktopPin the processes and tasks you actually watch. Each list folds down to just those, and remembers per workspace.
  • DesktopCopy an address, open a log, or reach a teammate from the panel header — everything the panel could already do now looks like something you can press.
  • EngineYour environment rebuilds itself when you change .berth/Dockerfile. There is no Rebuild button any more, and a rebuild no longer replaces what your team froze.

Fixed

  • DesktopYour own workspaces show your face in the list, the way everybody else’s already did.
1.4.8Desktop

A second way into GitHub

Some organisations do not allow the Padar GitHub app, and signing in cannot reach them. Now you can connect GitHub with a personal access token instead.

New

  • Connect GitHub by pasting a personal access token, alongside signing in — Settings → Connections → GitHub now offers both. A token reaches organisations that have not approved the Padar app, so your repositories and pull requests appear where signing in cannot reach them. Keep both connected, or either on its own.

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