Repository navigation
[bug] Session list fills with unreadable timestamps when no title model is configured #20501
Closed as not planned
Description
Describe the bug
Without a dedicated title model configured under agent.title.model, sessions are named with raw ISO timestamps (e.g. "New Session 2026-01-01T12:00:00.000Z"), making the session list completely unusable — you can't tell what any conversation was about at a glance.
When small_model is configured as a fallback, the LLM does generate a title, but the result is often too abstract and doesn't accurately reflect the actual conversation content.
To Reproduce
- Use opencode without configuring agent.title.model
- Start several new sessions
- Observe the session list — all entries show ISO timestamp titles
Expected behavior
When no dedicated title model is configured, derive the session title directly from the first line of the user's first message. This is instant, costs no tokens, and always produces an accurate and recognizable title.
Environment
- opencode version: latest
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Apr 1, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:), or Question. Based on the content, this appears to be a feature request or bug report — please pick the appropriate template and fill in all required fields.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
small_modelis invalid #14807: Session auto-naming silently fails whensmall_modelis invalid — describes sessions keeping default timestamp-based titles when title model configuration is brokenIf you believe this was flagged incorrectly, please let a maintainer know.
[-]Session titles default to timestamps instead of conversation content when no title model is configured[/-][+][bug] Session list fills with unreadable timestamps when no title model is configured[/+]github-actions commentedon Apr 1, 2026
Thanks for updating the issue! It now follows the contributing guidelines and has been marked as compliant.
harvzor commentedon Apr 16, 2026
This suddenly became a problem for me today:
I also checked with a coworker and they also just started experiencing this problem. I'm on 1.4.6 and tested a couple of patch versions back. My coworker is on 1.2.* and they have the same issue.
github-actions commentedon Jul 6, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.