Nibtree v0.1.0-beta.16

Added

• Move the activity bar icons: right-click an icon for Move to Left Top, Left Bottom, Right Top or Right Bottom, or drag it to a new place on either bar. A panel goes with its icon, so Changes can open on the right and the file tree on the left. Reset Positions puts everything back, and the places are remembered.
• Nibtree for Linux (x64): an .AppImage that runs on any distribution and a .deb for Ubuntu and Debian. A GitHub token is kept in your desktop's keyring (GNOME Keyring or KWallet), opening Nibtree again brings the running window forward (with the folder you opened), and the update check links to the new AppImage. The memory readout is not on Linux yet.
• Click a change bar beside the line numbers in the editor to open a change peek under it, like VS Code: the change's diff against the staged version in your Diff layout, with Stage this change, Revert this change, the next and previous change, and Close (or Escape). Every change in the peek's diff has its own Revert button too.
• Switch between worktrees from the top bar: when a repository has more than one, a worktree button after the branch lists them all with their branch and folder, changed files, commits to push and pull, a stopped merge or rebase, and when each last changed. Click one to make it active: it joins the window's workspace, and the tabs, terminals and AI agents of every worktree keep running.
• A new diff layout, Aligned, shows the two versions side by side the way VS Code does: both sides scroll as one and every line sits level with its match, a hatched filler stands where one side has no lines, and a red - or green + marks each changed line. Pick it with the new button in the diff toolbar or Diff layout in Settings > Git; Side by side stays the default.
• Nibtree runs in your browser too: npx nibtree (or npx nibtree@next for the newest beta) starts it on your machine and opens the whole app in a browser tab, with its own settings in ~/.nibtree-browser. It works on macOS, Linux and Windows, on Intel and Arm, and needs an access token on every page; --host 0.0.0.0 lets other machines in.
• The browser version also comes as a Docker image with git, git-lfs, SSH and GnuPG inside: docker run -p 4410:4410 -v "$PWD:/workspace" ghcr.io/shibbirweb/nibtree (also on Docker Hub). It listens on its own port, 4410, so it can run next to npx nibtree; NIBTREE_PUBLIC_URL prints the right address when you map another port. docker/compose.yaml starts it with docker compose up -d, reachable only from your own machine.
• The browser version's npm packages are published straight from GitHub Actions with npm's trusted publishing, so npm shows their provenance: the commit and the workflow that built each one. The image's Docker Hub page now explains how to run it, its tags and volumes.
• The merge tool has two layouts. Columns shows yours, the result and theirs side by side; Stacked shows yours and theirs on top and the result across the bottom, with Accept, Accept both and Ignore above each change and a note on each open conflict in the result. Switch with the buttons in the toolbar, without losing any work; the choice is remembered and Merge tool layout in Settings > Git sets it.
• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.
• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.
• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.
• Inline diffs mark each changed line like git diff: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.
• Notifications: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.
• Revert one change: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.
• Two debugging tools for the MCP server and nibtree cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.
• Staging view: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.
• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.
• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Nibtree quits. Closing a Mac's lid still puts it to sleep.
• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Nibtree read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).
• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.
• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.
• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.
• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.
• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.
• Commit box per repository...

Nibtree v0.1.0-beta.15

Added

• Nibtree runs in your browser too: npx nibtree (or npx nibtree@next for the newest beta) starts it on your machine and opens the whole app in a browser tab, with its own settings in ~/.nibtree-browser. It works on macOS, Linux and Windows, on Intel and Arm, and needs an access token on every page; --host 0.0.0.0 lets other machines in.
• The browser version also comes as a Docker image with git, git-lfs, SSH and GnuPG inside: docker run -p 4410:4410 -v "$PWD:/workspace" ghcr.io/shibbirweb/nibtree (also on Docker Hub). It listens on its own port, 4410, so it can run next to npx nibtree; NIBTREE_PUBLIC_URL prints the right address when you map another port. docker/compose.yaml starts it with docker compose up -d, reachable only from your own machine.
• The browser version's npm packages are published straight from GitHub Actions with npm's trusted publishing, so npm shows their provenance: the commit and the workflow that built each one. The image's Docker Hub page now explains how to run it, its tags and volumes.
• The merge tool has two layouts. Columns shows yours, the result and theirs side by side; Stacked shows yours and theirs on top and the result across the bottom, with Accept, Accept both and Ignore above each change and a note on each open conflict in the result. Switch with the buttons in the toolbar, without losing any work; the choice is remembered and Merge tool layout in Settings > Git sets it.
• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.
• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.
• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.
• Inline diffs mark each changed line like git diff: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.
• Notifications: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.
• Revert one change: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.
• Two debugging tools for the MCP server and nibtree cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.
• Staging view: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.
• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.
• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Nibtree quits. Closing a Mac's lid still puts it to sleep.
• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Nibtree read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).
• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.
• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.
• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.
• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.
• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.
• Commit box per repository: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.
• Nibtree for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).
• nibtree cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.
• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: nibtree cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.
• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged ta...

