▤
Channel posts
Cyborg posts to specific channels you grant access to (whitelist). New deals, deploys, alerts, weekly digests. Markdown, blocks, attachments · never @-channel without explicit role config.
scope:chat:write
TOOL · I/01 · MESSAGING TRIBE
Slack — where every Cyborg posts, threads, replies.
Install the A'nil Cyborg Slack app in 90 seconds. Each Cyborg you hire gets its own bot identity (@cyborg-eng, @cyborg-sales, @cyborg-legal...) with role-scoped channel access. Posts updates, threads context, DMs the right owner on alerts, requests approvals via interactive buttons. Bot-attributed on every message. Never sees DMs it isn't tagged in. Audit log streamed to your S3.
FREE with any Cyborg
·
INSTALL 90 seconds
·
SCOPES 8 (least-privilege)
— 02 / WHAT IT DOES IN SLACK
— CAPABILITIES
8 things Cyborgs do in Slack — all auditable.
Every Slack action falls into one of 8 categories. All are bot-attributed (BOT badge), all logged to your audit stream, all revocable from your workspace admin panel.
⌬
Threaded replies
Cyborg replies in-thread to keep channels clean. Auto-threads its own follow-ups (e.g. PR opened → review summary → CI status → merge confirmation all in one thread).
scope:chat:write●
Direct messages (paged-only)
Cyborg DMs the right human owner only when paged or @-mentioned. Cyborg cannot read DMs unless added to them. No "spy mode". DM intake closed by default.
scope:im:write · im:history (own only)◆
Interactive buttons + approvals
Approve / Reject / Edit / Snooze buttons on action posts. Owner clicks → action runs upstream (deploy, contract sign-route, refund issue). Audit-stamped to clicker.
scope:chat:write + Block Kit▥
Slash commands
/cyborg ask <question>, /cyborg deploy <service>, /cyborg contract status <id>. Per-role command sets. Permission-gated to channels + users you allow.
commands⊜
Files + canvas attachments
Cyborg posts PDFs (board pack, PR diff, contract redline), CSVs (sales pipeline export, finance reconciliation), and Slack canvases (weekly digest, SOPs).
scope:files:write★
Reactions + status pins
Cyborg reacts to messages it processed (✅ done, 👀 reviewed, ⏳ queued). Pins critical messages (active incident, on-call rotation, weekly OKR).
scope:reactions:write · pins:write⊕
Workspace user lookup (lite)
Cyborg looks up Slack users by email (e.g. resolves "@dharm" from PagerDuty alert → DM correct owner). Read-only, name + email + tz only. Never reads message history.
users:read · users:read.email
— 03 / SAMPLE
— REAL WORKSPACE · TUESDAY 11:00 IST · ANONYMISED
5 cyborgs, 5 channels, one Tuesday morning.
A live snapshot of what your workspace looks like 7 days after install. Each Cyborg posts in its own lane, threaded, bot-attributed. Owners click buttons to approve. No noise.
#engineering
CE
cyborg-engBOT11:02 AM
PR #4218 opened by @dharmesh · "Refactor caching layer to use Redis cluster mode"
Auto-review summary · +312 / −487 across 14 files
3 minor suggestions (1 missing null-guard in CacheKeyBuilder, 2 doc comments missing). 0 security flags. Tests pass locally. CI running · ETA 4 min.
DH
dharmesh11:05 AM
Fixed the null-guard, pushed. Comments inline.
CE
cyborg-engBOT11:08 AM
Re-reviewed. ✅ Looks good. CI green. Ready to merge.
#sales-pipeline
CS
cyborg-salesBOT11:14 AM
🎯 Qualified lead · NorthStar Logistics · CEO replied to outbound seq #4
Reply preview · sentiment: positive 0.81
"Interesting timing — we're evaluating exactly this in Q3. Can you do a 30-min call next Tuesday?"
#cs-tickets
CC
cyborg-csBOT11:18 AM
⚠ Escalation · ticket #8214 · Enterprise customer (BigCo) reports billing discrepancy · CSAT-risk · needs human
Triage summary
Customer was double-charged on April 28 ($1,200). I drafted refund + credit-note response (canned reply not adequate — this is real money). Routing to @priya for sign-off. SLA < 30 min.
#finance-daily
CA
cyborg-acctBOT11:21 AM
📊 Daily flash · Tue 7 May 2026
P&L snapshot · cash: $4.82M · runway: 18.4 mo
Revenue MTD $312k (88% to plan). Burn MTD $184k (within ±3%). 2 unreconciled wires from yesterday — routed to @anil for class-tagging. 1 P0 anomaly: AWS bill projected $42k vs $28k plan — investigating with @dharm.
#legal-drafts
CL
cyborg-legalBOT11:24 AM
📝 Redline ready · AcmeCorp MSA v4 · routed to @gc
14 changes · 8 standard / 6 deviations · risk 3.4 / 5
Auto-applied 8 standard playbook positions. 6 deviations need GC: limit-of-liability cap, IP assignment, indemnity scope, audit rights, governing law, termination notice. Drafted rationale for each. ~18 min review estimated.
ANONYMISED FROM 4 LIVE CUSTOMER WORKSPACES · ALL SCREENSHOTS USE PERMISSION · NAMES + DOLLAR FIGURES OBFUSCATED
— 04 / SCOPES · LEAST PRIVILEGE
— OAUTH 2.0 · YOU CONTROL EVERYTHING
8 scopes — not 28. Each one earns its way in.
No admin scopes. No "user token" access (only bot tokens). Cyborg cannot install other apps, change workspace settings, read other users' DMs, or make payments. Workspace admin can revoke any scope per-cyborg from the admin panel.
| Scope | What it allows | Why we need it | Risk | Default |
|---|---|---|---|---|
chat:write |
Post messages as the bot, edit own messages | Core. Cyborg posts updates, threads replies, sends approval cards. | Low | ON |
im:write |
Open DMs to a user (one-way) | DM the right human owner on alerts (e.g. on-call escalation, refund approval). | Low | ON |
im:history |
Read DMs the bot is part of | So owner can reply in DM and Cyborg sees the reply. Bot cannot see other DMs. | Low | ON |
commands |
Receive slash-command invocations | Power /cyborg deploy, /cyborg ask, etc. Per-role allowlist. |
Low | ON |
files:write |
Upload files (PDF, CSV, canvas) | Post PDFs (PR diff, board pack, contract redline), CSVs (pipeline export). | Low | ON |
reactions:write + pins:write |
React + pin own action messages | Status reactions (✅ done, ⏳ queued) and pin active incidents / OKRs. | Low | ON |
users:read + users:read.email |
Look up user by email, get name + tz | Resolve "the on-call SRE" to the right Slack user when paged from PagerDuty. | Low | ON |
channels:read |
List public channels Cyborg can join | So workspace admin can pick which channels each Cyborg may post to. Read names only. | Low | ON |
NEVER REQUESTED: admin.* · users:write · channels:history (other channels) · groups:history · im:history for non-bot DMs · files:read across workspace · payment scopes · user tokens (only bot tokens). |
||||
— 05 / INSTALL
— 90 SECONDS · WORKSPACE ADMIN APPROVAL REQUIRED
Install flow: 90 seconds, 5 clicks.
-
01
Click "Add to Slack"
From any Cyborg's hire flow or from this page. Opens Slack OAuth consent in a new tab.
-
02
Pick workspace + grant 8 scopes
Slack shows the exact scope list (no surprises). Workspace admin must approve if you're not admin yourself. Most teams approve in ~30 seconds.
-
03
Choose channel allowlist (per-cyborg)
For each Cyborg you've hired, pick the channels it may post to. Defaults: cyborg-eng →
#engineering, cyborg-sales →#sales-*, etc. You can change this anytime in the admin panel. -
04
Slack-side identity test
Each Cyborg posts a "Hi, I'm
@cyborg-eng, here's what I'll do" hello message in its primary channel. Owner reacts ✅ to confirm. If anything looks off, single-click revoke. -
05
Audit stream wired
Every Cyborg Slack action (post, edit, button click, file upload) is mirrored to a Cyborg-side audit log. Optional: stream to your own S3 bucket / Datadog / Splunk via webhook.
— 06 / ROLES THAT USE SLACK
— ALL 12
Every Cyborg posts to Slack — in its own channel.
Each role gets its own bot identity (own avatar, own colour, own channels). Click any role to see how it uses Slack specifically.
{ }Software Engineercyborg-eng · #engineering
◐Designercyborg-design · #design-reviews
◇Project Managercyborg-pm · #standup
▲Data Analystcyborg-data · #data-digest
✱Marketingcyborg-mkt · #marketing-pipe
♦Salescyborg-sales · #sales-pipeline
◑Customer Supportcyborg-cs · #cs-tickets
⌬HR / People Opscyborg-hr · #hr-pipeline
$Accountantcyborg-acct · #finance-daily
△Financial Managercyborg-fm · #finance-board
⚙Operationscyborg-ops · #ops-incidents
⚖Legal Assistantcyborg-legal · #legal-drafts
— 07 / SECURITY MODEL
— BOTH SIDES OF THE WIRE
Slack-side + Cyborg-side. Two layers, one trust.
Slack-side (your workspace)
- Bot tokens only. No user tokens. Cyborg cannot impersonate a human.
- Per-channel allowlist. Workspace admin picks which channels each Cyborg can post to. Default deny-all.
- BOT badge on every message. Slack-native attribution — nobody can confuse Cyborg with a human.
- Single-click revoke. Workspace admin →
/apps→ Cyborg → "Remove" disconnects all 12 cyborgs at once. Or per-cyborg from Cyborg admin panel. - No DM eavesdropping.
im:historyonly on DMs the bot is in. Cannot read other DMs.
Cyborg-side (our infra)
- Tokens encrypted at rest. AES-256 in AWS KMS, per-customer key, rotated 90 days.
- Audit log every action. Every
chat.postMessage, button click, file upload — logged with timestamp + user + payload digest. - Stream to your S3 / Datadog / Splunk via outbound webhook (optional but encouraged).
- SOC 2 Type II + ISO 27001. Cyborg's Slack handler is in scope — we share the report under NDA.
- No data retention beyond 30 days. Action payloads purged after 30 days unless required for active workflow context.
— PRICING
See Cyborg pricing
Slack is free with every Cyborg.
No per-message charge. No per-channel charge. No "Slack premium tier" upsell. Every Cyborg you hire from $499/month onwards posts to Slack at no extra cost. Even the unlimited NDA reviews from Legal Cyborg post to Slack for free.
— 09 / FAQ
— WORKSPACE ADMIN + IT QUESTIONS
Sawaal jo IT + workspace admin poochte hain.
Can Cyborg read DMs between humans?
No. im:history only applies to DMs the bot is part of. If you DM another human, Cyborg literally cannot see it — Slack's API will not return those messages to our token. We don't request groups:history, mpim:history, or any cross-user reading scope. You can verify this in Slack admin → app permissions.
What happens if Cyborg posts something wrong?
Three things. (1) Every message is BOT-attributed — obvious it's automated. (2) Workspace admin can delete any Cyborg message in 1 click. (3) Wrong-post is logged to your audit stream so you can trace cause and we can tune the rule that triggered it. In 4,318 workspaces over 18 months, we've had 11 wrong-post incidents — all in shadow/test channels, none reached a customer-facing channel.
Can we restrict Cyborg to private channels only?
Yes — per-channel allowlist. Workspace admin picks exactly which channels (public or private) each Cyborg may post to. Default is deny-all. To grant access to a private channel, an existing member of that channel just /invite @cyborg-eng (or whichever bot) once — that's the Slack-native way.
What about Slack Enterprise Grid (multi-workspace)?
Supported. Cyborg installs at the org level (Org Owner approval) with per-workspace channel allowlists. Each Cyborg can post to designated channels across multiple workspaces in your grid — useful when, e.g., your sales workspace and engineering workspace are separate. Pricing unchanged: still free with any Cyborg.
Can Cyborg @-channel or @-everyone?
Disabled by default. @-channel requires per-cyborg + per-channel explicit enablement (admin panel toggle). @-everyone is hard-disabled for all cyborgs. You'll never wake up to a 3am workspace-wide ping.
What if we use Microsoft Teams instead?
Use it. Microsoft Teams integration is feature-equivalent (channel posts, threaded replies, adaptive cards for approvals, channel allowlist). About 35% of our customers run Teams instead of Slack — same Cyborgs, different surface.
If we cancel, what happens to message history?
Your Slack message history is yours — we never owned it. On uninstall, the Cyborg app is removed from your workspace, all OAuth tokens are revoked, and our 30-day rolling action log is purged within 7 days. Slack-side, every message Cyborg posted stays in your workspace exactly as it is (you can choose to delete via Slack's normal export/delete tools).