Padar

Changelog

1.4.65

Your keys, in your workspaces

Keep your SSH keys and your own .env values in Padar, and they open in the cloud workspaces you start, nowhere else. Every new version now asks to be installed, so you are never far behind.

New

  • DesktopAdd your SSH keys in Settings › Connections. They work for ssh and git in the cloud workspaces you start, from your terminals and your agent, and are never written to the workspace’s disk.
  • DesktopKeep your own .env values beside a project’s env files, in the project’s settings. Each one says what it overrides, and your workspaces get them on top of the project’s, key by key.
  • DesktopWhen a new version is ready, Padar asks you to update. It takes a few seconds and reopens where you left off; Later asks again in an hour.

Improved

  • DesktopVariables shows which keys are yours. Mark a key as yours, or upload a single key to the project, and Share leaves your own values out.
  • MobileVariables shows your own values as yours and never shares a file that holds them. The empty Vault tab is gone.
1.4.64

Live, the moment it happens

Whether an agent is working, whether a machine is on and who is looking at a chat now update the instant they change, on your laptop and your phone, and a notification takes you straight to the chat it came from.

New

  • DesktopA chat whose machine went away mid-answer shows as Lost, instead of looking busy forever.

Improved

  • DesktopA chat starting, finishing or needing you shows in the sidebar the moment it happens, for your workspaces and your teammates’.
  • DesktopA teammate’s computer shows as on or off the moment it changes. Settings › Machines says Online or Offline.
  • MobileThe phone shows which agents are working and which computers are on, live, while the app is open.
  • MobileYou only miss a notification for the exact chat you have open, on any device. Your laptop and phone no longer silence each other, and a tag always reaches you.
  • MobileTapping a notification opens the chat it came from.
  • MobileUpdate the app on your phone too: older versions stop showing whether an agent is working.
1.4.63Desktop

Chats that keep their place

Your agent chats now hold on through restarts and updates: a message you send just before one still gets answered, your "allow for this conversation" choices stick, and nothing the agent wrote goes missing.

Improved

  • Messages you send while the agent is working wait their turn and run one after another, in the order you sent them.
  • "Allow for this conversation" is remembered for the whole chat, even after the agent restarts.

Fixed

  • A message sent just before your workspace restarted or updated now runs when it comes back, instead of disappearing.
  • A permission question that was waiting when the workspace restarted now shows as cancelled, instead of vanishing.
  • If the agent stopped unexpectedly, the messages it had already written show up in the chat when you resume it.
1.4.62Desktop

The rest of the tidy-up

Nothing changes on your screen. This finishes the reorganisation of the desktop app that 1.4.61 started, so what comes next is quicker to build.

Improved

  • The desktop app works exactly as before. This update only rearranges its insides.
1.4.61Desktop

Tidying under the hood

This release changes nothing you will see. We reorganised how the desktop app is built, so the changes coming next can land faster and break less.

Improved

  • The desktop app works exactly as before. This update only rearranges its insides.
1.4.60Desktop

A workspace keeps its keys to itself

Each workspace now has an identity of its own, and it is no longer handed to the programs you and the agent run inside it.

Improved

  • Each workspace gets a fresh key every time it starts, and an archived workspace’s key stops working straight away.
  • Workspaces reach your connected accounts on their own, instead of through the computer they run on.
  • A cloud workspace’s connection to the machine it runs on is encrypted, and it talks only to that machine.
  • Cloud workspaces restart once as this update rolls out. Your files, branches and conversations are kept; open terminals start fresh.

Fixed

  • The key a workspace uses to reach your Claude, GitHub and other connected accounts no longer shows up in its terminals’ environment, in what the agent runs, or in the list of running programs.
  • If a workspace on your computer cannot reach Claude, MCP servers or your environment files, or your team’s machines do not show up, update Padar: older versions can no longer reach them.
1.4.59Desktop

Tell the agent what you want before it starts

A new workspace can open with your own instructions to the agent, whether it starts from a ticket, a branch or a pull request.

New

  • New workspace has an Instructions box. Starting from a ticket, add what the ticket leaves out, like “do it the way branch X did”, or replace the ticket’s brief with your own. The ticket is still linked and still moves to In Progress.
  • A workspace started from a branch or a pull request with instructions gets to work on them as soon as it opens, the same way a ticket’s workspace does.

Fixed

  • An agent’s first message is labelled “Opening brief” when it did not come from a Linear ticket, instead of calling it a Linear issue.
1.4.58Desktop

Only Padar can talk to Padar on your computer

Websites you visit can no longer reach the part of Padar that runs on your computer, and a handful of small things now behave the way you would expect.

Improved

  • The window stays responsive while Padar starts up after a crash, and quitting no longer waits for a connection that is still being set up.

Fixed

  • A web page open in your browser can no longer read your workspaces, or anything else, from Padar on your computer. Only the app itself is answered.
  • A workspace waiting on your answer says so in the sidebar, even when an earlier turn in it failed.
  • If you have not connected Linear, a workspace’s ticket tab says so, instead of saying the ticket could not be loaded.
  • The ticket you pick while setting up your first workspace moves to In Progress, as it does when you start a workspace any other way.
  • A pull request’s checks are its own, even when another repository has a pull request with the same number.
1.4.57

Your conversations name themselves

Each conversation takes the short name its agent gives it, so a workspace full of them is readable at a glance — and you can rename any one when the agent’s choice is wrong.

New

  • DesktopEach conversation shows the short title its agent chose — “Login button bug” rather than “Agent 2” — so you can tell them apart without opening each one. The name appears a few seconds into the first message.
  • DesktopRename a conversation by double-clicking its tab, or pressing F2 on the one you are in. Save it empty to clear your name and bring the agent’s back.
  • MobileConversations carry the same agent-given names on your phone, in the title bar and the conversation switcher. Long-press one, or use the conversation menu, to rename it.
1.4.56Desktop

Read the agent your way

Choose how Padar and its agent chat are set: four font pairs, from the Theme panel or ⌘K.

The Font section of the Theme panel: System with System mono, Lexend with Libron, Inter with Literata, and Atkinson Hyperlegible with Atkinson Hyperlegible Mono, each name set in its own face.

New

  • Choose a font pair in the Theme panel or from ⌘K: Lexend with Libron, Inter with Literata, or Atkinson Hyperlegible with its own mono, beside the default. The first face sets the app and the second sets the agent chat, and code stays monospace whichever you pick.

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