Nibtree v0.1.0-beta.14

Added

• Nibtree runs in your browser too: npx nibtree (or npx nibtree@next for the newest beta) starts it on your machine and opens the whole app in a browser tab, with its own settings in ~/.nibtree-browser. It works on macOS, Linux and Windows, on Intel and Arm, and needs an access token on every page; --host 0.0.0.0 lets other machines in.
• The browser version also comes as a Docker image with git, git-lfs, SSH and GnuPG inside: docker run -p 4410:4410 -v "$PWD:/workspace" ghcr.io/shibbirweb/nibtree (also on Docker Hub). It listens on its own port, 4410, so it can run next to npx nibtree; NIBTREE_PUBLIC_URL prints the right address when you map another port. docker/compose.yaml starts it with docker compose up -d, reachable only from your own machine.
• The browser version's npm packages are published straight from GitHub Actions with npm's trusted publishing, so npm shows their provenance: the commit and the workflow that built each one. The image's Docker Hub page now explains how to run it, its tags and volumes.
• The merge tool has two layouts. Columns shows yours, the result and theirs side by side; Stacked shows yours and theirs on top and the result across the bottom, with Accept, Accept both and Ignore above each change and a note on each open conflict in the result. Switch with the buttons in the toolbar, without losing any work; the choice is remembered and Merge tool layout in Settings > Git sets it.
• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.
• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.
• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.
• Inline diffs mark each changed line like git diff: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.
• Notifications: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.
• Revert one change: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.
• Two debugging tools for the MCP server and nibtree cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.
• Staging view: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.
• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.
• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Nibtree quits. Closing a Mac's lid still puts it to sleep.
• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Nibtree read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).
• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.
• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.
• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.
• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.
• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.
• Commit box per repository: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.
• Nibtree for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).
• nibtree cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.
• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: nibtree cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.
• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged ta...

Nibtree v0.1.0-beta.13

Added

• Nibtree runs in your browser too: npx nibtree (or npx nibtree@next for the newest beta) starts it on your machine and opens the whole app in a browser tab, with its own settings in ~/.nibtree-browser. It works on macOS, Linux and Windows, on Intel and Arm, and needs an access token on every page; --host 0.0.0.0 lets other machines in.
• The browser version also comes as a Docker image with git, git-lfs, SSH and GnuPG inside: docker run -p 4410:4410 -v "$PWD:/workspace" ghcr.io/shibbirweb/nibtree (also on Docker Hub). It listens on its own port, 4410, so it can run next to npx nibtree; NIBTREE_PUBLIC_URL prints the right address when you map another port. docker/compose.yaml starts it with docker compose up -d, reachable only from your own machine.
• The merge tool has two layouts. Columns shows yours, the result and theirs side by side; Stacked shows yours and theirs on top and the result across the bottom, with Accept, Accept both and Ignore above each change and a note on each open conflict in the result. Switch with the buttons in the toolbar, without losing any work; the choice is remembered and Merge tool layout in Settings > Git sets it.
• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.
• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.
• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.
• Inline diffs mark each changed line like git diff: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.
• Notifications: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.
• Revert one change: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.
• Two debugging tools for the MCP server and nibtree cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.
• Staging view: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.
• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.
• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Nibtree quits. Closing a Mac's lid still puts it to sleep.
• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Nibtree read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).
• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.
• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.
• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.
• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.
• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.
• Commit box per repository: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.
• Nibtree for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).
• nibtree cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.
• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: nibtree cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.
• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged tag shows what is in the next commit.
• Inline diffs: Settings > Git > Diff layout, or the two buttons in the diff toolbar, switch every diff between Side by side and Inline. Inline shows one column with each change's removed lines above the lines that replace th...

