fix Claude Code install guidance#1697
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (3)
📝 WalkthroughWalkthroughReplaces npm-install guidance for the Claude Code CLI with a link to Anthropic’s official setup docs across docs and runtime messages; centralizes the setup URL constant and updates/adds integration tests to assert the revised messaging. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🦋 Changeset detectedLatest commit: 1f29246 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@tests/integration/claude-code-error-handling.test.js`:
- Around line 34-35: The test currently asserts on the full, exact error text
(including the full URL) which is brittle; update the assertions in
tests/integration/claude-code-error-handling.test.js so they check for stable
semantics instead: replace the exact full-string match with looser checks such
as expect(error.message).toMatch(/Claude Code CLI not available/i) and a
separate assertion that the message contains the docs domain or path fragment
(e.g., expect(error.message).toContain('docs.anthropic.com') or
expect(error.message).toMatch(/getting-started/i)); update both assertions that
reference the exact phrase/URL so they verify intent and guidance presence
rather than the full literal text.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 10945f61-6273-43ea-bb1d-135fd610ae21
📒 Files selected for processing (6)
.changeset/rare-badgers-ring.mddocs/examples/claude-code-usage.mdpackages/tm-core/src/modules/loop/services/loop.service.tspackages/tm-core/tests/integration/loop/loop-service-error-messages.test.tssrc/ai-providers/claude-code.jstests/integration/claude-code-error-handling.test.js
d4c4b67 to
1f29246
Compare
|
I force-pushed this PR after the base was changed to The branch originally contained I also kept a backup of the previous branch state in |
Summary
This PR updates Claude Code install guidance to point users to Anthropic's official setup docs instead of hard-coding a single install path.
What Changed
Why
The current guidance was inconsistent across the codebase and could go stale as Claude Code installation flows evolve. Pointing users to the official setup guide is more durable and avoids steering them to a single installation path.
Validation
npm run format-checknpm test -- tests/integration/claude-code-error-handling.test.js tests/unit/ai-providers/claude-code.test.js../../node_modules/.bin/vitest run --config vitest.config.ts --coverage.enabled=false tests/integration/loop/loop-service-error-messages.test.tsfrompackages/tm-corenpm run build./node_modules/.bin/cross-env NODE_ENV=test node --experimental-vm-modules node_modules/.bin/jest tests/integration/cli/complex-cross-tag-scenarios.test.js --runInBandNotes
I also ran the repository-wide
npm test, but there are unrelated pre-existing Jest ESM teardown failures in profile-related suites.Closes #1634
Summary by CodeRabbit
Documentation
Bug Fixes
Tests