ANTHROPIC PUB_DATE: 2026.03.24

ANTHROPIC BRINGS COMPUTER USE AND CHAT CHANNELS TO CLAUDE CODE

Anthropic is rolling out Computer Use and chat Channels for Claude Code, adding OS control and Discord/Telegram texting to the coding agent. Claude Code and Co...

Anthropic is rolling out Computer Use and chat Channels for Claude Code, adding OS control and Discord/Telegram texting to the coding agent.

Claude Code and Cowork can now open files, use the browser, and run dev tools via Computer Use on macOS, with permission prompts and a research-preview rollout to Pro/Max users; it also ties into Dispatch for continuous phone/desktop conversations Engadget. Anthropic advises against using it with sensitive data for now.

Separately, Claude Code Channels let teams message the agent from Discord and Telegram, with admin-managed allow-lists and a Model Context Protocol (MCP) backbone for safer integrations SiliconRepublic. This moves control from IDE-only to everyday chat apps.

These features align with Anthropic’s push toward longer-running agentic workflows in real projects, like multi-day scientific coding tasks coordinated by Claude Code Anthropic research.

[ WHY_IT_MATTERS ]
01.

Agents can now handle real machine actions and meet engineers in chat, reducing context switching and enabling hands-off automations.

02.

Admin controls and allow-lists offer a safer path to adopt agentic workflows without surrendering auditability.

[ WHAT_TO_TEST ]
  • terminal

    Run a one-week pilot of Computer Use on a non-prod macOS box to measure time saved on routine dev tasks and prompt frequency.

  • terminal

    Stand up a private Discord/Telegram Channel with allow-lists and trial on-call runbook helpers (logs, rollbacks, status pings) with strict scopes.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Enforce SSO, secrets scanning, and directory/repo allow-lists for OS actions; log all agent prompts and tool calls for audit.

  • 02.

    Map Channels and Dispatch into existing Slack/Teams patterns to avoid bot sprawl; define ownership for bot tokens and rotations.

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    Design new internal tools as small, auditable MCP endpoints that Claude can invoke from chat or the desktop agent.

  • 02.

    Default to chat-first workflows for CI nudges, ephemeral env spins, and GitOps chores with least-privilege scopes.

SUBSCRIBE_FEED
Get the digest delivered. No spam.