Git Manager v0.1.0-beta.9

Added

• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, like PhpStorm, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.

• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.

• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.

• Inline diffs mark each changed line like git diff and GitLens: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.

• Notifications, like PhpStorm: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.

• Revert one change, like PhpStorm and GitLens: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.

• Two debugging tools for the MCP server and git-manager cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.

• Staging view, like PhpStorm: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.

• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.

• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Git Manager quits. Closing a Mac's lid still puts it to sleep.

• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Git Manager read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).

• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.

• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.

• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.

• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.

• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.

• Commit box per repository, like VS Code: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, like JetBrains, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.

• Git Manager for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).

• git-manager cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.

• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: git-manager cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.

• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged tag shows what is in the next commit.

• Inline diffs: Settings > Git > Diff layout, or the two buttons in the diff toolbar, switch every diff between Side by side and Inline. Inline shows one column with each change's removed lines above the lines that replace them, old and new line numbers side by side, and the same colors. Removed lines can be selected, copied and found with Cmd+F, and single changes and lines still stage, unstage and discard. The choice is remembered.

• The Changes tab has a commit box below its file list, the same one as the Changes sidebar with the same message, so you can commit (or commit and push) without leaving the tab.

• New File, like Sublime Text: File > New File (Cmd+N) opens an empty Untitled tab named after its first line. Cmd+S asks where to save it; saved inside the folder, the tab becomes that file's tab.

• Remember unsaved changes in Settings > Editor > Saving (on by default): closing the window, quitting, Close Folder and Clear Cache keep the text of Untitled tabs and the unsaved edits of files, without asking, and the tabs come back with them the next time the folder opens. The text is kept in ~/.gitmanager/unsaved until you save, revert or discard it. Closing a tab yourself still asks.

• Clear Cache: a brush button right of Memory in the status bar, and View > Clear C...

Nibtree v0.1.0-beta.12

Added

• The merge tool has two layouts. Columns shows yours, the result and theirs side by side; Stacked shows yours and theirs on top and the result across the bottom, with Accept, Accept both and Ignore above each change and a note on each open conflict in the result. Switch with the buttons in the toolbar, without losing any work; the choice is remembered and Merge tool layout in Settings > Git sets it.
• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.
• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.
• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.
• Inline diffs mark each changed line like git diff: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.
• Notifications: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.
• Revert one change: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.
• Two debugging tools for the MCP server and nibtree cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.
• Staging view: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.
• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.
• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Nibtree quits. Closing a Mac's lid still puts it to sleep.
• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Nibtree read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).
• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.
• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.
• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.
• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.
• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.
• Commit box per repository: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.
• Nibtree for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).
• nibtree cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.
• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: nibtree cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.
• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged tag shows what is in the next commit.
• Inline diffs: Settings > Git > Diff layout, or the two buttons in the diff toolbar, switch every diff between Side by side and Inline. Inline shows one column with each change's removed lines above the lines that replace them, old and new line numbers side by side, and the same colors. Removed lines can be selected, copied and found with Cmd+F, and single changes and lines still stage, unstage and discard. The choice is remembered.
• The Changes tab has a commit box below its file list, the same one as the Changes sidebar with the same message, so you can commit (or commit and push) without leaving the tab.
• New File: File > New File (Cmd+N) opens an empty Untitled tab named after its first line. Cmd+S asks where to save it; saved inside the folder, the tab becomes that file's tab.
• Remember unsaved changes in Settings > Editor > Saving (on by default): closing the window, quitting, Close Folder and Clear Cache keep the text of Untitled tabs and the unsaved edits of files, without ask...

Nibtree v0.1.0-beta.11

Added

• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.

• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.

• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.

• Inline diffs mark each changed line like git diff: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.

• Notifications: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.

• Revert one change: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.

