Repository navigation
Replies: 2 comments 1 reply
|
@lvaizer Thanks for raising this! The reason Vibeyard doesn't auto-name sessions is that generating a summary would consume your tokens - I didn't want to quietly spend your Claude budget on something you didn't ask for. That said, you already get auto-naming for free in one case: when Claude Code itself renames a session (which currently happens when you transition from Plan to Implement mode), Vibeyard picks that up and updates the session name accordingly. If you'd like to opt in to token-consuming summarization as a preference, let me know and I can consider adding it as an optional setting. |
|
Update @lvaizer — this is built and lands in the next release. Correcting my earlier answer: Claude Code now exposes its session name directly in the status line payload, which it didn't back then. So Vibeyard just reads the title Claude already generated — no summarization, no tokens spent. Sessions are named by topic, and that name carries into History when you close them. On by default, with a toggle in Preferences → General. |
Uh oh!
There was an error while loading. Please reload this page.
When the user closed the session it save under "history" with the session name.
The default name is "session #" which is hard to understand what was the context at that session.
My idea is when i closed the session, the saved session name at the history will be saved with the name of short summary of the session, kind of like ChetGPT/Gemini etc..
All reactions