AutoGPT’s pitch has shifted a lot since it was the “give GPT-4 a goal and let it run” project everyone was talking about in 2023. The platform now leads with a different framing entirely: “Stop building workflows. Start hiring agents.” There’s a Marketplace of pre-built agents — browse by job, check real run counts and ratings, add one to your library in a click.

v0.6.70 (July 2026) is the release where that “hiring” language stops being just marketing copy.

The core addition is a formal Expert entity, with a hire/install API and roster seeds. Previously, adding a marketplace agent to your setup was presumably closer to a copy-into-library action. Now there’s dedicated infrastructure for it — an Expert as a distinct thing you hire and install, with a “roster” implying you’re meant to be managing more than one at a time. It’s a small-sounding change in a changelog, but it’s the kind of thing that makes a marketplace feel like an actual hiring pipeline instead of a template gallery.

A few smaller things landed in the same release:

  • Paste images from clipboard directly into CoPilot chat — no more saving a screenshot just to upload it
  • “Most Recently Ran” sorting in the Library — useful once you’ve actually got more than a couple of agents in there
  • Configurable transcription endpoints in CoPilot
  • Skipped webhook presets get surfaced when you swap a trigger, instead of silently leaving stale config behind

This builds on some bigger UI work from a few releases earlier (v0.6.64, mid-June): a persistent AutoPilot context panel, a global Cmd+K search, read-only viewing of graphs you don’t own, and — the one I found genuinely interesting — a “Dream Pass” that runs a background process for the Copilot bot between active sessions. I haven’t dug into what that actually does yet; it’s on my list.

Why it matters

Most agent frameworks I look at are still fundamentally “here are the building blocks, go build.” AutoGPT’s marketplace-first approach is a bet that most people don’t want to build — they want to pick an agent that already does the job and adjust it. Formalizing “hire” as an API primitive, rather than just a UI action, suggests they’re building toward letting other things (other agents, other platforms) do that hiring programmatically too. Worth watching where that goes.

Try it

git clone https://github.com/Significant-Gravitas/AutoGPT.git

Full release notes are on the GitHub releases page.