• Two debugging tools for the MCP server and nibtree cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.

• Staging view: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.

• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.

• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Nibtree quits. Closing a Mac's lid still puts it to sleep.

• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Nibtree read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).

• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.

• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.

• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.

• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.

• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.

• Commit box per repository: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.

• Nibtree for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).

• nibtree cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.

• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: nibtree cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.

• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged tag shows what is in the next commit.

• Inline diffs: Settings > Git > Diff layout, or the two buttons in the diff toolbar, switch every diff between Side by side and Inline. Inline shows one column with each change's removed lines above the lines that replace them, old and new line numbers side by side, and the same colors. Removed lines can be selected, copied and found with Cmd+F, and single changes and lines still stage, unstage and discard. The choice is remembered.

• The Changes tab has a commit box below its file list, the same one as the Changes sidebar with the same message, so you can commit (or commit and push) without leaving the tab.

• New File: File > New File (Cmd+N) opens an empty Untitled tab named after its first line. Cmd+S asks where to save it; saved inside the folder, the tab becomes that file's tab.

• Remember unsaved changes in Settings > Editor > Saving (on by default): closing the window, quitting, Close Folder and Clear Cache keep the text of Untitled tabs and the unsaved edits of files, without asking, and the tabs come back with them the next time the folder opens. The text is kept in ~/.nibtree/unsaved until you save, revert or discard it. Closing a tab yourself still asks.

• Clear Cache: a brush button right of Memory in the status bar, and View > Clear Cache, restart the window's interface in a fresh WebKit process and give back all the memory it holds (measured: 328 MB with every file closed after a Markdown s...

Git Manager v0.1.0-beta.10

Added

• The window glows softly in the open project's color from its top left corner, the same color as its tile on the Welcome page, like PhpStorm, so windows are easy to tell apart. On macOS the window buttons now sit in the app's top bar, with no separate title strip. Turn the color off with Project color in the top bar in Settings > Appearance.

• A commit's message and details (History panel and commit tabs) can be resized: drag the bar above the changed files. The height is remembered.

• Every diff (Changes, the Changes tab, commits in History and commit tabs, branch and revision compares, shelves, Compare Files and local history) is one view with the same toolbar and buttons. A commit's diff gets Revert this change and Apply this change for your working tree, and three columns (parent, commit and working tree); Side by side for commits in Settings > Git picks them.

• Inline diffs mark each changed line like git diff and GitLens: a red - before a removed line and a green + before an added one, so old and new lines stay apart inside a changed (blue) block.

• Notifications, like PhpStorm: messages pop up as balloons in the bottom right corner, with an icon for the kind, a title that names the branch and where it went ("Pushed 2 commits of main to origin/main", "Pulled origin/main into main", "Fetched origin: nothing new", "Could not push main"), the repository it came from, what git did (the commits that moved, new and deleted branches, files changed, or git's error) and a link such as Undo. A balloon stays open while the pointer is over it, and at most four show at once. The new bell at the bottom of the right activity bar (also the status bar bell and View > Notifications) opens a Notifications panel in the right sidebar that lists every message of the session, such as pushes, pulls and fetches, newest first with a dot on the unseen ones. Clear one with its x or all with the trash can, and turn Do Not Disturb on from the panel. While the panel is shown, nothing pops up.

• Revert one change, like PhpStorm and GitLens: in the Changes diff each change has a Revert this change button next to Stage (side by side and inline), which puts the staged version of its lines back in the working tree, with Undo. In the file editor, click a change bar beside the line numbers to put the last commit's lines back (an ordinary edit you can undo). Both ask first.

• Two debugging tools for the MCP server and git-manager cli: inspect_layout lists what is scrolled and what reaches past the window, and trace_scrolls records every scroll with the code that made it.

• Staging view, like PhpStorm: the Three panes button in the Changes diff shows a modified file as HEAD, the index and the working tree side by side, with bands for what is staged and what is not. The arrows on the bands stage or unstage single changes. Side by side and Inline go back to the usual diff; the choice is remembered. Settings > Git picks 2 or 3 columns for the Changes diff and for merge commits.

• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.

• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Git Manager quits. Closing a Mac's lid still puts it to sleep.

• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Git Manager read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).

• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.

• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.

• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.

• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.

• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.

• Commit box per repository, like VS Code: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, like JetBrains, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.

• Git Manager for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).

• git-manager cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.

• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: git-manager cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.

• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged tag shows what is in the next commit.

• Inline diffs: Settings > Git > Diff layout, or the two buttons in the diff toolbar, switch every diff between Side by side and Inline. Inline shows one column with each change's removed lines above the lines that replace them, old and new line numbers side by side, and the same colors. Removed lines can be selected, copied and found with Cmd+F, and single changes and lines still stage, unstage and discard. The choice is remembered.

• The Changes tab has a commit box below its file list, the same one as the Changes sidebar with the same message, so you can commit (or commit and push) without leaving the tab.

• New File, like Sublime Text: File > New File (Cmd+N) opens an empty Untitled tab named after its first line. Cmd+S asks where to save it; saved inside the folder, the tab becomes that file's tab.

• Remember unsaved changes in Settings > Editor > Saving (on by default): closing the window, quitting, Close Folder and Clear Cache keep the text of Untitled tabs and the unsaved edits of files, without asking, and the tabs come back with them the next time the folder opens. The text is kept in ~/.gitmanager/unsaved until you save, revert or discard it. Closing a tab yourself still asks.

• Clear Cache: a brush button right of Memory in the status bar, and View > Clear C...

Git Manager v0.1.0-beta.8

Added

• Terminal memory: the memory details in the status bar list each terminal, AI agent and Run script of the window with its memory (the shell and everything it started, such as Claude Code or a dev server), biggest first, with their sum. Click a row to show that terminal.

• Keep computer awake: the coffee cup in the status bar (or Settings > AI) picks On (always), Agent (while an AI agent works) or Off (the default). While active, the screen stays on, does not lock and the computer does not sleep; it lets go when the agents finish or Git Manager quits. Closing a Mac's lid still puts it to sleep.

• AI usage in the status bar: Claude Code's and Codex's 5-hour and weekly limits, and Claude Code's Fable weekly limit ("42% 2h 15m · 83% 2d 4h · 57% Fable 2d 4h": each limit's use and the time left until it resets), orange from 80% and red from 95%; click for each limit's bar and reset time. Claude Code's numbers come from Anthropic with Claude Code's own sign-in (macOS asks once to let Git Manager read it from the Keychain; it is never stored), Codex's from its own session files. Settings > AI > Usage in status bar puts it on the right (default), the left or nowhere, and Show usage of picks which agents it shows (both by default; a hidden one is not read).

• Each AI agent's command is a setting: Settings > AI > Agents changes the command that starts it, its full-autonomy flags, how it takes a first prompt and extra arguments, with a preview, so a provider's renamed command or flag needs no app update.

• AI tasks: work on several branches of one project at once. New Task (+ next to a repository in the AI panel, or View > New AI Task...) turns a task name into a branch and a worktree from the project's main branch, with an agent and an optional first prompt; Add Agent to Race gives up to five agents their own worktrees for the same task. New worktrees are ready to run: files listed in .worktreeinclude (such as .env) are copied and node_modules is linked (Settings > AI > Link into new worktrees). Finish Task closes the worktree's agents and removes the worktree and its branch, asking before losing changes or an unmerged branch.

• AI agents: the robot button under Files in the right activity bar (or View > AI Agents) opens an AI panel that shows each repository of the workspace with a card per worktree and the agents working in it, with a filter, a New Agent button and a count of the agents that need you. Hover a worktree and click + to start Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, Aider, Amp or Qwen Code (whichever are installed) in its own tab; each agent shows whether it is working (a spinner), needs you (an orange question mark) or is done (a check), what it works on and since when, and a hidden agent that finishes marks its tab. New Worktree from the panel can start an agent in the new worktree, and a + after an agent's tab starts another agent or a terminal in the same worktree. The first agent asks whether agents should ask before acting or work with full autonomy; Settings > AI changes it and adds extra arguments per agent.

• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.

• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.

• Commit box per repository, like VS Code: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, like JetBrains, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.

• Git Manager for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).

• git-manager cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.

• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: git-manager cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.

• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged tag shows what is in the next commit.

