fix(auth): resolve require is not defined error in profile manager

[sehoon787]

Base Branch

• This PR targets the develop branch (required for all feature/fix PRs)
• This PR targets main (hotfix only - maintainers)

Description

Fixes the "require is not defined" error that occurs when re-authenticating Claude profiles in Settings > Integrations > Claude Accounts. The error also affects Claude Code installation from the Home screen.

Related Issue

Closes #1378

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 📚 Documentation
• ♻️ Refactor
• 🧪 Test

Area

• Frontend
• Backend
• Fullstack

Checklist

• I've synced with develop branch
• I've tested my changes locally
• I've followed the code principles (SOLID, DRY, KISS)
• My PR is small and focused (< 400 lines ideally)

Platform Testing Checklist

• Windows tested (tested locally - built and verified exe works)
• macOS tested (CI will test)
• Linux tested (CI will test)
• Used centralized platform/ module instead of direct process.platform checks
• No hardcoded paths (used findExecutable() or platform abstractions)

CI/Testing Requirements

• All CI checks pass on all platforms (Windows, macOS, Linux)
• All existing tests pass
• New features include test coverage
• Bug fixes include regression tests

Root Cause

The file claude-profile-manager.ts uses ES module syntax but had an inline require('os').homedir() call in getActiveProfileEnv() (line 383-385):

const expandedConfigDir = profile.configDir.startsWith('~')
  ? profile.configDir.replace(/^~/, require('os').homedir())
  : profile.configDir;

This fails because require is not defined in ES module context, causing:

• "Authentication Failed require is not defined" when re-authenticating profiles
• "Failed to open terminal for installation: require is not defined" when installing Claude Code

Solution

Replace inline require('os').homedir() with the already-imported expandHomePath() utility function (imported from ./claude-profile/profile-utils on line 51):

const expandedConfigDir = expandHomePath(profile.configDir);

This is a minimal 1-line change that uses existing infrastructure.

Feature Toggle

• N/A - Feature is complete and ready for all users

Breaking Changes

Breaking: No

---

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.5 noreply@anthropic.com

Summary by CodeRabbit

• Refactor
  • Improved internal code organization for path expansion logic in the profile manager.

Note: This update contains no user-visible changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[CLAassistant]

All committers have signed the CLA.

[github-actions]

🎉 Thanks for your first PR!

A maintainer will review it soon. Please make sure:

• Your branch is synced with develop
• CI checks pass
• You've followed our contribution guide

Welcome to the Auto Claude community!

[coderabbitai]

📝 Walkthrough

Walkthrough

A refactoring that replaces manual ~ expansion using os.homedir() with a centralized expandHomePath() helper function for profile configuration directory paths, maintaining identical functionality while improving code maintainability.

Changes

Cohort / File(s)	Summary
Path expansion centralization apps/frontend/src/main/claude-profile-manager.ts	Refactored to delegate home directory path expansion to a centralized helper function instead of inline os.homedir() usage

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

bug, area/frontend, size/XS

Suggested reviewers

• AndyMik90

Poem

🐰 A path once tangled, now so clean,
With helpers true, we've intervened,
From home to config, the journey's bright,
Centralized expansion—everything's right! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the fix: replacing an inline require() call with a utility function to resolve the 'require is not defined' error in the profile manager.
Linked Issues check	✅ Passed	The PR directly addresses issue #1378 by eliminating the inline require('os').homedir() call in ESM context and replacing it with the expandHomePath() utility, resolving the CommonJS vs ES Modules incompatibility.
Out of Scope Changes check	✅ Passed	The change is narrowly scoped to fix the specific issue: refactoring one require() call to use an existing utility function with no other alterations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[gemini-code-assist]

Summary of Changes

Hello @sehoon787, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical bug where the application failed to re-authenticate Claude profiles and install Claude Code due to a 'require is not defined' error. The fix involves a targeted code modification to ensure compatibility with the existing ES module environment, thereby restoring essential functionality for users.

Highlights

• Fix 'require is not defined' error: Resolved an error preventing Claude profile re-authentication and Claude Code installation by replacing an inline require('os').homedir() call with the expandHomePath() utility function in claude-profile-manager.ts. This addresses the incompatibility between CommonJS require and ES module context.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request provides a clean and effective fix for a critical runtime error. The use of an inline require() in an ES module was causing a 'require is not defined' error, and replacing it with the existing expandHomePath utility function is the correct solution. The change is minimal, well-documented in the pull request description, and resolves the issue without introducing any new concerns. The code quality is excellent, and no further changes are needed.