Sessions and changes
A session keeps one task’s conversation, file changes and command output together. Start a new session for a separate task; reopen an existing one to continue it.
Give the task a clear start
Open the project, choose New session, and describe the result you want. Name important files or constraints and say whether Glixo should inspect first or make changes. For example:
Find why the search page shows no results for a valid query. Explain the cause before editing.
Check the selected provider, model and permission mode in the composer, then send the message.
Follow the work
Read the reply and any questions or approval requests. For a task you want Glixo to keep working toward, start the message with /goal and describe the result. The session shows the goal and updates its checklist as work progresses.

Inspect commands and edits
Open the session’s Terminal to see a command’s output. Use Diff to review changed lines and open a file when you need more context. Ask for a correction if the result misses a requirement. You can also ask Glixo to run a relevant test and read its output.


At the end, review the final response, changed files and test output that matters to your task.
Open files in tabs
In builds with file tabs, opening a file from Files or Diff adds a tab beside the session tab. Select a tab to switch between files and return to the conversation through the session tab. Close a file tab with its close button.
Markdown files offer Preview and Edit. A file opened as a diff shows its changes rather than the ordinary file view; the same file can have a separate file tab and diff tab. Save or discard unsaved edits when prompted before closing or leaving the file.

Resume a session
Open the session again from the project in the sidebar to continue the same task. Its conversation and changes stay together.