• Inline diffs: Settings > Git > Diff layout, or the two buttons in the diff toolbar, switch every diff between Side by side and Inline. Inline shows one column with each change's removed lines above the lines that replace them, old and new line numbers side by side, and the same colors. Removed lines can be selected, copied and found with Cmd+F, and single changes and lines still stage, unstage and discard. The choice is remembered.

• The Changes tab has a commit box below its file list, the same one as the Changes sidebar with the same message, so you can commit (or commit and push) without leaving the tab.

• New File, like Sublime Text: File > New File (Cmd+N) opens an empty Untitled tab named after its first line. Cmd+S asks where to save it; saved inside the folder, the tab becomes that file's tab.

• Remember unsaved changes in Settings > Editor > Saving (on by default): closing the window, quitting, Close Folder and Clear Cache keep the text of Untitled tabs and the unsaved edits of files, without asking, and the tabs come back with them the next time the folder opens. The text is kept in ~/.gitmanager/unsaved until you save, revert or discard it. Closing a tab yourself still asks.

• Clear Cache: a brush button right of Memory in the status bar, and View > Clear Cache, restart the window's interface in a fresh WebKit process and give back all the memory it holds (measured: 328 MB with every file closed after a Markdown session, 127 MB after). The screen blinks once and the folder and tabs come back. Terminals and Run sessions keep running and come back in the same place with what they showed, so a dev server or a build never stops. It waits for unsaved files and running git operations.

• Unload hidden tabs in Settings > Editor (on by default): a file tab you have not looked at for 15 minutes (or 5, 30, 60) frees its editor, about 4 MB each. The tab stays in the strip and opens again at the same line; tabs with unsaved changes are never unloaded. Undo history of an unloaded tab starts over.

• Syntax highlighting switch in Settings > Editor (on by default). Off, code in editors, diffs, the merge tool and Markdown code blocks shows as plain text and no language grammar is loaded, which saves about 35 MB. Toggle Comment still works; fold arrows and bracket pair colors need highlighting, and sticky scroll follows the indentation instead.

• Search in Settings: type in the field at the top left of the Settings dialog to keep only the sections with a match, and the open section shows only the matching settings with the matched words highlighted. Words match the start of a setting's words, other common names work too (for example "ruler" or "autosave"), and matching keyboard shortcuts filter the Keyboard Shortcuts list. Esc clears the search, then closes Settings.

• Single tab title in Settings > Editor (on by default): with Tab limit set to Single tab and only one tab open, the tab strip shows the file's name in the middle instead of a lone tab. Open a second tab, such as a terminal, and the tabs come back.

• Navigation Bar, like JetBrains: press Cmd+Up (Alt+Home on Windows and Linux), choose Edit > Jump to Navigation Bar, or click the path above the code to open a list of what each folder holds. Up and Down pick, Right and Left go into and out of folders, Enter opens a file, and typing searches the list, with Search Everywhere one Enter away when nothing matches. The welcome screen of an open project shows the bar at the top, and on the Log or a diff it floats at the top of the window. In the code editor Cmd+Up now opens it (Cmd+Home still goes to the start of the file). Settings > Appearance > File toolbar puts each file's toolbar (path, badges and buttons) at the Top or the Bottom of the code, or hides it, with a switch for each part: path, badges, change arrows, Blame, Copy relative path, the Markdown view switch and the Markdown formatting row. Without the path, Cmd+Up shows the bar floating at the top left of the editor.

• Recent Files, like JetBrains: Cmd+E (Ctrl+E on Windows and Linux) or Edit > Recent Files lists the files you worked on last, with the previous file selected so Cmd+E, Enter switches back. Type to filter, press Cmd+E again for edited files only, and Delete to take a file off the list. Each workspace keeps its own list across ...

Git Manager v0.1.0-beta.7

Added

• Sign-in prompts: when a push, pull, fetch or clone needs a username and password (HTTPS), an SSH key passphrase or a yes for a new SSH host, a dialog asks for it instead of the command failing with "terminal prompts disabled". Username and password come in one dialog, with a reminder that GitHub, GitLab and Bitbucket take a token. Git saves the login with your credential helper; background auto fetch never asks.

