Communications kit - Claude Code Docs
Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. This page is for administrators and engineering leads rolling Claude Code out to a team. It provides copy-ready launch announcements, a tips-and-tricks drip campaign, and one-line FAQ responses for the questions you will be asked most.
Treat everything here as draft copy, not finished copy. Rewrite each message in your organization’s voice, swap the example tasks for real bugs and modules from your own codebase, and replace the [bracketed placeholders] before sending. The announcements that drive adoption are the ones that read like someone at your company wrote them. Launch communications One announcement in two formats, plus two optional variants.
Pick whichever fits your rollout and rewrite it from there. Before you send Work through this checklist before the announcement goes out. Each item closes a gap that otherwise turns into a launch-day support thread. Item Why it matters #claude-code channel created and linked in the message Gives questions one place to land Install command tested on at least one machine in your environment Catches proxy or firewall issues before everyone hits them at once Security and data-handling link ready ( Data usage or your internal equivalent) “Where does my code go?” will be the first reply One concrete first task chosen, a real bug or file in your codebase Generic examples don’t convert; “fix the flaky test in auth_test.go ” does A named owner for the channel for the first 48 hours Unanswered launch-day questions kill momentum A C-suite sponsor lined up to send or co-sign the announcement Exec-sent launches consistently see higher first-week adoption than admin-sent ones The announcement Use this as your standard org-wide rollout message.
It covers what Claude Code is, gives a two-minute install path, hands readers one concrete task to try, and answers “where does my code go?” before anyone has to ask. Email Slack or Teams Subject: Claude Code is live for [Engineering / your team] Team, As of today you have access to Claude Code, an AI coding agent that runs in your terminal, reads your actual codebase, and works through real tasks end to end: debugging, refactors, tests, PRs.
It is not autocomplete and it is not a chat window. It edits files and runs your commands. Get running in two minutes: curl -fsSL https://claude.ai/install.sh | bash cd <your-repo> claude Then run /init once. Claude reads your project and writes a CLAUDE.md with your build commands and conventions, so you stop re-explaining the basics. Then try one of these on the repo you are already in: - "The test in [file] is flaky.
Figure out why and fix it" - "Walk me through how [module] handles [X]" - "Look at my working diff and tell me what's risky before I push" Where your code goes: Claude Code runs in your terminal and talks directly to Anthropic's API. On our Team or Enterprise plan, Anthropic does not use your code or prompts to train its models. Details: https://code.claude.com/docs/en/data-usage https://code.claude.com/docs/en/security Where to go with questions: #claude-code. [Owner name] is watching it this week. - [Name] P.S.
Prefer your editor? There is a VS Code extension and a JetBrains plugin. Same agent, no terminal required. 🚀 *Claude Code is live for [ team ]* AI coding agent, runs in your terminal, reads your repo, does real work: bugs, refactors, tests, PRs. `curl -fsSL https://claude.ai/install.sh | bash` → `cd your-repo` → `claude` *First thing to try* → run `/init` , then: "the test in [ file ] is flaky, figure out why and fix it." 🔒 Runs in your terminal, talks directly to Anthropic's API.
On our Team or Enterprise plan, your code and prompts are not used to train models. Data usage → https://code.claude.com/docs/en/data-usage 📚 Quickstart · VS Code · Free 1-hr course https://code.claude.com/docs/en/quickstart https://code.claude.com/docs/en/vs-code https://academy.claude.com/courses/claude-code-in-action Questions → this thread. [ Owner ] is on point. Executive sponsor variant Send this from your sponsoring executive, such as the CTO, CIO, or SVP Engineering, under their name and from their account.
Launches that go out under an exec’s name consistently see higher open rates and faster first-week activation than the same message from an admin or tooling team. It signals a company priority rather than an optional experiment. This version is deliberately stripped to one ask: install it and run it on one real task. The exec’s job is to make the ask land; the standard announcement and #claude-code handle the how.
Email Slack or Teams Subject: One thing I'd like every engineer to try this week Team, We have turned on Claude Code for all of engineering. It is an AI agent that works directly in your terminal, on your actual codebase, and the early results from teams already using it are strong enough that I want everyone on it this week. I am asking for ten minutes: curl -fsSL https://claude.ai/install.sh | bash cd <your-repo> claude Then hand it one real task: the bug you have been putting off, or "walk me through how [module] works." That is the whole ask. [Owner name] and team are in #claude-code for anything you hit along the way. - [Exec Name] [Title] 📣 *From [Exec Name]: one thing to try this week* We have turned on *Claude Code* for all of engineering.
Early results are strong enough that I am asking everyone to give it ten minutes on real work this week. `curl -fsSL https://claude.ai/install.sh | bash` → `cd your-repo` → `claude` → hand it one real task. That's it. Questions → #claude-code. Pilot group variant Use for a phased rollout. Send to the pilot cohort only. Subject: You're in the Claude Code pilot [Name / team], You are in the first wave of Claude Code at [company].
We picked this group because you will put it on real problems and tell us the truth about it. The ask: use it on at least one real task this week, then drop a note in #claude-code-pilot covering what worked, what was annoying, and what surprised you. That feedback decides how we roll it out to everyone else. [Continue with "Get running in two minutes" from the standard announcement] One extra thing for pilots: on your first multi-file change, press Shift+Tab until you see "plan".
Claude will lay out what it intends to do without editing your source. It is the fastest way to calibrate how much to trust it. Champion recruitment DM After launch, DM the two or three people who are most active in #claude-code . Hey [name], your #claude-code posts are doing more for adoption than my announcement did. A couple of people told me your [thread / screenshot] was why they actually tried it. Want to make that semi-official?
Low lift: mostly keep posting what you are posting, plus first crack at new features and a direct line to the Anthropic team. I can share a short playbook if you're in. Tips and tricks campaign Ready-to-paste Slack or Teams messages designed to drive feature activation after launch. Each follows the same pattern: a hook, the payoff, a “try it now” prompt, and a docs link. Drip them one or two a week in #claude-code , or pick the handful that match your team’s gaps.
They stand alone with no required order. Get started Choosing the right model 🎯 *Tip: Match the model to the moment* Using Opus to fix a typo burns compute. Using Haiku for a 12-file refactor is asking for a re-do. Claude Code runs on the same models as the Claude app, and you can switch mid-session. *Sonnet* is the workhorse default for everyday feature work, bugs, tests, and reviews. Reach for *Opus* on large refactors, gnarly debugging, or anything high-stakes.
Drop to *Haiku* for quick questions, formatting, and mechanical edits where speed wins. *Fable* is the most capable model for
The rest of this page is on the live site.