Plexus blog

Bitbucket is moving SSH to ssh.bitbucket.org

2026-10-22T00:00:00Z

Bitbucket Cloud is moving git over SSH from bitbucket.org to a new hostname, ssh.bitbucket.org. If you clone, fetch or push Bitbucket repositories over SSH, every one of those remotes needs the new address. This post covers what is changing, who it affects, and what Plexus 1.3.1 does about it.

What Bitbucket is changing, and when

Atlassian's announcement splits Bitbucket's traffic in two. bitbucket.org will serve only HTTPS: the website, the API and git over HTTPS. Git over SSH moves to ssh.bitbucket.org.

The original deadline was 12 November 2026. Atlassian updated the announcement on 21 October 2026 with a grace period. From 12 November, SSH on bitbucket.org is blocked during scheduled "brownout" windows that start at 15 minutes and grow to three hours. On 10 December 2026, it is switched off for good. During a brownout, and for good after 10 December, a fetch, pull or push to git@bitbucket.org: fails.

Atlassian asks SSH users to do four things:

change each SSH remote to git@ssh.bitbucket.org:<workspace>/<repo>.git;
trust the new host in ~/.ssh/known_hosts;
update CI/CD pipelines, deployment scripts and any other automation that uses SSH;
allow ssh.bitbucket.org on port 22 through firewalls that restrict outbound SSH.

Who is affected

Only SSH remotes. A remote that starts with https://bitbucket.org/ keeps working as it does today. That includes every repository you cloned from Plexus's repository search, because those clones use HTTPS with your Bitbucket connection.

What Plexus 1.3.1 does

It recognises the new host. Plexus decides which remotes are Bitbucket by their address, so on 1.3.0 a remote on ssh.bitbucket.org would have lost its pull requests, CI status and Open on Bitbucket. It would also have stopped matching the same project on your other machines for cross-device sync. In 1.3.1 those all keep working, whether a project has switched or not.

It tells you which projects need the change. If any project still has an SSH remote on bitbucket.org, a notice says so, with Review and Not now. Review lists every remote that would change, with its current and new address. It also offers to add Bitbucket's published host keys for ssh.bitbucket.org to your known_hosts. That matters more inside Plexus than in a terminal. The first time ssh meets a new host it asks whether you trust it. Plexus's background fetches and the commands an agent runs in a session have no way to answer that question, so they would simply fail.

It changes nothing until you click Update. Your remotes are in your repository's own configuration, and known_hosts decides which servers every ssh client on your machine trusts. Neither is ours to change without asking, so Plexus asks.

The host keys Plexus adds are built into the app. Atlassian says the new hostname uses the same host keys as bitbucket.org. On 22 October 2026 we checked that ourselves: ssh.bitbucket.org already answers, and it serves the same keys as bitbucket.org, matching Atlassian's published list. Plexus never asks the network for the keys at the moment you click. Recording whatever key answers would trust anyone who could intercept that connection.

Plexus never edits ~/.ssh/config. If your setup routes Bitbucket through a Host alias, a Host bitbucket.org block or a git insteadOf rule, the dialog shows you the exact line to change.

Doing it yourself

If you'd rather switch by hand, it is one command per remote, run in each repository:

git remote set-url origin git@ssh.bitbucket.org:<workspace>/<repo>.git

Then trust the new host, either by connecting once and checking the fingerprint ssh shows, or by adding the published keys to known_hosts. The docs have the three key lines, their fingerprints and how to switch back.

Plexus only looks after the repositories on your machine. Your CI, deploy scripts and firewall rules are still on Atlassian's list above.

If something about the move doesn't work the way this post says, tell us through Feedback in the app.

Plexus 1.0

2026-10-12T00:00:00Z

Plexus 1.0 is out. It is the first version with an optional account, the first with organizations for the people you work with, and the first with something you can pay for. Adding a paid plan means we also have to say what will never be behind one. That matters as much as the new features, so this post covers both.

What Plexus is

If you are new here: Plexus is a desktop app for running several Claude Code sessions at once without losing track of them. It runs on macOS, Windows and Linux.

You add a repository as a project and group projects into workspaces. Each session gets its own git worktree, which is a separate checkout on its own branch, and runs the real claude CLI in a real terminal inside it. Plexus does not call the model API. It drives the Claude Code you already have, on the subscription you already pay for. From one window you can:

See what every agent is doing. Each session shows whether it is working, needs you, is delegating to subagents, or is idle, and whether its branch has a pull request yet. See Status & notifications.
Review before anything is pushed. Look at the diff like a pull request, leave comments, and have the agent work through them. See Review & diffs.
Edit and commit without leaving the app. Plexus has a file explorer and editor scoped to the worktree, a full git client, and pull requests and CI status from GitHub and Bitbucket.
Automate the lifecycle. Run your own scripts when a worktree is created, started or removed, and set them globally, per workspace or per project. See Lifecycle hooks.

All of that was in Plexus before 1.0. None of it changes now, and none of it needs an account.

What is new in 1.0

An account, if you want one

Settings → My account signs you in through your browser. The sign-in is stored in your operating system's keychain, not in a file and not in the app's database. The same page lists every machine you are signed in on, and you can sign any of them out. See Your Plexus account.

Organizations and roles

You can create an organization, invite people by email and give them roles, all without leaving the app. Every organization starts with five roles: Owner, Admin, Maintainer, Member and Restricted. You can copy any of them and tick or untick what the copy may do. When someone holds two roles, a permission one role takes away stays taken away. That is what makes Restricted dependable for contractors. Roles cost nothing and never will. See Roles and permissions.