• Monokai Charcoal color theme: Monokai on a charcoal background, with red keywords, tags and operators, green attributes, gold strings, lavender constants and plain white function calls and variables.

• Commit box per repository, like VS Code: the new button in the Changes title bar, or Settings > Git > Commit box, switches between one commit box under the Changes list (Single, like JetBrains, the default) and a commit box at the top of each repository (Per repository). Each repository keeps its own message in both layouts, and the Changes tab follows the setting with its box above the files.

• Git Manager for Windows 10 and 11: a per-user installer (the -setup.exe of a release, no administrator rights needed) with the same features as on macOS. Paths show as C:/..., shortcuts use Ctrl, the terminal starts PowerShell, Command Prompt or Git Bash, deleted files go to the Recycle Bin, the GitHub token is kept in Windows Credential Manager, a second launch opens its folder in the running app, Cancel stops git and everything it started, and the status bar counts memory like Task Manager. The installer is not signed yet, so Windows SmartScreen asks once (More info, Run anyway).

• git-manager cli call reads its arguments from a JSON file with --args-file <file>, or from stdin with --args-file -, for shells that mangle quotes such as Windows PowerShell 5.1.

• Clone Repository... on the welcome screen opens the Clone dialog, so you can start from a repository on GitHub or another server without opening a folder first. Scripts and AI tools can clone too: git-manager cli clone <url> [folder] [--into <folder>] [--open window|workspace] and the MCP tool clone_repository. The tool starts off, since it writes outside the open folders; turn it on in Help > Available MCP Tools.

• The Changes tab (click N changes in the status bar) can stage, unstage and discard: hover a file for Stage, Unstage and Discard changes, right-click it for more, or use Stage all, Unstage all and Discard all next to Changed files. A staged or partly staged tag shows what is in the next commit.

• Inline diffs: Settings > Git > Diff layout, or the two buttons in the diff toolbar, switch every diff between Side by side and Inline. Inline shows one column with each change's removed lines above the lines that replace them, old and new line numbers side by side, and the same colors. Removed lines can be selected, copied and found with Cmd+F, and single changes and lines still stage, unstage and discard. The choice is remembered.

• The Changes tab has a commit box below its file list, the same one as the Changes sidebar with the same message, so you can commit (or commit and push) without leaving the tab.

• New File, like Sublime Text: File > New File (Cmd+N) opens an empty Untitled tab named after its first line. Cmd+S asks where to save it; saved inside the folder, the tab becomes that file's tab.

• Remember unsaved changes in Settings > Editor > Saving (on by default): closing the window, quitting, Close Folder and Clear Cache keep the text of Untitled tabs and the unsaved edits of files, without asking, and the tabs come back with them the next time the folder opens. The text is kept in ~/.gitmanager/unsaved until you save, revert or discard it. Closing a tab yourself still asks.

• Clear Cache: a brush button right of Memory in the status bar, and View > Clear Cache, restart the window's interface in a fresh WebKit process and give back all the memory it holds (measured: 328 MB with every file closed after a Markdown session, 127 MB after). The screen blinks once and the folder and tabs come back. Terminals and Run sessions keep running and come back in the same place with what they showed, so a dev server or a build never stops. It waits for unsaved files and running git operations.

• Unload hidden tabs in Settings > Editor (on by default): a file tab you have not looked at for 15 minutes (or 5, 30, 60) frees its editor, about 4 MB each. The tab stays in the strip and opens again at the same line; tabs with unsaved changes are never unloaded. Undo history of an unloaded tab starts over.

• Syntax highlighting switch in Settings > Editor (on by default). Off, code in editors, diffs, the merge tool and Markdown code blocks shows as plain text and no language grammar is loaded, which saves about 35 MB. Toggle Comment still works; fold arrows and bracket pair colors need highlighting, and sticky scroll follows the indentation instead.

• Search in Settings: type in the field at the top left of the Settings dialog to keep only the sections with a match, and the open section shows only the matching settings with the matched words highlighted. Words match the start of a setting's words, other common names work too (for example "ruler" or "autosave"), and matching keyboard shortcuts filter the Keyboard Shortcuts list. Esc clears the search, then closes Settings.

