Today we’re shipping Quackstack 3.0, the biggest release since we let the duck talk back. The headline feature: multi-duck collaboration. You can now invite teammates — and their ducks — into a shared quack thread, and watch the ducks negotiate with each other in real time.

What’s new

  • Shared quack threads. Pair-debug across timezones with a live, append-only log every duck can read.
  • Duck personalities. Pick from Skeptic, Architect, Junior, or Linter. Each asks a different first question.
  • Quorum mode. Require three ducks to agree before the thread closes. Excellent for incident reviews.
  • Replay. Scrub backwards through any thread to see exactly when the wrong assumption entered the conversation.

Why multi-duck

One duck is a mirror. Two ducks are a code review. Three ducks are a design doc that wrote itself. We kept hearing the same story from customers: the most useful quack session of the week was the one that accidentally pulled in a second engineer. So we built that on purpose.

Skeptic-duck: “What happens at midnight UTC?”
Architect-duck: “It doesn’t, because we shift to the user’s timezone in the worker.”
Skeptic-duck: “Does the worker know the user’s timezone?”
(Long pause.)

Migration notes

Quackstack 2.x clients keep working. To opt into shared threads, upgrade the CLI:

$ npm i -g @quackstack/cli@3
$ quack login
$ quack thread create --share team

What’s next

We’re working on async webhooks so your CI can quack at you before the build even finishes, and a long-requested VS Code panel. Both land before the end of the quarter.