MeshMeshBeta
Releases

October 22, 2026 - Agents and workbenches now scale themselves

Agents and workbenches get more CPU and memory when a job needs it, recover on their own if they stop, and respond faster. Plus rebuilt GitHub connections that act as you, and a Salesforce reconnect fix.

October 22, 2026

Desktop 0.21.20

Big jobs need more room. Agents and workbenches now get more power when their work needs it, without restarting, and they recover on their own if something stops them.

Watch the video

What's New

Agents and workbenches scale with their load

When an agent or workbench is working hard, MeshMesh gives it more power while it runs. There's nothing to set up, and the work keeps going.

  • Up to 3× the CPU: a sandbox that stays busy for five minutes steps up from 1 to 2 to 3 vCPU
  • Up to 4× the memory: a sandbox close to its memory limit steps up from 4 to 8 to 16 GiB
  • No restart, so the agent carries on where it was

Automatic agent and workbench recovery

If an agent's sandbox stops responding, MeshMesh restarts it and sends your message again, so you don't have to start over.

  • It only steps in when the sandbox has really stopped, never while an agent is busy thinking or running a long command
  • If you stopped the agent yourself, it stays stopped
  • A runaway command that uses too much memory is stopped on its own, instead of taking the whole agent down with it

Faster when it counts

The slowest 5% of requests now take 0.46 seconds instead of 2.06 seconds, even with 16% more traffic (weekday production, October 12–14 vs October 19–21).

What's Improved

GitHub connections, rebuilt

Connecting GitHub is quicker, and a connection now shows exactly what it can reach.

Using the GitHub App connection? Update the desktop app, then reconnect GitHub once. Until you do, agents run without GitHub and show Reconnect needed. GitHub personal access token connections aren't affected.

  • Acts as you: a GitHub connection now uses your own GitHub access, so agents can work with every repository you can, including read-only ones. If your access changes in GitHub, MeshMesh follows straight away, with no reconnect
  • Fewer steps to connect: no more organization chooser, and no more "You don't have write access" refusal for read-only users
  • See what's connected: the connection shows who it acts as (@login), each account and organization it reaches, and how many repositories. Search an organization's repositories and filter by Read & write or Read only
  • Add an account or org straight from the connection
  • Clear status when something's in the way: Connected, Waiting for approval, Blocked by IP allowlist, Not verified, or Not finished connecting, each with a one-line next step and Check again. Connections that aren't ready can't be added to an agent, and clicking one opens it so you can fix it
  • Simpler sign-in: the GitHub sign-in window closes on its own when you're done, paste any github.com link and MeshMesh uses github.com, and you get clear messages when a GitHub Enterprise Server address isn't set up or a sign-in link has expired

What's Fixed

  • Reconnecting Salesforce switched to Custom domain and tried to sign in through your org's own domain. Reconnect now remembers how you signed in, and uses Production or Sandbox sign-in for standard orgs
  • Messages could be lost when an agent's sandbox stopped mid-conversation. They're now sent again once it's back

Security & reliability

  • Agents can only use GitHub connections that are fully set up, and only with your own GitHub access
  • Removing a GitHub connection revokes its access at GitHub
  • Dependency security patches and MCP security updates