Manage Nour sessions
Every chat is kept per repository in Chat history. Stop ends the current reply; Nour also stops an agent that prints nothing for too long. If the chosen agent cannot answer (not signed in, no usage left, missing model), another installed agent may answer instead and Nour says why.
Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.
On this page
Before you start
- GitTree Pro or a running trial: Nour is part of Pro.
Where to find it
- The Nour header: New chat, History, Where the chat shows; Stop in the message box.
| Action | macOS | Windows and Linux |
|---|---|---|
| Open or close Nour | ⌘⇧Space | Ctrl+Shift+Space |
Steps
Stop a reply
Press Stop while Nour answers. The turn shows Stopped; changes it already made can be undone with Undo this turn.
Start fresh or go back
Press New chat for a clean conversation, or History to reopen one: This scope, With … or All.
Move the chat
Under Where the chat shows, choose Docked beside the Inspector, Floating panel or Its own window.
Expected result
You control when Nour answers and can return to any earlier chat.
When an agent cannot answer
- Nour says, for example, “… is not signed in, so … answered instead.”
- Reasons include no usage left, a missing model, a missing Node.js, an outdated agent or an empty answer.
- “No output from … for … seconds. Nour stopped it.” means the agent went quiet; ask again or test it in Nour settings.
If something goes wrong
“Nour is already replying in this chat, perhaps in another window.”
Wait for that reply or stop it there; a chat answers one message at a time.
Questions
What happens to a chat when I close the repository tab?
It stays in History. Actions that need the repository’s tab do not run until you open it again.