Slack

Start Niteshift tasks through Slack DMs or mentions. Replies include progress, results, and task and pull request links.

Setup

You need a Niteshift account. Sign up, connect your repository, and configure an environment.

Install the Slack app

Open Settings → Connections → Integrations → Slack, click Add to Slack, and approve installation in your workspace. This links your Slack account.

Choose a default environment

Set Default environment in that panel. A default is required even when specifying another environment. Each teammate must connect their Niteshift account.

Invite the bot to channels

Run /invite @Niteshift in each channel, including private channels.

How to use

Direct messages

DM Niteshift your task description for a private conversation.

Slack direct message with Niteshift showing a user prompt and Niteshift starting work on the task.

Channel mentions

Mention @Niteshift with your request. Channel mentions include recent channel context; mentions inside threads include that thread instead. Updates appear in the task’s thread.

Slack thread with a Datadog alert, a user asking Niteshift to identify a root cause and open a pull request, and Niteshift responding with a root cause and task links.

Choose a model and environment

Pick a model and environment in your starting message using plain English, in channels or DMs:

@Niteshift use sonnet to fix the login page.
@Niteshift use opus in Payments Staging to investigate the failed deploy.
@Niteshift use gpt astra in the Mobile environment to fix the settings screen.

Use a model available to the task’s account and an accessible environment. Environment names are case-insensitive and must identify one environment. Model shorthand selects the newest matching model. Request supported effort levels with wording like use gpt astra at high effort. Unrecognized or ambiguous choices keep your defaults. So does discussing a model or environment, such as add Sonnet to the model picker. Follow-ups continue the existing task.

Thread follow-ups and team replies

Reply in the DM thread, or mention Niteshift again in the channel thread:

@Niteshift also add a test for expired sessions.

Personal tasks accept owner follow-ups; teammates get Start a new task. For shared tasks, see Multiplayer Slack tasks.

Task link previews

Share a niteshift.dev task link to preview its title, repository, model, and pull request. Previews require the sharer’s task access and are visible throughout the conversation.

Configuration

Slack App Home

In Home, set Default repository and Default model. Repository selection uses its default environment; choose another in web settings. Your default follows your account’s model.

Web settings

In Slack settings, connect your account, change Default environment, or Unlink.

In Settings → Preferences, the Slack model picker overrides or follows your account’s default.

Slack model preference showing GPT-6.1 Sol with Default, following the account's default model. — Default model for Slack tasks.

Multiplayer Slack tasks

Multiplayer tasks run under a shared service account. Active organization members with linked Slack accounts can direct the same agent in a channel thread.

Multiplayer tasks are in early access. Contact support for access.

In Organization → Members & service accounts, edit a service account, select Add to Slack, and turn on Answer @Niteshift in this workspace. New channel mentions start shared tasks.

Permissions

Bot scopes

Support requests, updates, and Slack tools.

Conversations and updates

Scope	Reason
`app_mentions:read`	Receive mentions.
`assistant:write`	Show task status in Slack’s agent view.
`commands`	Authorize commands and shortcuts.
`channels:history`	Read public-channel context.
`channels:join`	Join public channels.
`channels:read`	Find public channels for agent messages.
`groups:history`	Read private-channel thread context for mentions.
`groups:read`	Identify accessible private channels.
`im:history`	Read DM requests and follow-ups.
`im:read`	Identify app DMs.
`im:write`	Open DMs for notifications and agent messages.
`mpim:history`	Access group DM history.
`mpim:read`	Identify group DM conversations.
`chat:write`	Send updates, replies, and agent messages.
`chat:write.customize`	Customize message sender names or icons.
`reactions:read`	Read reactions through agent tools.
`reactions:write`	Mark progress and add agent-requested reactions.
`links:read`	Detect shared task links.
`links:write`	Add authorized task previews.

Files, canvases, and workspace information

Scope	Reason
`files:read`	Download attachments for task context and agent tools.
`files:write`	Let the agent share files and images.
`canvases:read`	Let the agent read canvases and locate sections.
`canvases:write`	Let the agent create and update canvases.
`users:read`	Identify authors; let the agent find members and profiles.
`users:read.email`	Look up account identities by email.
`team:read`	Read workspace details.
`users.profile:read`	Read member profile fields.

User scope: message search

For personal tasks, the agent uses your Slack token to find relevant messages in public channels you can access, including channels where the bot hasn’t been added.

Scope	Reason
`search:read`	Search messages.

Data and privacy

Niteshift reads your prompt, thread or recent channel context, and attachments to work on your request. Slack tools can read additional accessible data during tasks. Read the privacy policy or contact support. Disconnect through Unlink in Slack settings, or uninstall workspace-wide through Slack’s app management.

Start

Environment configuration

Platform

Interfaces

Customizing agents

Setup