Ops · incident watch · SRE persona

{{SLACK_ICON}} #ocw-test · Jordan Lee via Slack C0BD7KZ1AH5 · U07JK68S4BH 2:14 PM

Hey team — can someone confirm the staging deploy actually went out? Dashboard still shows the old build.

Assistant

I checked the deploy log in the workspace — the staging release v2.4.1 finished at 2:09 PM. The dashboard cache likely hasn't refreshed. I'll post a note back in the channel and pin the release notes.

2 actions · 1 approval ✓ show details

send_message target: slack:#ocw-test · text: "staging v2.4.1 is live (2:09 PM)…" done

{{SLACK_ICON}} write_file approval · sent to #ocw-approvals Approved by Alex Rivera in Slack

path: runbook-notes.md · content: cache TTL 5m; pin v2.4.1 notes…

{{SF_ICON}} Case #00123 · Dana Whitfield via Salesforce 2:21 PM

New comment on the escalation: customer confirms the workaround held overnight. OK to downgrade severity?

Reply in #ocw-test that the cache should clear in ~5 min, and ask Dana for the latest log before we downgrade.

📁 1 directory ● Unattended claude-opus-4-8 ▾

Message the coworker…

Ask for approval ▾

Connectors

Apps and tools OpenCoworker can use. You bring the credentials for this local build.

Slacktwo-way

deeplearning.ai / ocw · 1 allowed

Allowed to message

AR Alex Rivera

Recent senders

JL Jordan Lee · channel

Salesforce

Cases, comments, records

HubSpot

CRM, tickets, contacts

Two-way messaging

Messaging routing

How inbound messages reach sessions, and where Unattended approvals go out.

Channel subscriptions — sessions that listen to a channel (inbound)

Session	Listens to	Inbox routes to
hi	{{SLACK_ICON}} #ocw-test	{{SLACK_ICON}} #ocw-approvals

Direct messages

Session that handles DMs to the bot. Unrouted DMs are parked under Activity.

Unattended approvals

Channel where an Unattended session posts Approve/Deny buttons.

Activity

Unrouted inbound and background-turn failures — nothing vanishes silently.

When	Source	Reason	Message
2:31 PM	{{SLACK_ICON}} DM · casey	no DM session designated	hey, are you around? quick q…
2:28 PM	session 856b16f8	401 · invalid model auth	💬 New message on #ocw-test…

· Persona

🛠️

Ops Coworker

Operate and investigate — runbooks, logs, infrastructure

Enabled

About

A careful, methodical operations engineer. It investigates incidents, runs runbooks, inspects logs and metrics, and produces clear operational deliverables — incident notes, postmortems, runbook updates — preferring read-only, reversible steps and asking before anything consequential.

Built-in capabilities

files search shell todo

Connections for full benefit

Declared by the persona — wire Ops into these to unlock its full workflow.

GitHubcore

confirm deploys and inspect the PRs behind a change

connected

Slackcore

receive alerts and reply to the team in-channel

connected

Datadogcore

pull the firing alerts and the incident timeline

PagerDuty

see who's on-call before paging

FilesystemMCP

read runbooks and postmortems from a local folder

New sessions get by default

When you start an Ops session these are enabled automatically. You can still mute any of them per session.

Slack

GitHub

Datadog · connect to enable

Models · claude-opus-4-8, gpt-5.5

Default mode · Interactive

Workspace · deliverable

Connectors

Messaging routing

Activity

MCP servers

Ops Coworker