Skip to main content
A session is a persistent conversation thread with the Luminy agent. Every message you send, every file the agent reads, every tool call it makes, and every result it returns are stored locally and remain available the next time you open the app. Sessions are the primary unit of work in Luminy — each one captures a complete line of reasoning around a task.

​
Creating a session

Click the New Chat button at the top of the sidebar to open a fresh session. You can start typing immediately; you don’t need to configure anything before sending your first message. Sessions can be project-scoped or global:

Project session

Tied to a specific project. The agent has access to the project’s repo map, can read and write files, and uses the indexed codebase as context. Select a project from the project selector in the chat input before or after creating the session.

Global session

Not tied to any project. Useful for general coding questions, learning, or tasks that don’t require file access. The agent operates without a codebase context.

​
Auto-generated titles

Luminy automatically generates a title for each session based on your first message. You’ll see the title appear in the sidebar shortly after you send your opening prompt. You don’t need to name sessions manually, though you can rename them by clicking the title in the sidebar.

​
The session list

All your sessions are listed in the left sidebar, sorted by most recent activity. Switching between sessions is instant — Luminy loads the full message history from local storage and restores the exact state of the conversation, including any tool results and in-progress todo items.

​
Forking a session

Forking creates a point-in-time copy of a session from any completed assistant message. The fork preserves the entire message history up to that point, all tool call results, and the current todo state. From that point forward, the fork is an independent session — changes in one branch do not affect the other. When to fork:
  • You want to try a different approach without losing the current one
  • The agent just produced a good checkpoint and you want a safe fallback before continuing
  • You’re exploring two architectural directions in parallel
How to fork:
1

Find the message

Scroll to any completed assistant message in the conversation. Hover over the message to reveal the metadata row beneath it.
2

Click the fork icon

Click the fork icon (a small branching line icon) in the metadata row. Luminy creates a new session forked at that message.
3

Continue in the fork

The forked session opens automatically in the sidebar. It starts from the exact state of the original conversation at that message.
Forking is especially useful before asking the agent to make a large change. Fork first, let the agent make the change, and if you don’t like the result you can always switch back to the original branch.

​
Context window

As a conversation grows, it consumes more of the model’s context window. Luminy tracks context occupancy and shows a progress bar at the top of the chat when the window is getting full. When you see this indicator, consider starting a new session or using context compaction to continue working without hitting the limit. See Context Compaction for details on how to manage context usage.

​
Session storage

All session data — messages, tool results, token counts, and todo state — is stored locally on your machine. Nothing is uploaded to any server.

​
Deleting sessions

To delete a session, right-click it in the sidebar and select Delete. Deletion is permanent and removes all messages and associated data for that session from local storage.
Deleting a session does not affect any files the agent edited during that session. File changes made by the agent are written directly to your filesystem and persist independently.