Two plans

There are two plans: an individual plan, and an organization plan paid per seat. Both are monthly and both are in euro. The price and the VAT for your country are shown at checkout before you pay. Your card and bank details go to our invoicing provider and never to us. If a payment fails, nothing is switched off while it gets sorted out. See Pricing and Plans, seats and billing.

Seven things a plan unlocks

Cross-device sync****. Your settings, workspaces and projects stay the same on every machine you sign in on. Before anything is sent the first time, Plexus shows you the full list of what would leave the machine, with a switch beside every workspace and project to keep it out.
A prompt library that travels with you. Prompts have typed fields, and you can start a session from one.
Shared workspaces****. An organization sets up a workspace and its repositories once, and everyone with a seat gets it.
Managed settings****. An organization can recommend or enforce settings on its members' machines, and can do a dry run that changes nothing.
Organization prompts****. Templates are published as numbered revisions and can be rolled back in one step. An organization prompt can never run a command or attach a file on your machine.
Your issue tracker inside Plexus****. You can read, edit and create a project's GitHub issues, work its GitHub Projects boards, and start a session from an issue with one click. These calls go from your machine to GitHub on your own account. We are not told they happened.
Stacked pull requests****. Start a session on top of another session. Plexus restacks each branch while the agents work, retargets each pull request when the one below it merges, and lands the stack in order.

The free part stays free

Adding a paid plan to a free tool raises an obvious question: what else will end up behind it? Here is our answer, with what we did to back it up.

Nothing that already worked moved behind a plan, and nothing ever will. These all work the same whether you are signed out, signed in, paying or not: sessions, worktrees, the agent terminal, review, the explorer, the git client, pull requests, hooks, the dashboard and every setting. There is no cap on sessions, projects or worktrees, and there will not be one. Every one of the seven features above is new. None of them existed without a plan in any earlier version. This is not only a promise: automated checks in our build hold us to it.

If a plan ends, you stop sending and receiving changes, and nothing else changes. Your settings, workspaces, projects and prompt templates stay on your machine, because the copy on your disk is the real one. A shared workspace stays in your sidebar with its sessions and worktrees untouched. Deleting what we hold, leaving a shared workspace and withdrawing what an organization published all keep working after a plan has lapsed. Cancelling cannot trap anything you made.

If something ever becomes conditional on a plan, we will say so in the release notes and as an announced change to the Terms. You will not find out by running into it.

What leaves your machine

Plexus is still local-first. Your code, your keys, your sessions, your worktrees and your transcripts are never sent anywhere by an account, a plan or sync. Sync sends nothing until you have seen the full list of what it would send. Fifteen settings that describe a particular machine, such as the path to claude or your shell, can never leave it. The device list stores no IP address. Signing in or buying a plan does not change the anonymous usage report or Feedback: neither carries your account, and neither has a place to put a plan. The details are in the Privacy Policy.

Smaller changes in 1.0

A calmer Settings. Each page is a short list. Select a row and a side panel explains the setting and shows where its value comes from. The sidebar is down to eight pages.
The project Git tab puts the graph first. The commit graph takes the full width. References, commit details and diffs open as layers on top of it, and your sessions' states show on the branches they are working on.
Every dropdown can be searched, including the branch fields in New Session.
Prompt fields are chips you can type, click or drag into place.
Pasting a screenshot works on Windows again.
A security fix to the git provider sign-in. The callback address is now validated strictly, and the sign-in is always bound to the copy of Plexus that started it.

The changelog has the full list, and it is the same text the app shows in its What's new window.

Getting 1.0

If you already have Plexus, the app offers the update itself. If not, the download page suggests the right build for your system, and Installation covers the rest. Plexus is free to download and its core is free to use. It is not open source.

What comes next

Some boxes in the role editor are greyed out and marked as planned. They stand for features we are still building, and each one becomes active in the release that ships its feature. On the team side, hooks an organization can share with its members are planned but not built yet.

If something in 1.0 is wrong, unclear or broken, tell us through Feedback in the app. We would rather fix it than leave it.

A new home for Plexus

2026-10-04T00:00:00Z

runplexus.com has been rebuilt. Until now it was mostly a landing page with the docs attached. The new site is meant to be somewhere you come back to: to look something up, to see what changed, and to decide whether Plexus fits the way you work.

What is new

The docs, redesigned. Every page is still there, grouped the way you use the app: projects, sessions, automation, integrations and reference. Each page still describes what the app does today, not what is planned.
Feature pages. One page each for sessions and status, review, worktrees and hooks, git and issues and teams. The pictures are the app itself, recreated in the page, not mock-ups.
Comparisons. How Plexus compares with Claude Code on its own, Conductor, Cursor and other IDE agents and Claude Squad and Nimbalyst. Every claim about another tool links to that tool's own documentation and carries the date we checked it. Where they do something better, the page says so.
Pricing. The pricing page shows what stays free and what a plan adds. Plans and prices are read from our billing system when the site is built, never typed in by hand. The checkout shows the final price with your VAT before you pay.
Download. A download page that suggests the build for your system and lists every installer, with the requirements next to it.
The changelog. Every release, on one page. It is the same text the app shows in its What's new window.
This blog, for anything longer than a changelog entry: how a feature works, why we built it a certain way, and what we are working on.

What has not changed

Plexus is still a desktop app that runs the Claude Code CLI you already have, one session per git worktree, on your own machine. The core of the app is free, and it still works without an account.

If something on the new site is wrong, unclear or broken, tell us through Feedback in the app. We would rather fix it than leave it.