DEDUPED Hot AI repos. Real use cases. What people build. Get the Monday 5

How to add Slack and a knowledge base to your Sim install with Sim

Switch on optional capabilities one at a time so agents can post to Slack and answer from your documents.

Short answer: From your install directory run npx sim-setup add integration slack; then enable knowledge bases with npx sim-setup add knowledge; add or change a model provider with npx sim-setup add llm. All steps.

permissions. A Slack integration lets agent workflows post in your workspace, so scope the bot to the channels it needs.

Who it is forA team lead automating internal questions and notifications.

The problemRerunning a full setup for each new integration is slow and risky.

The outcomeA Sim install with Slack integration and knowledge enabled, verified by the config report.

What you need first

  • Node.js 20+ and Docker for self-hosting
  • A Chat API key for the model provider, or local models via Ollama or vLLM
  • Or the hosted cloud at sim.ai

Steps

  1. From your install directory run npx sim-setup add integration slack
  2. Enable knowledge bases with npx sim-setup add knowledge
  3. Add or change a model provider with npx sim-setup add llm
  4. Run npx sim-setup config to see configured, missing or invalid capabilities without printing credential values

Prompt for your agent

In my simstudioai/sim install, run `npx sim-setup add integration slack` and `npx sim-setup add knowledge`, then `npx sim-setup config`, and summarize what is configured and what is still missing.

Caveat. Keep the install current with `npx sim-setup update`, which pulls and applies the Compose images.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for simstudioai/sim and "Add Slack and a knowledge base to your Sim install"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer