Slack-AI

Get AI summaries of your team's Slack discussions right in your terminal.

Perfect for developers using Claude Code, Cursor, and Copilot who need context without leaving their IDE.

Quick Start

# Install
npm install -g @slack-ai/cli

# Login to Slack
slack-ai login

# Configure AI (FREE with Ollama, or use Claude/GPT/Gemini)
slack-ai config

# Get a summary
slack-ai summary engineering --days 7

Done. You now have an AI summary of the last 7 days in #engineering.

Why?

Before:

You: "Claude Code, refactor our auth system"
Claude: "Sure, what approach should I use?"
You: *switches to Slack, scrolls 200 messages, reads for 10 min*
You: *switches back, lost context*

After:

$ slack-ai summary architecture --days 3
✓ Summary saved to ~/slack-notes/architecture_2025-11-02.md

# You paste this to Claude Code
You: "Claude, here's what the team decided. Now refactor our auth."
Claude: *generates perfect code aligned with team decisions*

Time saved: 30 min/day → 2.5 hours/week → 10 hours/month

AI Providers

| Provider | Cost | Setup | |----------|------|-------| | Ollama (local) | FREE | ollama pull gpt-oss:20b or ollama pull deepseek-r1:8b | | Claude | ~$0.10/summary | API key from Anthropic | | GPT | ~$0.10/summary | API key from OpenAI | | Gemini | ~$0.05/summary | API key from Google |

Recommended: Ollama with gpt-oss:20b (OpenAI) or deepseek-r1:8b for unlimited free summaries.

Commands

slack-ai login                                      # Authenticate with Slack
slack-ai config                                     # Set up AI provider
slack-ai my-channels                                # List your channels
slack-ai summary <channel>                          # Get AI summary
slack-ai summary <channel> --days N                 # Last N days only
slack-ai summary <channel> --user jack              # Filter by one user
slack-ai summary --all-channels --user jack,john    # Cross-channel search
slack-ai conflict <channel>                         # Detect team conflicts
slack-ai conflict <channel> --verify-with-code      # Compare with codebase
slack-ai interactive                                # Start interactive mode

Interactive Mode

Don't want to type slack-ai every time? Use interactive mode:

$ slack-ai interactive

╔════════════════════════════════════════╗
║   Slack-AI Interactive Mode            ║
╚════════════════════════════════════════╝

Type 'help' for commands, 'exit' to quit

slack-ai> my-channels
Available channels:
  #engineering
  #general
  #random

slack-ai> summary engineering --days 3
✓ Summary generated...

slack-ai> exit
✓ Goodbye!

Commands in interactive mode:

• summary <channel> [--days N] - Generate summary
• my-channels - List channels
• connect <channel> - Connect channel
• help - Show help
• clear - Clear screen
• exit - Exit interactive mode

Example Output

# engineering Summary – 2025-11-02

## Architecture Decisions

**Session Storage (Oct 28)**
- Sarah: Use Redis instead of Postgres for sessions
  → Rationale: Sub-ms latency, built-in TTL, proven at scale
  → Decision: Approved

**Password Hashing (Oct 27)**
- Mike: bcrypt with rounds=12
  → Rationale: OWASP recommendation, good perf balance

## Action Items

- [ ] Sarah: Deploy Redis cluster (Due: Oct 30)
- [ ] Mike: Update auth middleware
- [ ] Lisa: Document flow for mobile team

## Migration Plan

1. Week 1: Deploy new code (inactive)
2. Week 2: Enable for internal users
3. Week 3: Roll out to 10%
4. Week 4: Full migration

---
47 messages analyzed | Oct 24-28, 2025

Use Cases

1. Morning Catchup

slack-ai summary backend-team --days 1
# 30 seconds vs 30 minutes reading Slack

2. Onboarding New Devs

slack-ai summary project-alpha --days 30
# Instant project history instead of "read through Slack for 2 hours"

3. Cross-Team Context

slack-ai summary platform-team --days 7
# Understand backend decisions without interrupting them

4. Better AI Assistance

slack-ai summary architecture --days 14
# Paste to Claude Code → get team-aligned suggestions

5. Track Specific People

# What did the CTO say this week?
slack-ai summary engineering --user cto --days 7

# What did Jack and John discuss?
slack-ai summary backend --user jack,john

# Multiple people in the last 3 days
slack-ai summary general --user sarah,mike,lisa --days 3

6. Detect Team Conflicts ⚠️

# Are there any unresolved disagreements?
slack-ai conflict engineering --days 7

# Check conflicts between specific people
slack-ai conflict backend --between john,sara

# Find architectural disagreements
slack-ai conflict architecture --days 14

7. Cross-Channel Search 🔥 NEW!

# What did Jack say across ALL channels?
slack-ai summary --all-channels --user jack --days 7

# Track multiple people everywhere
slack-ai summary --all-channels --user john,sara,mike

Example Output:

📚 Searching across ALL channels...
✓ Found messages in 5 channels (127 total messages)

### Channel: #engineering (45 messages)
### Channel: #backend (32 messages)
### Channel: #general (15 messages)
...

8. Verify Code vs Slack 🤖 NEW!

# Do our decisions match the actual code?
slack-ai conflict engineering --verify-with-code

Example Output:

⚠️  Mismatch: Redis Session Migration

📝 Slack Decision:
  "Migrate sessions from Postgres to Redis"
  Date: 2025-10-28
  By: Jack, Sara

💻 Code State:
  Still using PostgresSessionStore
  Files: src/services/session.js:45

💡 Recommendation: Implement Redis session store as decided

Setup (First Time)

1. Invite App to Channels

Important: Before using any channel, invite the app:

1. Open the Slack channel
2. Type: /invite @Slack-AI
3. Done! Now you can run summaries

If you see not_in_channel error, this is the fix.

2. Install Ollama (for FREE AI)

# macOS/Linux
curl -fsSL https://ollama.ai/install.sh | sh

# Pull a model
ollama pull llama3.2

# Done! Zero cost forever.

3. Or use Cloud AI

Get an API key:

• Claude: https://console.anthropic.com
• GPT: https://platform.openai.com/api-keys
• Gemini: https://makersuite.google.com/app/apikey

Privacy & Security

• OAuth2 authentication
• Read-only Slack permissions
• Local storage of tokens
• No message content sent to our servers
• Anonymous analytics (opt-out available)

With Ollama: 100% of your data stays on your machine.

FAQ

Q: Does this work with private channels? A: Yes, if you have access.

Q: Can I use this for multiple workspaces? A: Not yet. Coming in v2.0.

Q: Does this cost money? A: CLI is free. Ollama is free. Cloud AI providers charge ~$0.10/summary.

Q: Is this open source? A: No, this is proprietary software. See LICENSE.

Q: Can my team use this? A: Yes! Everyone installs the CLI: npm install -g @slack-ai/cli

Support

• Bugs: [email protected]
• Features: [email protected]
• Enterprise: [email protected]

License

Copyright © 2025 Slack-AI. All rights reserved.

Proprietary software. See LICENSE for terms.

Built for developers who want to stay in flow.

© 2025 Slack-AI