Shared Communication with Claude Code

When one developer uses Claude Code, they see everything it does. When a team uses it, everyone else is blind — unless you build shared communication channels. This guide covers patterns for making Claude Code's activity visible to your whole team.

The visibility problem

Claude Code sessions are inherently private. The developer who started the session sees the full transcript. Everyone else sees nothing until a PR appears. This creates gaps:

Team leads don't know what's being worked on or how much it costs
Developers working on related tasks don't know about overlapping changes
On-call engineers can't see what automated agents are doing
Non-technical stakeholders have no visibility into AI-assisted progress

Notification patterns

Session start/end notifications

Post a message to your team channel when a Claude Code session starts and when it completes. Include: who started it, which project, what the task was, and whether it succeeded. This gives the team ambient awareness without information overload.

PR notifications

When Claude Code creates a pull request, post it to the relevant channel with a summary. This is often the most useful notification — it's the moment where human review is needed.

Error and alert notifications

When an autonomous agent encounters an error it can't resolve, notify the team immediately. This is especially important for on-call and CI/CD agents that run without human supervision.

Cost threshold alerts

Notify when daily or session costs exceed a threshold. This prevents surprise bills and helps identify tasks that need better definition.

Integration approaches

Slack and Microsoft Teams

Use incoming webhooks to post notifications. Claude Code can be configured via hooks to send HTTP requests at key moments (session start, commit, PR creation, error). Most teams create a dedicated #claude-activity channel to keep notifications separate from human conversation.

For smaller teams or personal use, a Telegram bot provides lightweight notifications. Send session summaries and alerts to a group chat. The bot API is straightforward and works well for real-time updates.

GitHub/GitLab integration

The natural communication channel for code changes is your git platform. Claude Code already creates PRs and commits. Enhance this by:

Adding detailed PR descriptions with context about what the agent was asked to do
Using labels to distinguish AI-assisted PRs from human-authored ones
Adding session cost and token usage as PR comments

Email digests

For stakeholders who don't monitor chat channels, send daily or weekly digests summarising Claude Code activity: tasks completed, PRs created, costs incurred. Keep it brief and focused on outcomes.

What to share (and what not to)

Task descriptions and outcomes
PR links and summaries
Cost and token usage
Errors and failures that need attention

Don't share

Full session transcripts (too noisy, may contain sensitive code)
Token-by-token details (only useful for debugging)
Raw diffs (that's what the PR is for)

Building a communication skill

Create a Claude Code skill that handles notifications. The skill can:

Send a "starting work" message when invoked
Post progress updates at key milestones
Send a summary when the task completes
Alert on errors that need human intervention

This keeps notification logic reusable and consistent across all team members.

Next steps

Shared communication works best with centralised logging (the data source for notifications) and AgentOps (the governance framework). For automated incident communication, see On-Call Skills.