Padar

Changelog

Older releases — page 2 of 10.

1.4.55

Find any workspace from ⌘K

Type a workspace’s name into ⌘K to jump to it from any project, or to bring an archived one back.

New

  • Desktop⌘K finds every workspace by name, project or branch, across all your projects. Pick one to open it.
  • DesktopArchived workspaces show up in ⌘K too. Pick one to restore it and open it, with no scrolling through the Archived list.

Improved

  • EngineA workspace on a frozen environment only takes up disk for what it changes, so one with a large database no longer runs out of space within hours.
  • EngineOnly the person who added a machine, or a team admin, can add it again. Two laptops with the same name no longer take each other’s place.

Fixed

  • EngineA frozen environment starts from its frozen image again instead of rebuilding from scratch. Workspaces that were affected repair themselves the next time they start.
  • EngineAdding the padar label to a Linear ticket recognises you and the assignee, even when Linear and Padar know you by different email addresses.
1.4.54Desktop

Terminal tabs are signed in

Claude in a terminal tab could ask you to log in. It now uses the same Claude account your chats do.

Fixed

  • A terminal tab opens Claude already signed in, on the same account your chats in that workspace use, and stays signed in for as long as you keep it open.
1.4.53Desktop

Claude in a terminal, beside your chats

The + above your conversations now opens a chat or a terminal. A terminal runs Claude Code itself, as a tab next to your chats, and tells you when it is done.

New

  • Pick Terminal from the + above your conversations to open Claude Code in a terminal tab beside your chats. It has the MCP servers you set up in Padar, picks up where it left off when you come back, and closing the tab ends it.
  • A terminal tab notifies you like a chat does: when Claude finishes, or when it stops to ask you something.

Improved

  • The Default model is Opus 5.5.
1.4.52Desktop

The archived list scrolls

With enough archived workspaces, the list ran off the top of the screen instead of scrolling. It scrolls now.

Fixed

  • The Archived list scrolls once it has more workspaces than fit on your screen. It used to keep growing upward instead, so with enough of them the ones furthest up ran off the top with no way to reach them.
1.4.51Desktop

Your bot's work, kept apart

Workspaces your team's bot creates now sit under the bot in the sidebar, and you can see where each of its messages got to.

New

  • The bot has its own place in a project's sidebar. The workspaces it creates open from there, and leave your own lists.
  • Each message the bot sends shows whether it is queued, delivered, answered or not delivered, and the reason when it failed. It updates as it happens.

Improved

  • In a workspace the bot created, the message box gives way to a line saying the bot writes there, with a link to its settings. A chat the bot opens in your own workspace leaves it yours.
1.4.50Desktop

Give your team a bot

Other tools can now message your team's agents and read their answers, through a bot you set up in Settings.

New

  • Settings → Bot: an owner or admin names the team's bot, picks whose Claude login it runs on, chooses which projects it can reach, and issues API keys. A key is shown once to copy, and can be revoked at any time.
  • Each key shows when it was last used, and the page warns you when the bot's Claude login has lapsed or its sponsor has left the team.
  • A project's settings have a Bot tab that says whether the team's bot works there. An admin can add it to the project, or set a bot up from there if the team has none.

Improved

  • Messages the bot sends appear in the chat under the bot's own name, so you can tell them from something a teammate typed.
1.4.49Desktop

A clearer start for remote workspaces

While a remote workspace starts, you see how far along it is, how long each step took, and what it is doing now.

Improved

  • Starting a remote workspace shows one card: a ring for how far along it is, the time so far, then Machine, Connect, Code, Services and Agent, each with how long it took. The step in progress says what it is doing, and if one fails it says which.
  • Once your code is checked out the workspace opens, and the rest of the start finishes where the chat will be. The chat appears as soon as the agent is ready.
1.4.48Desktop

A new layout for the desktop app

Your projects live in a dock, each project has its own rail, and a workspace keeps the chat, what you are reading and one side panel in a single window. Colours, type and controls are quieter everywhere, and there are nine colour themes to choose from.

