Skip to main content

Quorum

The decision memory for your Slack workspace.

Open source (MIT) · TypeScript · 19 unit + 2 integration tests, all green · Slack Agent Builder Challenge 2026.

The problem

Teams make real decisions in Slack threads, then lose them. Existing tools summarize conversations, but none capture durable decision provenance: what was decided, why, who owns it, and what it supersedes, in a form you can retrieve weeks later. So the same questions get re-litigated and nobody can point to the thread where it was settled.

A person marks a thread with the Capture decision shortcut; Quorum drafts a structured Decision Record and waits for a human to Approve, Edit, or Discard it. Capture is human-triggered by default, and proactive auto-detection is opt-in and off by default, so nothing is filed without a person in the loop. Approved records go to a canonical Decision Log (a Slack Canvas plus a #decision-log channel), and asking "what did we decide about X?" returns sourced, permalink-cited replies drawn from fresh, permission-scoped context.

Quickstart

Node and pnpm. The whole agent runs offline with deterministic canned data and no API keys, so you can exercise the full flow without a Slack workspace.

Clone and install:

git clone https://github.com/OrionArchitekton/quorum-slack-agent
cd quorum-slack-agent
pnpm install

Command surface

  • 📌 Capture decision: Human-triggered message shortcut on any thread: drafts a structured Decision Record for a person to Approve, Edit, or Discard. Proactive auto-detection is opt-in via QUORUM_NUDGE_CHANNELS and off by default.
  • @Quorum / /decisions: Ask "what did we decide about X?" and get sourced, permalink-cited replies, drawn from the Real-Time Search API first and the hosted Slack MCP server second.
  • QUORUM_FAKE_LLM=1 pnpm dev: Runs the whole agent offline with deterministic canned data and no API keys, so the capture, approval, and Q&A flow reproduces on your machine.
  • pnpm test: 19 unit tests across the Decision Record schema, the capture and approval flow, the Decision Log writer, and the retrieval and citation path.
  • pnpm test:int: 2 integration tests: the durable approval workflow genuinely suspends on the human-approval hook and resumes, verified against the runtime event log.

Why it is different

  • Provenance, not another summary: Other Slack tools summarize a conversation. Quorum captures durable provenance: what was decided, why, who owns it, and what it supersedes, as a structured record you can retrieve and cite long after the thread scrolls away.
  • A human is always in the loop: Capture is human-triggered by default and every record waits for a person to Approve, Edit, or Discard before it is filed. Proactive auto-detection is opt-in and off by default, so the agent never files a decision on its own.
  • Durable approval at zero compute: The approval step runs on a durable Vercel Workflow that suspends up to seven days at zero compute and survives restarts, so a decision can wait for the right reviewer without holding a process open or timing out.
  • Built on the Slack agent stack: Three required Slack technologies, each load-bearing: the Slack AI agent runtime, the hosted Slack MCP server, and the Real-Time Search API. Answers are permalink-cited and scoped to each user's own permissions.

Links