anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Feature Request: Editable session names with auto-generated titles #5743

New Issue
Closed
opened 2026-02-16 17:56:19 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:56:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @openAgi2 on GitHub (Jan 14, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

Currently, sessions are named with a timestamp format like new session-2026-01-14-17:32. When users want to revisit previous conversations, this naming convention makes it difficult to identify specific sessions without opening each one to review its content.

In contrast, products like ChatGPT and Gemini automatically generate descriptive titles based on the conversation content (e.g., "React Hook Performance Optimization" or "Docker Compose Setup Guide"), making session history much more navigable.

Proposed Solution

Minimum Viable Feature

  • Editable session names: Allow users to manually rename sessions

Enhanced Feature (Recommended)

  • Auto-generated titles: After the user sends their first message, use the LLM to generate a concise 5-10 word title that summarizes the conversation topic
  • Title regeneration: Option to regenerate the title at any point during the session

Implementation Suggestions

User sends first message →
  LLM generates short descriptive title →
  Session is renamed automatically

The title generation could be a simple prompt like:

"Generate a concise 5-10 word title for a coding session that starts with: {first_message}"

Benefits

  • Faster navigation through session history
  • Better context at a glance
  • Improved user experience, especially for power users with many sessions
  • Feature parity with mainstream AI chat products

Additional Context

This is a common UX pattern in AI chat applications. The auto-naming significantly reduces cognitive load when managing multiple sessions.

Originally created by @openAgi2 on GitHub (Jan 14, 2026). Originally assigned to: @thdxr on GitHub. ## Problem Currently, sessions are named with a timestamp format like `new session-2026-01-14-17:32`. When users want to revisit previous conversations, this naming convention makes it difficult to identify specific sessions without opening each one to review its content. In contrast, products like ChatGPT and Gemini automatically generate descriptive titles based on the conversation content (e.g., "React Hook Performance Optimization" or "Docker Compose Setup Guide"), making session history much more navigable. ## Proposed Solution ### Minimum Viable Feature - **Editable session names**: Allow users to manually rename sessions ### Enhanced Feature (Recommended) - **Auto-generated titles**: After the user sends their first message, use the LLM to generate a concise 5-10 word title that summarizes the conversation topic - **Title regeneration**: Option to regenerate the title at any point during the session ## Implementation Suggestions ``` User sends first message → LLM generates short descriptive title → Session is renamed automatically ``` The title generation could be a simple prompt like: > "Generate a concise 5-10 word title for a coding session that starts with: {first_message}" ## Benefits - Faster navigation through session history - Better context at a glance - Improved user experience, especially for power users with many sessions - Feature parity with mainstream AI chat products ## Additional Context This is a common UX pattern in AI chat applications. The auto-naming significantly reduces cognitive load when managing multiple sessions.
yindo closed this issue 2026-02-16 17:56:19 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#5743
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?