Conversation management
A conversation is a focused working context, not a permanent dumping ground for every task.
Start a new conversation
Create a new chat when the objective changes significantly, when the current conversation has accumulated unrelated context, or when you want a clean comparison between models or approaches.
Keep one goal per conversation
A conversation can contain multiple turns, but the work should stay coherent. If a discussion moves from debugging authentication to planning a marketing campaign, split the tasks.
Rename conversations
Use a short descriptive title that reflects the actual goal. Good titles make search and project organization easier later.
Examples:
Fix admin timeline TypeScript errorBilling 4.0 reconciliation designFORGE artifact retention plan
Avoid vague names such as Help, New chat, or Stuff for important work.
Move durable work into Projects
If several conversations belong to the same product, research effort, or long-running initiative, use a Project so those chats can share durable project context.
Branching and comparison
When Starfire exposes branch/regeneration controls, use them to compare alternate responses without losing the original reasoning path.
If branching is not available in the current Alpha build, start a new conversation and copy only the necessary context.
Deleting conversations
Before deleting a conversation, check whether it contains the only copy of an important decision, source, or generated output. Durable project decisions belong in Projects or Knowledge rather than depending on one chat history.
Context hygiene
Remove accidental secrets from future workflows by rotating/revoking the secret—not by assuming deletion of one visible message is sufficient to make the credential safe.
Use conversations for working context and Projects/Knowledge for durable context. That separation keeps model inputs cleaner and project history easier to manage.
