Claude Code

A markdown file in your project that Claude Code reads at the start of every session — the place for coding standards, architecture decisions and review checklists.

Shell commands that run automatically before or after Claude Code actions — formatting after an edit, linting before a commit, blocking a tool call outright.

The rules controlling what Claude Code may do without asking — which tools it can call, which commands it can run, and which paths it can touch.

Where Claude Code stores configuration — the layered settings files, the .claude directory, and the environment variables that override both.

A unit of Claude Code work with its own context and history, which can be resumed, moved between surfaces, and run in parallel with others.

How Claude Code fills, compacts and caches the context window, and why long sessions behave differently from short ones.

Three different ways to run Claude Code on a schedule — cloud routines, desktop scheduled tasks, and in-session looping — with different trade-offs.

Running Claude Code in a browser or the Claude mobile app, with no local setup — for long-running tasks, repos you do not have locally, and work in parallel.

Running Claude Code inside your pipeline to review pull requests, triage issues and automate repetitive repository work.

A screen for running and watching several Claude Code sessions at once, so long tasks proceed while you work on something else.

The reporting surfaces for Claude Code — per-user analytics, cost management and OpenTelemetry monitoring — used mainly by organisations rolling it out.

Git worktrees give each parallel Claude Code session its own checkout, which is what stops two agents editing the same files from fighting.