Channel-native workflows
Start any workspace workflow from a message. The agent replies in-thread with progress, artifacts, and questions.
Recorded with the runThread-linked run
Surfaces
Context in Slack
The full platform, in the channel where the work is discussed.
Install Context into Slack and any channel can raise, review, and approve agent work without leaving the conversation. Agents post progress in threads, request approval inline, and file results back to the workspace.
Context in Slack
Example workflow
# finance-ops28 members
MC
Maya Chen 10:42
@Context review the Kestrel refund and prepare the approval packet.
CReady
Context 10:42
I checked the case, policy, and account history. The refund is within Maya's review scope and needs one approval.
Refund review
$18,420 · Kestrel Labs
Policy checks 6/6 · sources 4 · confidence high
ApproveReview details
How it works
From request to a reviewable result.
Each run keeps the request, actions, evidence, and final decision together.
01 · Request
Mention Context in a thread.
Ask for a supported workflow in plain language. Context resolves the requester, channel, and relevant conversation.
Output · Scoped run created
02 · Work
Follow progress where you asked.
The agent posts sources, intermediate artifacts, and questions into the same thread as it works.
Output · Trace visible in Slack
03 · Decide
Approve the consequential step.
Review, edit, or reject the proposed action inline. The decision is recorded with the completed run.
Output · Decision captured
What you can inspect
Capability is only useful when it leaves evidence.
Approvals without switching tools
Accept, edit, or reject agent output from the thread. Every decision is captured as feedback for the loop.
Recorded with the runReviewer and timestamp
The requester's permissions
Agents use the identity configured for the workflow: a delegated user or a scoped service identity resolved through your IdP.
Recorded with the runResolved principal and scope
Same audit trail
Slack-initiated runs land in the same trace store and eval pipeline as everything else.
Recorded with the runRun trace and grade
Deployment boundaries
Control is part of the product.
Context in Slack can run as a standalone surface, while its traces, evals, and policy decisions remain part of the same Context system.
Supported workflows
Administrators choose which agents can be invoked from Slack and which actions require approval.
Slack is the surface
Long-form artifacts and full run traces remain in Context; the thread carries status, decisions, and links.