New

  • Your projects sit in a dock down the left edge. Pin the ones you use, drag them into any order, jump between them with ⌘1–9 (hold ⌘ to see the numbers), and see at a glance which one needs you. Theme, inbox, settings and your account sit at its foot.
  • Each project has its own rail: search, the Board, Mentions, Resources and the project’s settings, then your workspaces grouped into Needs you, Running and Idle, each saying why in words.
  • Mentions is a page of its own in every project, grouped by day, with Unread and All and a filter for each kind. The bell in the dock opens a quick inbox that links to it.
  • Owners and admins can change a teammate’s role, remove someone from the team, and resend or withdraw an invite, all from Settings → Members.
  • Mute, Archive and Delete sit in a workspace’s top bar. Archiving keeps the code and the chats, and archived workspaces wait on a shelf at the foot of the rail, one click from Restore.
  • Choose a colour theme from the palette button in the dock: Graphite, Midnight, Mocha, Paper, Sand, Sage, Ink, Chalk or Ember. ⌘\ still flips between light and dark.

Improved

  • Home opens on a welcome that says what is waiting for you, or the next step while a project is still being set up.
  • The queue is now the Board: one row per ticket, coloured by its state, with who it is assigned to, who picked it up, its workspace and its age, and one menu each to filter by assignee and by project.
  • In a workspace, conversations sit in a strip above the chat. Switch between Chat, Split and File to read a file or a diff beside the conversation. Task, files, changes, review, terminal and environment open one at a time from an icon rail on the right, and Esc closes them.
  • The status bar shows the ticket, branch and pull request, and whether a script is still running in a terminal. The model pill names the Claude model a conversation is using.
  • A project’s settings — General, Members and Integrations — open inside the project, beside its rail. Resources lists its workspaces by state, by machine or by owner, with a search, and keeps archived workspaces and stores one click away. Each store says who froze it and which machine holds it, and counts towards the project’s own disk.
  • The Environment panel draws each process as one line whose colour says what it is doing. Picking a store is one list, and Freeze asks for a name. A process log can be searched as well as filtered.
  • Dialogs are centred and say what an action keeps and what it removes. New workspace no longer jumps as you move between Branch, Issue and Pull request.
  • The app uses your system’s font, and buttons, fields and colours are calmer throughout. On a Mac, the window buttons have a clear strip of their own above the sidebar.
1.4.47

Stores: name, keep and switch a workspace’s data

Freeze a workspace’s databases into a named store, keep as many as you like, and restart any workspace on one of them — or on a clean slate — without changing what anyone else starts from.

New

  • DesktopFreeze asks for a name and saves the workspace’s images and databases as a new store. The workspace restarts on it; new workspaces keep starting from the project’s default until you choose otherwise.
  • DesktopSwitch restarts a workspace on any of the project’s stores, or on Clean. It warns you before throwing away database changes since the last restart, and offers to freeze first. Your code is never touched.
  • DesktopThe Compute tab lists every store with its size and what’s inside it. Rename one, make it the default for new workspaces, or delete one nobody uses to get the disk back.

Improved

  • DesktopThe Environment panel is one view: a tile for everything your workspace runs, coloured by what it is doing. Press a tile to open its port. A process still building says so instead of looking broken, and a stop that hangs offers Force stop.
  • DesktopA process’s log opens as a document with a filter, Follow and Clear, and its own Start and Stop.
  • DesktopWhen .berth/actions.toml has a mistake, the panel tells you what it is and on which line, including anything it no longer reads, such as [[actions]].
  • DesktopArchive lives in the Compute tab, and archived workspaces no longer fill the workspace list.
  • DesktopPadar no longer starts the extra services in .berth/compose.yaml. Start your project’s databases from .berth/actions.toml, so a frozen store keeps their data.
  • MobileThe phone’s Environment screen matches the desktop: the same tiles and logs, and Freeze and Switch from the Store sheet.
1.4.46Desktop

Fork a chat

Branch any agent conversation into a new one that already knows everything said so far — hand a thread to a teammate, or take it somewhere new, without disturbing the original.

New

  • Hover an agent reply and choose Fork to start a new conversation in the same workspace that carries everything up to that point. The new chat remembers the discussion so far, so the agent picks up where it left off instead of starting cold.

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