Editors & Contributors

How the editorial team is structured

The reference is maintained by four core editors, each responsible for a defined section of the hub. That division of responsibility exists for a practical reason: the install guides, the model reference, the skills and teams content, and the safety documentation each move on different timescales and require different subject-matter backgrounds to verify correctly. One editor who covers everything either cannot keep up or spreads their verification work too thin to catch the kind of subtle breakage — a flag name that changed, a minimum version that moved — that makes an install guide quietly wrong without looking it.

The team communicates through a shared editorial channel and reviews each other's changes before they go live for any substantive update. Minor corrections — a typo, a broken link — can be pushed by the responsible editor directly. Anything that changes an instruction, a code snippet, or a claim about model behaviour goes through a second pair of eyes. This process is slower than publishing immediately, but it is the reason the guides here tend to match what the terminal actually does.

Core editorial team

Marta D. Hoffstedt — Lead Editor, Installation and CLI Reference

Marta covers the install guides, CLI flag reference, and platform-specific walkthroughs for Windows, macOS, and Linux. Her background is in developer experience engineering; she spent six years writing and maintaining internal developer toolchain documentation for a mid-sized software company before joining the editorial team. She runs the documented install commands in a clean environment monthly and after any CLI release that touches the install path. She is also the editor responsible for the proxy and certificate trust-store sections, which she added after noticing how many correction reports arrived from corporate users hitting exactly that problem.

Callum R. Ashford — Editor, Models and API Reference

Callum owns the model comparison tables, API reference, and pricing notes. He has a background in applied machine learning and previously maintained API documentation for a developer tools startup. Pricing and context window data changes with each release, so Callum's review cycle runs monthly and is triggered immediately by any public vendor announcement about limits or pricing. He is the editor most likely to add a note when a structural model difference — extended thinking support, caching behaviour — changes in a way that affects how developers should pick between options.

Priscilla N. Okafor — Editor, Skills, Teams, and Enterprise Reference

Priscilla covers the skills system, team configuration, and enterprise reference pages. Her background is in platform engineering and internal tooling; she has run developer platforms for teams ranging from ten engineers to several hundred. She is primarily responsible for keeping the skills and teams documentation aligned with the current CLI version and for the enterprise audit-log and SSO configuration notes. She added the section on bounding agent autonomy in regulated industries after fielding questions from readers in healthcare and financial services who needed to explain the permission model to their compliance teams.

Theodore J. Walmsley — Editor, Trust, Safety, and Editorial Policy

Theodore covers the trust and safety reference, the about page, and the editorial policy documentation. His background is in technical writing and information security, with previous experience documenting security configurations for enterprise software. He reviews the safety-adjacent pages quarterly and coordinates the correction triage process for the hub — when a correction arrives, Theodore routes it to the right editor and tracks it through to resolution. He is also the editor responsible for the .claudeignore guidance, which he drafted after researching the credential-leakage patterns that show up most frequently in developer AI tool incident reports.

Editor	Coverage area	Review window
Marta D. Hoffstedt	Installation, CLI reference, platform walkthroughs	Monthly + on CLI release
Callum R. Ashford	Models overview, API reference, pricing notes	Monthly + on vendor announcement
Priscilla N. Okafor	Skills, teams configuration, enterprise reference	Bi-monthly + on CLI release
Theodore J. Walmsley	Trust and safety, about, editorial policy	Quarterly + on policy change

Editorial standards

Every instruction in this reference is verified in a live environment before it is published. Where the team cannot run a verification — for example, an enterprise SSO configuration that requires a specific identity provider setup — they note that limitation inline and link to the vendor's own documentation rather than paraphrase instructions they cannot independently confirm. Claims about model behaviour are sourced from public vendor documentation or academic research; when the two conflict, the editors note the discrepancy and use the more conservative claim. For AI safety and governance framing, the team references NIST AI RMF and MIT CSAIL research where relevant.

No advertiser or sponsor has editorial input. The editors are not compensated by Anthropic or any AI vendor. When an editor disagrees with a proposed correction from a reader, they explain why in their reply and include the source they used — the goal is a transparent editorial process, not an opaque one. Readers who want to contribute corrections, additions, or topic suggestions can do so through the contact page.