• Single tab title in Settings > Editor (on by default): with Tab limit set to Single tab and only one tab open, the tab strip shows the file's name in the middle instead of a lone tab. Open a second tab, such as a terminal, and the tabs come back.

• Navigation Bar, like JetBrains: press Cmd+Up (Alt+Home on Windows and Linux), choose Edit > Jump to Navigation Bar, or click the path above the code to open a list of what each folder holds. Up and Down pick, Right and Left go into and out of folders, Enter opens a file, and typing searches the list, with Search Everywhere one Enter away when nothing matches. The welcome screen of an open project shows the bar at the top, and on the Log or a diff it floats at the top of the window. In the code editor Cmd+Up now opens it (Cmd+Home still goes to the start of the file). Settings > Appearance > File toolbar puts each file's toolbar (path, badges and buttons) at the Top or the Bottom of the code, or hides it, with a switch for each part: path, badges, change arrows, Blame, Copy relative path, the Markdown view switch and the Markdown formatting row. Without the path, Cmd+Up shows the bar floating at the top left of the editor.

• Recent Files, like JetBrains: Cmd+E (Ctrl+E on Windows and Linux) or Edit > Recent Files lists the files you worked on last, with the previous file selected so Cmd+E, Enter switches back. Type to filter, press Cmd+E again for edited files only, and Delete to take a file off the list. Each workspace keeps its own list across restarts, and Quick Open and Search Everywhere show the same recent files. It is on by default and can be turned off in Settings > Editor > Recent Files (measured at about 1 MB); while it is off, Cmd+E says so and offers to open the setting.

• Editor font weight in Settings > Editor: draw code from Thin (100) to Black (900), with a live preview. Light (300) with JetBrains Mono gives a soft look like JetBrains IDEs. It applies to the editor, diffs, the merge tool and Markdown code blocks.

• The empty editor area also offers Go to File (Cmd+P) and Search Everywhere (Shift Shift).

• JetBrains-style 3-way merge tool: Yours, Result and Theirs panes with connectors, apply, append and ignore per change, apply all non-conflicting changes, word-level highlights, synchronized scrolling, F7 navigation, full undo and ignore-whitespace mode.

• Conflicts dialog to accept yours or theirs for whole files (including binary and deleted files), then continue or abort the merge, rebase, cherry-pick or revert.

• Inline conflict actions in the editor: Accept Current, Accept Incoming, Accept Both and Resolve in Merge Tool, plus Mark as Resolved.

• Workspaces like VS Code: open any folder (git or not), nested repositories, several folders in one workspace, and workspace files compatible with .code-workspace.

• Changes sidebar grouped by repository with staging of files and hunks, discard, commit and amend.

• Stage, unstage or discard selected lines in the Changes diff, like GitHub Desktop: select lines on either side and use the toolbar, the right-click menu, Git > Uncommitted Changes or Option+Shift+Cmd+S / U / D. Discard asks first and offers Undo.

• Editor tabs with preview tabs, git status letters in the Files panel, breadcrumbs, change markers on the scrollbar and next or previous change navigation.

• Git blame for the current line and a blame gutter, with click-through to the commit in the Log.

• Log with a branch graph, commit details and per-file diffs; cherry-pick, revert, reset and checkout.

• Open a commit in its own editor tab, like VS Code, so its diff gets the whole editor area: double-click it in the Log, press Enter, use Open in Tab, or double-click one of its files.

• Branches, tags and stashes sidebar; fetch, pull and push with progress.

• Back and Forward navigation across files, diffs and commits.

• Settings saved in ~/.gitmanager: theme, fonts, ligatures, tab size, word wrap, blame, zoom with Ctrl or Cmd + mouse wheel.

• Status bar with the current repository, branch, cursor position and the app's memory use.

• Clicking the changes count in the status bar opens a Changes tab: every uncommitted file of the repository, each compared with the last commit. Its file list can be resized or hidden to give the diff more room.

• Works as git mergetool.

• Update check: notify-only checks for new releases on the stable or beta channel, with release notes and a download link, plus What's New after an update.

• Settings, About: star the project on GitHub, report a bug (with your version filled in) or request a feature.

• A wiki with a user guide (with screenshots ...