-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
π§ Summary
During AIDD installation, when CLAUDE.md already exists as a regular file (not a symlink), the installer fails to replace it with the AIDD symlink despite user confirmation.
π Objective / Problem
When installing AIDD in a project that already has a CLAUDE.md file:
- Installer prompts "Replace with AIDD symlink? Yes - replace"
- User confirms replacement
- Warning appears: "Target exists and is not a directory or symlink"
- The symlink is NOT created, leaving the original file in place
Expected: The installer should backup/remove the existing file and create the symlink.
π οΈ Proposed Solution
Options to consider:
- Backup & Replace: Rename existing
CLAUDE.mdβCLAUDE.md.backupbefore creating symlink - Force removal: Delete existing file when user confirms replacement
- Merge strategy: Append existing content to AIDD template (for memory-bank generation)
π«‘ Acceptance Criteria (Gherkin format)
Scenario: Replace existing CLAUDE.md with symlink
Given a project with existing CLAUDE.md file (not a symlink)
When user runs AIDD installation
And user selects "Yes - replace" for CLAUDE.md
Then the existing CLAUDE.md should be backed up or removed
And a symlink to AIDD CLAUDE.md should be created
And installation should complete without warningsπ Context / Technical Constraints
- macOS Darwin 25.1.0
- AIDD CLI via
npx aidd .claude/agentssymlink worked correctly- Only
CLAUDE.mdsymlink failed
π Attachments / References
Installation output:
β Dependencies installed successfully
? Target already exists at .../CLAUDE.md. Replace with AIDD symlink? Yes - replace
β Target exists and is not a directory or symlink: .../CLAUDE.md
β Installation completed with warnings
π· Screenshot available - will be added in comments
Metadata
Metadata
Assignees
Labels
No labels