Add per-machine session name suffix for Remote Control identification

Problem

When using Remote Control from the mobile app to manage sessions across multiple machines, there's no way to tell which machine a session is running on. The session list shows topic names but no machine identifier.

Current Workarounds (all inadequate)

1. --name flag — Sets a static name at startup before any topic exists, replacing the auto-generated topic entirely
2. /rename command — Works but requires manual intervention every session
3. Editing local ~/.claude/sessions/*.json — Does not propagate to the mobile app / Remote Control list
4. SessionStart hook — Can edit local files but same propagation issue; also fires before any topic is generated

Proposed Solution

A setting (e.g., in settings.json) that appends a configurable suffix to the session name as displayed in Remote Control:

{
  "sessionNameSuffix": "Jon's Macbook"
}

This would make sessions appear as:

• Fix auth bug - Jon's Macbook
• Add payment flow - Jon's Macbook

Instead of just:

• Fix auth bug
• Add payment flow

The suffix would be appended automatically to whatever name is generated (auto-topic, --name, or /rename), and would sync to the mobile app's Remote Control list.

Alternatives Considered

• A hook-based approach using SessionStart to edit local session files — doesn't sync to mobile
• Always starting with claude -n "Machine Name" — loses the auto-generated topic
• Manual /rename every session — tedious and easy to forget

🤖 Generated with Claude Code