claude-code - 💡(How to fix) Fix iMessage plugin: per-project channel routing [1 comments, 2 participants]

• Manually swapping access.json between sessions — error-prone

TL;DR

Implementing per-project iMessage channel configurations, such as using a project field in access.json to map sender IDs to project directories, could resolve the issue of routing different phone numbers to different Claude Code sessions.

Guidance

• Consider modifying the access.json file to include a project field that maps sender IDs to specific project directories, allowing for context-separated communication.
• Consider using a directory structure like ~/.claude/channels/imessage/projects/<project-dir-hash>/access.json to store project-specific iMessage channel configurations.
• Evaluate the feasibility of implementing a feature that restricts Claude Code sessions to only surface messages from numbers mapped to their current working directory.
• Assess the potential impact of this feature on teams and individuals building multiple projects with complementary apps.

Example

No explicit code example is provided, as the issue focuses on proposing a solution rather than implementing a specific code change.

Notes

The proposed solution requires modifications to the existing Claude Code configuration and potentially the application itself. The feasibility and implementation details of this feature may depend on the specific requirements and constraints of the Claude Code platform.

Recommendation

Apply a workaround, such as manually managing separate access.json files for each project or using a custom script to automate the process, until a more robust per-project iMessage channel configuration feature is implemented. This recommendation is based on the potential benefits of implementing a more flexible and scalable solution for managing multiple projects with Claude Code.