Slack Green CLI Documentation

The Slack Green CLI is a terminal application that keeps your Slack status active. It runs entirely on your machine — your Slack tokens never leave your device.

$45.99 one-time purchase. No subscription.

Installation

1. Download

Go to Dashboard → CLI and download the binary for your platform:

• • macOS — Apple Silicon (M1+) or Intel
• • Windows — Windows 10+
• • Linux — x64

2. Install the binary

macOS / Linux:

bash
chmod +x ~/Downloads/sg-cli-*
sudo mv ~/Downloads/sg-cli-* /usr/local/bin/sg-cli

If macOS blocks the binary with Gatekeeper:

bash
xattr -d com.apple.quarantine /usr/local/bin/sg-cli

Windows:

Move sg-cli.exe to a directory in your PATH, or run it directly from the download folder.

3. Launch

bash
sg-cli

That's the only command. Everything happens inside the interactive TUI.

First Launch

On first launch, the TUI prompts you to enter your license key (SG-XXXX-XXXX-XXXX-XXXX). You can find this key on your CLI dashboard.

After activation, the app validates your license with the server and starts the background daemon automatically.

Using the TUI

The TUI is a full-screen terminal interface. It shows your connected workspaces, their presence status, and daemon health.

Keyboard Shortcuts

Status Bar

The status bar at the bottom shows:

• Daemon status — running, connected count

• License status — valid or expired

• Token health — any invalid tokens

• Last refresh — seconds since last data poll

• Timezone clock — current time in your configured timezone

Workspace Cards

Each workspace shows:

• Name and status badge (Active, Paused, Scheduled, etc.)

• Presence — polled directly from the Slack API on every refresh

• Schedule — current schedule or "Always On"

Adding a Workspace

Press a to open the Add Workspace modal. You have two options:

Option 1: Chrome Extension Token (recommended)

Install the Slack Green Chrome Extension

Open Slack in Chrome, click the extension icon

Copy the JWT token

Paste it into the "Chrome Extension Token" field

Option 2: Manual Tokens

Enter your xoxc and xoxd tokens manually. See the token extraction guide for how to find these.

After adding, the TUI automatically opens the schedule editor for the new workspace.

Schedules

Press c on a selected workspace to edit its schedule.

The schedule editor lets you:

• Select active days — click days or press w for weekdays, e for every day

• Set start/end times — type times like 9am, 9:30, 14:00, or use arrow buttons

• Always On — removes the schedule entirely

Outside of scheduled hours, the daemon pauses the workspace automatically.

How the Daemon Works

The daemon is a background process that maintains WebSocket connections to Slack.

• Auto-starts when you launch the TUI

• Keeps running after you close the TUI

• Reads config from ~/.sg-cli/workspaces.enc (encrypted)

• Writes status to ~/.sg-cli/status.json

• License refresh — validates with the server periodically; works offline for up to 10 days using a signed token

The TUI and daemon communicate via a Unix socket. When you add, remove, or modify workspaces in the TUI, the daemon picks up changes immediately.

Device Management

Each license allows one device at a time. Your device is identified by a machine fingerprint (hostname, OS, MAC address, etc.), so restarting your computer does not require re-activation.

To switch devices:

Go to Dashboard → CLI

Remove the old device

Run sg-cli on the new device and activate

Privacy

• Slack tokens are stored locally in ~/.sg-cli/workspaces.enc, encrypted with a machine-specific key

• License config is stored in ~/.sg-cli/config.enc

• The server only knows: your license key, email, device ID, and last-seen timestamp

• The server never sees: workspace names, Slack tokens, team IDs, or any user activity

File Locations

Running on Startup

The daemon auto-starts when you launch the TUI. To have it start at login without opening the TUI:

macOS (launchd)

Create ~/Library/LaunchAgents/com.slackgreen.cli.plist:

xml




    Label
    com.slackgreen.cli
    ProgramArguments
    
        /usr/local/bin/sg-cli
    
    RunAtLoad
    
    KeepAlive
    

Load it:

bash
launchctl load ~/Library/LaunchAgents/com.slackgreen.cli.plist

Linux (systemd)

Create ~/.config/systemd/user/sg-cli.service:

ini
[Unit]
Description=Slack Green CLI
After=network.target
[Service]
ExecStart=/usr/local/bin/sg-cli
Restart=always
RestartSec=10
[Install]
WantedBy=default.target

Enable it:

bash
systemctl --user enable sg-cli
systemctl --user start sg-cli

Troubleshooting

"Signing secret missing"

Your local config is out of sync. Fix:

bash
rm -rf ~/.sg-cli
sg-cli

Then re-activate with your license key.

Daemon not connecting

Check ~/.sg-cli/sg-cli.log for errors

Verify your Slack tokens are still valid (Slack rotates cookies periodically)

Press r in the TUI to force a refresh

Token expired

Slack tokens expire when you log out of Slack in your browser or when Slack rotates cookies. Re-add the workspace with fresh tokens by pressing d to remove the old one, then a to add it again.

macOS Gatekeeper blocks the binary

bash
xattr -d com.apple.quarantine /usr/local/bin/sg-cli

FAQ

Can I use my license on multiple computers at the same time?

No. Each license is bound to one device at a time. You can switch devices from the CLI dashboard.

What happens if my computer goes to sleep?

The daemon stops maintaining presence while the computer is asleep. Options:

• Adjust power settings to prevent sleep

• Run on an always-on machine (home server, Raspberry Pi, VPS)

Does it work with Slack Enterprise Grid?

Yes. The CLI uses browser tokens, which work with all Slack plans including Enterprise Grid.

How do I update to a new version?

Download the latest binary from Dashboard → CLI and replace the old one. Your config and workspaces are preserved.

How is this different from the cloud subscription?

| Best for | Set-and-forget | Privacy-focused users |