What's new in Gloo Code

This page covers what changed in Gloo Code from version 1.18 (September 26, 2026) through 1.22, and how to use each part. For dates, see the changelog. The desktop app is for macOS. The command-line tool runs on macOS and Linux. To update the CLI, run gloocode update. The desktop app updates itself, or you can download it again from the desktop guide.

​

New in 1.22 (October 14, 2026)

• Find: ⌘F finds words in a session or an open file, with next and previous.
• Branch first: choose the branch before your first message, or stay on the current one. Set the default in Settings ▸ General.
• Appearance: Reduce motion, conversation text size, avatar colours, and a light/dark switch in the profile menu.

​

Review, commit, and open a pull request

In the desktop app, open the review panel with ⇧⌘R and choose Commit….

1. Pick the files to include.
2. Gloo Code drafts a branch name, a commit message, and a PR title and description. Edit any of them.
3. Choose Commit, Commit & push, or Commit & open PR. A draft PR option is available.

Opening a PR needs a GitHub connection. Drafted branch names follow the naming already used in your repository.

​

GitHub in sessions

The agent can read GitHub issues and pull requests, including private ones, without the gh command installed. Paste a PR link or type #42 in the prompt.

• Connect in Settings ▸ GitHub, or run gloocode github login. Use gloocode github status to check and gloocode github logout to disconnect.
• By default, posting a comment asks first.

​

Notion and Linear

Notion and Linear connectors are built in.

• Connect in Settings ▸ Notion or Settings ▸ Linear, or run gloocode notion login or gloocode linear login. Over SSH, add --paste and paste the address the browser ends on.
• Settings shows which account and workspace you are connected as. You can switch workspace without disconnecting and choose which tools the agent gets. Notion has an Only read option.
• Writes ask by default: every write shows what it will send and waits for your OK. Settings ▸ Safety lets you set a tool to Allow. Unleashed never approves these writes. Allow always is not offered in the prompt.
• If your Linear workspace needs an admin to approve new apps, Settings says so and lets you check again.
• Link a Linear issue or Notion page to a session from the link picker. A strip above the prompt shows the branch, its pull request, and the linked items.

​

Safety settings

After Gloo Code reads something someone else wrote, such as an issue, a pull request, a web page, a search result, a Notion page, a Linear issue, or an MCP tool result, an action that sends data out asks first. The prompt says what would be sent, where, and after reading what. Everyday work on files in your own repository does not trigger these extra prompts. Choose how strict this is in Settings ▸ Safety, with /safety, or with gloocode safety show, set, trust, untrust, and reset.

• A web fetch that redirects to another site needs approval for each hop.
• MCP servers stay pinned to the tool list you approved. If a server’s tools change, you approve the new list.
• If the safety settings file cannot be read, Gloo Code uses Strict and names the file. gloocode safety reset --move-aside sets it aside and starts fresh.
• gloocode run has no one to ask, so it refuses and prints the setting that would allow the action. See Run from scripts.

​

Unleashed mode

Unleashed replaces the old auto-accept toggle. It answers permission prompts across your open projects, and deny rules still apply. It never approves Notion or Linear writes. Turn it on from the desktop toggle or with ⌘⇧A. In the terminal it shows as UNLEASHED, and --unleashed turns it on for the terminal UI and for gloocode run.

​

Allowance and top-up

A ring beside Send shows how much of your monthly Gloo Code allowance is used. The terminal footer shows the same as allowance 42%. The ring changes colour as you approach the limit, with a warning at 80% and the limit at 100%, and a notice appears the first time your account crosses 80% in a period.

• Click the ring for the reset date and View usage. Admins also see Top up.
• At 100%, an admin sees Top up for the organization and I’ve topped up, keep going, which resends your last message. Members see the admins’ names and a Check again button.
• /usage shows the same percentages, the reset date, and this month’s requests and tokens, with no dollar amounts.

See Billing & Plans for tiers and top-ups.

​

Tabs and the branch picker

• ⌘T opens a new tab and Ctrl+Tab moves between tabs. Drag tabs to reorder. Choose Open in new tab on a session to open it in its own tab. Each tab has its own back and forward.
• On the default branch of a shared checkout, click the branch name in the session header to rename the branch or pick an existing local branch. In a worktree session you can rename it. Publishing uses the branch you chose.
• ⌘N starts a new session and ⌘K searches sessions across projects.

​

Retry and Continue

When a turn fails or you stop it, the output so far stays. On the newest turn, choose Retry to run it again or Continue to pick up where it left off. This works in the desktop app and the terminal.

​

Loop protection and handoff

If the agent repeats the same call, repeats the same error, or alternates between two calls without progress, Gloo Code first nudges it and then ends the turn. Repeated file reads get a notice that you already have the evidence, but they never end a turn. When the agent has used 80% of its step budget, it is told to write a handoff note, so you or the next session can continue from it.

​

Next steps