Slack

Slack is where many teams coordinate incidents, reviews, and day-to-day work. The Slack integration will bring X4RGE into that flow — start agent tasks from chat, get run updates in channels, and optionally trigger automations from messages.

Today: Slack appears on Dashboard → Integrations, but connect is not fully available yet. This page explains what that means, what to use instead, and what will change when connection ships.

Coming soon

If Connect on Slack does not finish, that is expected. For production automations and repo work now, use GitHub. Monitor runs in the Agents workspace until chat notifications ship.

What this page is for

You want to…	This page tells you…
Know if Slack works today	Current status vs coming features
Keep working without waiting	GitHub, Agents workspace, schedule automations
Understand the future flow	Notifications and triggers in your channels
Set up safely when it ships	Channels, org mapping, and admin approval

Slack complements GitHub

Slack is for people and notifications — who to ping when a run finishes. GitHub remains where agents clone code, open PRs, and listen for repo events. Connect GitHub first; add Slack when connect is ready.

Current status

Today	Coming with Slack
GitHub connect end to end	Workspace install from Integrations
Run status in Agents workspace	Completion messages in chosen channels
GitHub and schedule automations	Message- and command-based triggers
User API keys for CI	Optional notifications for headless runs

If Connect does not complete, you are not doing anything wrong — the integration is still being finished. Use What to use today until then.

Why Slack

Most teams do not live in the Agents workspace all day. Slack integration means runs find you where you already work — less tab-switching, clearer when something finished or needs input.

Without chat integration	With Slack connected
Everyone checks the Agents workspace	Run finished / failed pings the right channel
Hard to kick off work from incidents	Start or route tasks from a dedicated channel
Notifications scattered	One place next to your standups and alerts

Slack complements GitHub (code events) — it is for people and ops, not replacing repo access.

How Slack fits your workflow

Think of two layers:

Layer	Tool	Role
Chat & alerts	Slack	Notify the team, optional triggers from messages
Code & automations	GitHub + X4RGE	Repos, PRs, event-driven cloud runs

Today: watch runs in the Agents workspace (or Sentinel); use GitHub for automations.

When Slack ships: completion messages and optional chat triggers land in channels you choose.

In practice

Use this table to pick your next step. Rows marked today work now; later need the connect flow.

You want to…	Do this	When
Event-driven cloud runs	GitHub + Automations	Today
See run status	Agents workspace or Sentinel	Today
CI / headless from pipelines	Headless CLI with org-approved API keys	Today
PR updates in Slack	GitHub's native Slack app for merge-ready notifications	Today
X4RGE run finished / failed in channel	Connect Slack when available	Later
Start a run from a Slack message	Connect Slack when available	Later

What to use today

Until Slack is connectable, this is the reliable path most teams use:

GitHub — primary integration for cloud runs, PRs, and automations.
Agents workspace — start runs and watch progress directly.
Sentinel — operational summary for recent agent activity.
Schedule automations — time-based jobs without chat triggers.

PR notifications today

For merge-ready PR alerts in Slack, use GitHub's Slack app alongside X4RGE — X4RGE chat notifications for agent runs will come with the Slack integration.

Rollout order

Prove value on GitHub and one repo first, then add chat notifications when Slack is ready — same staged rollout most teams use for agent adoption.

When Slack is available

When connect ships, your organization admin (or someone with Integrations access) will set this up from the dashboard. Plan for these steps:

Add the X4RGE Slack app
From Integrations in the dashboard, authorize the app for your workspace. A Slack workspace admin may need to approve the install.
Choose channels
Pick channels for notifications and commands. Prefer a dedicated channel (for example #x4rge-agents) over high-traffic general channels.
Link to your X4RGE organization
Confirm the Slack workspace maps to the correct org so Usage and Model control policies apply.
Send a test
Start a cloud run and confirm a completion message appears in the selected channel with a link back to the run.

Your org may require integration approval before Slack goes live, same as other connectors.

What it will enable

Once connected, Slack becomes a notification and optional trigger surface — not a replacement for GitHub repo access.

Start tasks from a message or slash command (within policy).
Run notifications — started, completed, failed, cancelled — with links to diffs and PRs.
Automation triggers when messages match patterns (for example an alert URL posted in channel).
Scoped visibility — people only see activity they are allowed to access in X4RGE.

Messages will typically include run status, repository and branch, a short summary, and links to open the run, diff, or PR — without secrets or credentials in chat.

Until Slack triggers are active, use schedule or GitHub triggers for production automations.

Security habits

When Slack can start paid cloud runs, channel choice and install approval matter for spend and access — not just convenience.

Topic	Guidance
Channels	Use team channels where members have X4RGE access
Secrets	Never post API keys or tokens in Slack — agents use stored secrets
Install	Require workspace admin approval for the Slack app
Audit	Run starts from Slack will appear in your org audit trail