# SageOx + Slack via OpenClaw (https://sageox.ai/docs/cookbooks/slack-openclaw)

# SageOx + Slack via OpenClaw

Your team makes decisions in Slack every day. Architecture calls in `#engineering`, deployment approvals in `#ops`, debugging breakthroughs in DMs. Within a week, those threads are buried. Within a month, they're gone.

This cookbook uses **OpenClaw** to bridge Slack and SageOx — automatically capturing meaningful conversations as searchable Team Context.

## What you need

- SageOx CLI installed and a connected repo (`ox init`)
- An [OpenClaw](https://openclaw.dev) account
- Slack workspace admin access (for the bot install)

## How it works

```mermaid
graph LR
    A[Slack thread] -->|OpenClaw bot| B[Recording created]
    B -->|SageOx pipeline| C[Transcript + summary]
    C --> D[Team Context]
    D --> E[AI coworker sessions]
```

OpenClaw watches Slack channels you configure. When a conversation matches your criteria — length, keywords, emoji reactions — it creates a SageOx recording from the thread content. SageOx processes it through the same pipeline as any recording: transcription, summarization, and indexing into Team Context.

## Setup

### 1. Install the OpenClaw Slack bot

Follow the [OpenClaw Slack integration guide](https://openclaw.dev/docs/slack) to add the bot to your workspace. Grant it access to the channels you want monitored.

### 2. Connect OpenClaw to SageOx

<Terminal>
  <TerminalComment>Link your OpenClaw account to SageOx</TerminalComment>
  <TerminalCommand>ox integrations connect openclaw</TerminalCommand>
</Terminal>

This establishes the bridge so OpenClaw can create recordings in your SageOx team.

### 3. Configure capture rules

Define which Slack conversations get captured. OpenClaw supports rules based on:

| Trigger | Example |
|---------|---------|
| **Channel** | All threads in `#architecture-decisions` |
| **Emoji reaction** | Any thread with a `:bookmark:` reaction |
| **Thread length** | Threads with 5+ messages |
| **Keyword** | Threads mentioning "decided", "agreed", "going with" |

Start narrow. A single channel or emoji trigger is better than capturing everything and drowning in noise.

### 4. Verify it works

Post a test thread in a monitored channel, trigger your capture rule, and confirm the recording appears:

<Terminal>
  <TerminalCommand>ox recordings list --limit 5</TerminalCommand>
</Terminal>

## Recipes

### The `:bookmark:` workflow

The lowest-friction approach: tell your team to react with `:bookmark:` on any Slack thread worth preserving. OpenClaw captures bookmarked threads automatically.

This works because it's opt-in and zero-effort — no workflow changes, no new tools. Someone already bookmarks important threads. Now those bookmarks become permanent team knowledge.

### The decisions channel

Create a `#decisions` channel (or `#architecture`, `#tech-decisions`, whatever fits). Configure OpenClaw to capture every thread in this channel.

The social contract: if you make a decision, post it to `#decisions`. One sentence is enough — "Going with Postgres JSONB for metadata, schema is too unstable for columns." The full context lives in the thread.

Within a month, your AI coworkers can answer "why did we choose X?" by citing the actual discussion.

### Capture debugging sessions

Long debugging threads in `#incidents` or `#bugs` are gold — they contain the symptoms, the investigation, the false leads, and the fix. Configure OpenClaw to capture threads over 10 messages in your incident channels.

Next time a similar bug surfaces, your AI coworker has the debugging playbook from last time.

## What gets captured

SageOx processes Slack threads the same way it processes any recording:

| Artifact | Source |
|----------|--------|
| **Transcript** | Thread messages, preserving author and timestamp |
| **Summary** | Key decisions, action items, and conclusions |
| **Annotations** | Links to code, PRs, and concepts mentioned in the thread |

The thread becomes a first-class knowledge artifact — searchable, referenceable, and available to every AI coworker session.

## What's next

- [SageOx + Claude Code](/docs/developers/claude-code) — how your AI coworker uses captured context
- [SageOx + Loom](/docs/cookbooks/loom) — capture video walkthroughs alongside Slack threads
- [SageOx for solo players](/docs/cookbooks/solo) — start building context before your team adopts