Feature Request: Custom Session Name Flag

[Hooligan-Black]

Problem:

When running multiple happy instances from different machines/WSL instances that share the same Linux username, all sessions appear identically in the mobile app (e.g., all show "hooligan"). There's no way to distinguish between them.

Proposed Solution:

Add a --name flag or HAPPY_SESSION_NAME environment variable: bashhappy --name "frontend" happy --name "backend"

Or better yet, having a "rename" option next to sessions in the terminal tab

Use Case:

Running parallel Claude Code sessions on the same project from cloned WSL instances that have the same default user.

[zhigang1992]

but you should be able to "rename" your machine in the settings?

[Hooligan-Black]

but you should be able to "rename" your machine in the settings?

I have two instances of Claude Code CLI (separate accounts) running in two separate WSLs, through the same machine. So changing the machine name wouldn't help.

Also it seems by default Happy Coder names the sessions after the home folder that I have Claude Code CLI launched in (or inferred info from convo context). Both of my WSLs were once upon a time just copies of each other so they have the same home folder name and changing the names of my home folders would potentially break hardcoded paths in config files, .env, databases and so on, across many apps.

I feel like having a "rename session" button on the sessions in the "terminals" tab would be a great QoL feature either way. I'd love to organize these chat histories with titles of my own rather than having home folders or AI inferred headings.

[keithkmyers]

Yes, please!! I can't understand why this isn't the #1 requested issue. Am I doing something wrong?

My workflow seems very "vanilla": Single host, single workspace, multiple conversation threads working on different areas of the codebase. Nothing fancy.

In Happy, all the threads are named the same thing:

• /opt/workspace_project_abc
• /opt/workspace_project_abc
• /opt/workspace_project_abc
• /opt/workspace_project_abc

Just looking for a way to assign names to these sessions in the tool, or to have it respect /rename commands from Claude Code. This would be a game changer in being able to easily work on my codebase.

Right now it's a guessing game every time I want to get in there for something.
50 times a day it's:
Which one of these was the EAV refactor again?
click-scroll scroll... no, not this one.
Click.. scroll, scroll, no... not that one...
Click, scroll, okay, this is it.

[JSai23]

Yes, please!! I can't understand why this isn't the #1 requested issue. Am I doing something wrong?

My workflow seems very "vanilla": Single host, single workspace, multiple conversation threads working on different areas of the codebase. Nothing fancy.

In Happy, all the threads are named the same thing:

• /opt/workspace_project_abc
• /opt/workspace_project_abc
• /opt/workspace_project_abc
• /opt/workspace_project_abc

Just looking for a way to assign names to these sessions in the tool, or to have it respect /rename commands from Claude Code. This would be a game changer in being able to easily work on my codebase.

Right now it's a guessing game every time I want to get in there for something. 50 times a day it's: Which one of these was the EAV refactor again? click-scroll scroll... no, not this one. Click.. scroll, scroll, no... not that one... Click, scroll, okay, this is it.

Doubling down on this. Its very hard to use when there is ten sessions int he same project that I need to scroll through to figure out which one is the one I am trying to get to.

[ascott]

i opened a pr for this feature #737