Changelog

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.

New

• DesktopSign in from Settings as well. The Claude card takes you straight to the sign-in for the workspace you have open, so you no longer have to know that it lives in the MCP panel.

Fixed

• EngineThe sign-in works. It was opening a tab that immediately failed with "command not found", because it was being run in the wrong place — inside your project's environment rather than the workspace itself.
• EngineYour connectors show up as soon as you have signed in. The agent was carrying on with the credential it started with, so a workspace you had just signed in still behaved as though you had not — and nothing said restarting the conversation was what it wanted.
• EngineWorkspaces on a machine build again. The image build could pick up two copies of Claude Code and refuse to choose between them.

New

• DesktopSign a workspace in to your Claude subscription from the MCP panel. It opens a sign-in tab, you approve in your browser, and that workspace is signed in. The sign-in stays in the workspace — Padar never receives it, and the Claude Code login on your own machine is left alone.
• EngineThe connectors on your Claude account work in a signed-in workspace. Whatever you have set up at claude.ai is there for the agent to use, alongside the MCP servers you declare in Padar.

Improved

• DesktopA connector is listed under its own name. It used to carry "claude.ai" in front of every one, which said the same thing the label beside it already did.

Fixed

• EngineTerminal tabs open again in a workspace running on a machine rather than your laptop. A new tab was coming up empty with a "command not found", which also made last release's sign-in instructions impossible to follow.
• DesktopThe MCP panel says where each server actually came from. Servers brought by a plugin, or added inside the workspace, were listed as though they came from your Claude account — so the panel sent you to claude.ai to fix something that was never there.

New

• DesktopUndo what a message changed. Every turn keeps a copy of the files it touched, so a turn that went the wrong way can be put back without unpicking it by hand. The undo shows up in the transcript, and you can redo it.
• MobileThe phone shows when a turn has been undone, so a transcript reads the same on both.
• EngineSign a workspace in to Claude yourself. Open a terminal in it, run claude and sign in with /login, and that workspace uses your own Claude subscription instead of the token in Settings. Padar never sees the sign-in, and your Claude Code login on your own machine is untouched.

Improved

• DesktopLong conversations stay fast. The chat used to get slower the more you talked to it, until a long thread arrived in fits and starts and the app felt heavy — a hundred messages in, it now streams as smoothly as it does on the first.
• DesktopThe model picker offers the models your account can actually use. It asks Claude instead of going by a built-in list, so a model you have access to no longer goes missing.
• DesktopThe context meter counts the whole conversation rather than the most recent turn, so it reads as full when it is.
• DesktopThe MCP panel says where each server came from and which Claude credential the workspace is running on, so a server you expected and cannot see gives you somewhere to go.

Fixed

• DesktopA reply no longer stops part-way through while the agent carries on working. Nothing was lost when it happened, but the rest of the answer only appeared once the turn had finished.
• DesktopEvery one of a workspace's agent conversations shows up when you open it. Sometimes only the first appeared and you had to reopen Padar to find the others.

Fixed

• A workspace that stopped opening connects again. A handful had been unreachable for everyone for days, showing as dead in the app while the workspace itself was running perfectly, and nothing you could do in the app brought one back.

New

• DesktopType / in the chat and every command the session really has is there, your project’s own skills included, and it runs. The list was ten fixed names before — half of them not real commands, and none of them yours.

Improved

• DesktopYour project’s own skills sort above everything a plugin brings, so the ones you wrote are the ones you see first. The list is shown whole and scrolls rather than stopping at the first dozen.

Fixed

• EngineA machine stays reachable however long you leave a workspace open on it. After a few hours it would go dead in the app while the machine itself was perfectly healthy, and only restarting Padar brought it back.
• EngineA workspace that has just restarted is reachable again straight away. It could come back unreachable and stay that way while the workspace itself was running perfectly, and reopening Padar fixed it only sometimes.
• DesktopClearing the conversation leaves a clean transcript. It used to read as though the agent had answered you with “(no content)”.
• DesktopThe agent stops looking busy after a command it answers instantly. Running /context or /usage used to leave it showing as working until you sent something else.

New

• DesktopDeclare an MCP server once in Settings → Connections and every workspace you open has it. Until now the tools that make you effective on your own machine were simply missing in the place the work happens.
• DesktopImport from this machine takes the servers you already use, including the ones your plugins provide, so you do not retype a single command. It copies the setup only — no key or token is ever read off your machine.
• DesktopServers that need a browser sign-in get one. You sign in once and it works on every device you use, phone included.
• DesktopA key you set is encrypted before it is stored and is delivered only to the machine running your workspace. Nothing can show it again — not Padar, and not you.
• EngineA project can ship its own servers in its .berth/actions.toml, so a repo brings its tools with it and nobody sets them up twice. Your own servers still win where they overlap.

Improved

• DesktopA control beside the composer says which servers the agent reached and which it could not, with the reason. A server that failed to start used to be missing with nothing said about it.

Fixed

• DesktopThe agent carries on the same conversation after it restarts. It was quietly beginning a new one, so it forgot what you had been working on.

Improved

• MobileA workspace opens as its task — the Linear brief on top, with Agent thread, Changes, Terminal, Files, Ports and Environment as named rows under it.
• MobileThe phone matches the desktop’s type and colour throughout.

Fixed

• DesktopThe chat follows the agent while it works. On a long run it stopped wherever you last were, so output piled up out of sight and the app looked frozen while it was working.
• DesktopA link an agent writes opens in your browser. Clicking one used to replace Padar with the page, with no way back except quitting.
• MobileTapping a link in the agent’s replies opens your browser. Before, nothing happened at all.

New

• Copy link, at the bottom of a workspace under In this workspace. Send the link to anyone on your team and it opens that workspace on their Mac, whichever machine it lives on. Somebody outside the team is told the workspace is not theirs to open rather than being shown anything.