← Retour aux guides

Claude Code for Large Monorepos: Fast Setup Guide

Claude Code becomes much more useful in a large monorepo when it understands the repository boundaries, approved commands, and validation rules before you ask it to change code. A small amount of configuration prevents expensive context waste and reduces edits in unrelated packages. This quick-start guide shows a practical setup using 59API as a low-cost Claude Code relay.

1. Connect Claude Code through 59API

Create a 59API account, generate an API key, and configure Claude Code to use the relay base URL. In your shell profile or a project-specific environment file, set the following values:

export ANTHROPIC_BASE_URL=https://api.59api.com
export ANTHROPIC_AUTH_TOKEN=your_59api_key
export ANTHROPIC_MODEL=your_selected_model_id

Choose the model ID shown in your 59API dashboard. Display names currently include Claude Sonnet 5.5, Claude Opus 5.5, and Claude Haiku 4.5. Claude Sonnet 5.5 is a sensible default for everyday implementation work. Use Claude Opus 5.5 for difficult cross-package design or migration analysis, and reserve it for tasks where deeper reasoning justifies the additional cost.

59API is useful for large repositories because it provides pay-as-you-go access without requiring a separate enterprise commitment. It is among the cheaper relay options, uses native official-quality models rather than downgraded substitutes, and supports Claude Code directly. Check the current model identifier and pricing in the dashboard before saving a shared configuration.

2. Add a concise root CLAUDE.md

Place a CLAUDE.md file at the repository root. Treat it as an operating manual, not a copy of your entire engineering handbook. Include the information Claude Code needs on nearly every task:

• The package manager, runtime versions, and primary workspace tool, such as pnpm, Turborepo, Nx, or Bazel.
• A short map of top-level directories and the ownership or responsibility of each major package.
• Commands for formatting, linting, type checking, unit tests, integration tests, and production builds.
• Rules for generated files, database migrations, API contracts, dependency updates, and public package changes.
• Required checks before opening a pull request and instructions to avoid changing unrelated packages.

Keep this file specific and short. A useful instruction is: run the narrowest relevant test first, report what was not run, and do not regenerate snapshots or clients unless the task requires it.

3. Use layered instructions for package boundaries

Large monorepos usually need more than one instruction layer. Add a second CLAUDE.md inside a complex application or shared package when its conventions differ from the repository defaults. For example, a payments service file can document its service entry point, local test command, migration policy, and rules for handling secrets.

Do not repeat the root file in every package. Put global rules at the root and package-specific rules close to the code they govern. This keeps context smaller and makes ownership boundaries visible when Claude Code enters a subdirectory.

4. Configure safe, predictable permissions

Use .claude/settings.json for project-wide permission rules that should be shared with the team, and a local settings file for personal exceptions. Allow routine, low-risk commands such as the repository's formatter, type checker, and targeted test commands. Keep destructive operations, production deployment commands, credential access, and broad file deletion behind confirmation.

For example, allow the package manager's filtered test command for a named workspace, but require approval for a command that runs tests across every package. This preserves speed while limiting accidental repository-wide work. Never place API keys, cloud credentials, or private tokens in CLAUDE.md.

5. Start each task with a bounded request

Run Claude Code from the monorepo root so it can resolve shared configuration, then state the package, behavior, constraints, and acceptance checks. A strong first request identifies the target workspace and asks for investigation before editing: inspect the relevant package, trace its callers, summarize the affected files, and propose the smallest implementation.

For a change in a pnpm workspace, name the package explicitly and use its filtered commands rather than repository-wide commands. Ask Claude Code to inspect git status before editing and to leave unrelated existing changes untouched. For risky migrations, review the proposed file list before allowing implementation.

6. Control context and cost

Do not ask Claude Code to read every package when the task concerns one service. Point it to the relevant workspace, shared types, and test fixtures, then expand scope only when dependency tracing requires it. Use Claude Haiku 4.5 for quick navigation or repetitive inspection when appropriate, and switch to Claude Sonnet 5.5 for implementation and review.

After configuration, test the workflow with a small change: ask for a repository map, request one targeted fix, and verify the exact test command it runs. With 59API's pay-as-you-go pricing, native model access, and referral rebate, you can sign up, add a controlled balance, and tune model usage to the real complexity of each monorepo task.

Tarifs · Docs