Appendix

CLI Reference

For the complete and up-to-date CLI reference — slash commands, keyboard shortcuts, CLI flags, MCP commands, and plugin commands — see the official Claude Code documentation.

The official docs are the authoritative source for reference material and are updated with each release.

---

Troubleshooting

For installation issues, authentication problems, MCP connection errors, permission errors, and common error messages, see the official Claude Code troubleshooting guide.

The section below covers a course-specific issue that the official docs don't address directly.

"Claude Forgot My Instructions"

This is not a bug. It's context decay. When the conversation grows long, auto-compaction may summarize away parts of your CLAUDE.md content.

Fix: Run /compact manually. Manual compaction preserves CLAUDE.md content more reliably than auto-compaction.

Prevention:

• Keep CLAUDE.md concise. Shorter files survive compaction better
• Put critical rules at the top of CLAUDE.md
• Use /clear between unrelated tasks so instructions reload fresh
• Recognize context decay symptoms early (see Module 4: Context Management)

The golden rule

When in doubt, /clear and start fresh. A clean session with a well-written CLAUDE.md will almost always outperform a long, bloated conversation.

---

Enterprise & Compliance

For detailed information on authentication, cloud providers (Amazon Bedrock, Google Vertex AI), Zero-Data-Retention (ZDR), security model, sandboxing, audit logging, and compliance certifications (SOC 2, ISO 27001), see the official Claude Code security and enterprise documentation.

The sections below cover opinionated rollout guidance that the official docs don't provide.

Recommended Enterprise Setup

A checklist for rolling out Claude Code to a development team:

1. Choose a cloud provider (Bedrock or Vertex) for data residency and compliance
2. Enable ZDR for projects involving sensitive code or data
3. Distribute API keys via secret manager. Never commit keys to repos, never share keys between developers
4. Create a team CLAUDE.md with coding standards, security rules, and approved patterns. Commit it to each repository.
5. Set up hooks for mandatory linting, formatting, and security scanning on every commit
6. Use plugins to distribute team-wide tool configurations and MCP server setups
7. Monitor usage via the admin console. Set budget alerts before costs surprise you

Start small

Roll out to a pilot team first. Let them build the CLAUDE.md and workflow conventions, then scale to the rest of the organization with proven patterns.

Regulated Industries

Industry	Key Requirements	Recommended Setup
Healthcare (HIPAA)	Data protection, audit trails	ZDR + Bedrock/Vertex + audit logging
Finance (SOC2)	Access controls, monitoring	ZDR + cloud provider + per-developer keys
Government	Data residency, security clearance	ZDR + Bedrock (GovCloud) + VPC isolation

Choosing a provider

Start with the cloud you already use. If you have no existing cloud investment and no data residency requirements, the direct API is the simplest path.