Launchpad
Menu
How it worksDeliverablesUse casesComparePricingSecurityResourcesSign inGo to Launchpad LiveTry the interactive demo

Free recorded demo · No live AI calls

News · Releases

Release notes

What changed in Launchpad, release by release — the new features, improvements, and fixes as they ship.

Published releases

v0.4.0

Release v0.4.0

This week has been occupied by small fixes and the bigger room implementation. We've sketched it out and started building the corner stones but there will be more to come

New

  • visible archived state for coworkers and teams (#2271)
  • author room S-1 tenancy + D-21 session-read posture
  • author room S-0 foundation + fail-closed scope enum sweep
  • phase 2 — deliverables, use cases, how-it-works depth pages
  • library slice B/C — tags UI + filter, canvas folder shelf, apply bookkeeping (#2262)

Improved

  • apply the room arc's S-1 tenancy and D-21 read posture
  • apply S-0 room foundation + control_owner_type room label
  • apply C-12 scope-enum fail-closed sweep

Next week will continue the room concept introduce the partner and client interface as well as a client specific login.

v0.2.1

Release v0.2.1

A small mid-week release, and an unusual one: everything in it is a correction. Three things were quietly not doing what they claimed. A session that failed could still show as finished, so you'd open something empty and have no idea anything had gone wrong. A team set up to run a workflow would let you start a session even when its workflow wasn't built yet — and then go nowhere. And session visibility wasn't scoped as tightly as it should have been. None of these were things you'd have thought to report, which is exactly why we'd rather ship the fix now than hold it to Sunday.

Improved

  • Sessions are now scoped to the person who started them, and team-level sharing settings actually bind — so what you see reflects what you were meant to see.

Fixed

  • Teams that run a set workflow now tell you up front when that workflow isn't ready, and explain what's missing — instead of letting you start a session that quietly goes nowhere.
  • A session that runs into a problem now says so. Previously it could show as finished with nothing in it; now it's clearly marked as stopped, with the option to try again.

Next week is unchanged: rooms, the client interface, and the GitHub integration. See the v0.2.0 notes for what that means.

v0.2.0

Release v0.2.0

This week's headline is being able to ask one coworker something directly. Until now every question went to a team. That's right when you want several perspectives, and overkill when you just want to ask one person one thing. "Ask" now opens a one-to-one conversation with only that coworker in the room — a normal session, same memory, same knowledge, just without the crowd. Alongside it: a tidier home page when you have a lot of coworkers, and a heads-up banner when we're mid-update so you know if something feels briefly odd.

New

  • wire Resources 'Draft with Link' panel to the live direct-ask launcher
  • maintenance banner with a DB-backed release-window toggle
  • ask a coworker directly — 1:1 session over an idempotent per-coworker direct team (#2197)
  • emailed report covers all 19 website event types

Fixed

  • satisfy the generated non-null p_message arg type
  • scope the maintenance banner to signed-in users on app home
  • bucket wip checkpoints as maintenance in the changelog

**Next week is about rooms — and the people you do the work for.** A room is a place for one client or one project. Everything saved to it stays in that context, so the work you do for one customer doesn't blur into the work you do for another. It's one more layer underneath your saved data, and it's what makes collaborating on it make sense. The other half is who gets in. Rooms come with a client interface: your own customers can log in, see their rooms, and add only what belongs there. Nothing else in your workspace is theirs to see. On integrations — **GitHub lands next week.** LinkedIn is about two weeks out; we'd rather it arrive properly than early. And one we're not promising yet: we've picked our structured-data work back up. If it goes the way we hope, there may be a surprise at the end of the week.

Show all releases (4)
v0.1.0

Launchpad v0.1.0 — our first weekly release

From now on, Launchpad ships on a weekly rhythm — every Sunday or early monday we release what we built during the week, and this page tells you exactly what changed. Here is what's new in our first numbered release.

New

  • Client delivery links — share a finished canvas as a professional, version-locked link, with delivery history.
  • Review & approval before delivery — send a canvas to a coworker for review and record a sign-off before anything reaches a client.
  • Google Drive connection — let coworkers work with the files you pick from your Drive.
  • Publish to LinkedIn from a coworker. This work has been started but is not fully published yet, It will be implemented in the weeks to come
  • Release notes — this page. You can now see what changed each week.

Improved

  • Clearer tool picker — tools are grouped by purpose and easier to scan.
  • Faster, steadier sessions — better handling of long multi-coworker runs.

Fixed

  • Sessions now stay correctly bound to their workspace.
  • Several session-transcript and canvas-editing fixes.

Next week: Emelie will continue looking into new tools, updating the website but also further strengthening the sessions and outcomes

See it for yourself

Reading the changelog is one thing — explore the demo at your own pace, or start building your own team.

Walk through your use case with usGo to Launchpad Live