CopilotKit / CopilotKit/outpost

Slack go-live: pre-deploy setup (App creation + Railway env vars)

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: channels roadmap roadmap: now
Dominant language
TypeScript
Stars
7
Forks
3
Avg merge
7d 16h
Merged PRs (30d)
15

Description

Context

Pre-deploy operational setup for the outpost-slack-bot service. Code is shipped (@slack/bolt Socket Mode app, message + action handlers, slash commands, health server) — this is configuration.

Timing: Week 2 platform — Discord + GitHub launch first.

Source: the Outpost go-live runbook (internal), Phase 1e.

Checklist

Slack App (api.slack.com/apps)
  • Create the Slack App in the workspace
  • Bot scopes: chat:write, channels:history, channels:read, users:read, reactions:read, commands
  • App-level token scope: connections:write (required for Socket Mode)
  • Enable Socket Mode (no public webhook URL required)
  • Generate SLACK_BOT_TOKEN (xoxb-...)
  • Generate SLACK_APP_TOKEN (xapp-...)
  • Note SLACK_SIGNING_SECRET from app settings
  • Install / authorize the app to the workspace
  • Register slash commands matching the bot's command registry (see apps/slack-bot/src/commands/)
Slack Connect channel onboarding (per-customer)
  • Identify the Slack Connect channels where the bot should listen (list tracked internally)
  • Customer-side admin invites the bot to each Slack Connect channel
  • Collect channel IDs → comma-separated list for MONITORED_CHANNEL_IDS
Railway env vars on outpost-slack-bot
  • SLACK_BOT_TOKEN
  • SLACK_APP_TOKEN
  • SLACK_SIGNING_SECRET
  • SLACK_SOCKET_MODE=true
  • MONITORED_CHANNEL_IDS — Slack channel IDs (NOTE: same env-var name as Discord uses; Railway scopes per-service, so this is OK)
  • TEAM_MEMBER_IDS — comma-separated team Slack user IDs (excluded from AI triggers — see apps/slack-bot/src/config.ts:10)
  • Shared via Railway refs: DATABASE_URL, ANTHROPIC_API_KEY, PATHFINDER_MCP_URL

Acceptance

  • Slack App exists with the listed scopes + Socket Mode enabled
  • Bot invited to at least one Slack Connect channel for the launch
  • All env vars populated on the Railway service

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the command registry in apps/slack-bot/src/commands/ and the team-member configuration at apps/slack-bot/src/config.ts:10 before setting up the Slack app. Configure the listed Slack scopes, Socket Mode, channel access, and Railway variables, then verify the app is installed, invited to a launch channel, and all required variables are populated.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cloud, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.