slack-setup

You can extract a Slack session token and the companion d cookie using a Chrome remote debugging instance for automated extraction, or manually through browser DevTools as a fallback. Both methods require an active signed-in Slack browser session to capture the xoxc- token and d cookie.

Automated Slack token extraction requires the jq and node command-line tools, along with access to a Chrome remote debugging instance. You must also have an active, signed-in Slack session in the browser to programmatically pull the session credentials.

Yes, you can manually extract Slack credentials using browser DevTools. The skill documents step-by-step DevTools methods to locate the xoxc- session token and companion d cookie in network requests when the automated Chrome remote debugging approach is not available.

Extracting the Slack xoxc- token is necessary when enterprise Slack apps are restricted. This session token and companion d cookie provide an alternative authenticated API access method, allowing you to read message history, search messages, and post updates.

You can verify Slack session tokens using included verification commands to confirm authentication status after extraction. When tokens expire, the skill provides guidance to refresh and renew them by re-running the credential capture script to update the local environment file.

Yes, this Slack session token extraction process applies specifically to enterprise Slack workspaces where standard API apps are restricted. It captures the xoxc- token and d cookie from your signed-in browser session to enable authenticated read, search, and post message workflows.