Limboo v1.17.0

Limboo 1.17.0 (2026-08-01)

Changes since v1.16.0.

Plan Mode now stops. A plan waits for your decision instead of sliding into
implementation, and the plan you are shown is the plan the agent actually wrote —
which, until this release, it very often was not. Git also becomes a platform
service in its own right, so repository work reads as part of the conversation
rather than something that happened in a side panel.

Added

• Plan approval is a real stop, not a prompt. When the agent presents a plan,
  execution halts: no further model calls, no new prompts, no background work,
  and every tool is refused until you decide. Approving continues the same turn
  rather than starting a new one, so the agent keeps everything it had learned
  while planning. Approve, Approve & accept edits, Keep planning, Reject and
  Archive are the only things that move it forward.
• Keep planning now sends feedback. Instead of discarding the plan and
  starting over, it hands your notes to the agent, which revises and presents
  again — same conversation, same context.
• Plans are versioned. A session has one plan; refinements replace it and the
  previous text moves into History. Two windows on the same session can no longer
  approve different plans, and a plan that changed while you were reading it says
  so rather than acting on the stale copy.
• A pending plan survives a restart. Quit with a plan awaiting approval and it
  is still there on relaunch, with its buttons live and implementation still
  locked. Approving after a restart starts a fresh run carrying the plan text,
  because the paused conversation cannot outlive the process.
• Git is a platform service. Repository actions post structured entries into
  the conversation carrying the paths, commit and checkpoint behind them, with
  Open Diff, View Commit, Restore Checkpoint and Copy Command on each.
• Optional GitHub CLI integration. If gh is installed and signed in, a
  GitHub sub-tab lists pull requests and issues, and the agent can read them
  through the tools it already has. Limboo stores no GitHub credential —
  authentication stays the CLI's. Posting a comment is gated and shows the exact
  body first.
• Contributor avatars in history, fetched in the main process and embedded so
  no page ever requests a remote image. Behind git.avatars.enabled, which is
  off-limits by default in the sense that turning it on is the thing that tells
  GitHub which repository you are browsing — the setting says so.

Changed

• The integrated terminal is its own column between the conversation and the
  drawer, instead of competing for the drawer with Files and Changes.
• The Activity and Hooks drawer panels are gone. The Hook Engine, its audit
  log and every hook setting are untouched — only the two panels and the IPC they
  were the sole consumers of were removed.
• Switching sessions is now an ordered handover. Worktree, file watcher, git
  status, search index, memory scope, MCP and the agent are rebound in sequence,
  and a thin ribbon says so while it happens. Switching quickly between sessions
  cancels the stale work rather than letting it finish over the newer session.

Fixed

• The plan you approved was usually empty. Current Claude releases write the
  plan to a file and pass no plan text to the tool Limboo was reading, so almost
  every captured plan was blank — and because the tool was blocked, no plan file
  was produced either. Approving then sent an empty plan, the agent re-derived
  the work from scratch, and the empty plan was filed as completed. Limboo now
  tells the agent where to write its plan and reads it from there, with the
  agent's own copy taking over once the plan is approved.
• Starting a new plan could silently destroy the one you were reviewing when
  plan history was turned off. A pending plan is never discarded without being
  filed first, and starting a second plan while one awaits approval is refused.
• A failed or cancelled planning run reported itself as "rejected", which is
  what the app says when a person declines a plan. Those now read as ended, with
  the reason recorded, so declining and crashing no longer look identical.
• An unrelated prompt could mark a stalled plan complete. Only the run that
  was actually released to implement a plan can finish it.
• Live planning progress replayed the previous attempt's steps after asking
  for a new plan, because it measured from when the plan first existed rather
  than when the current attempt started.
• Deleting a session left its plan revisions behind in the database.
• A machine without git looked like a folder without a repository, and the app
  offered to initialise one — an action that could never succeed. Limboo now
  detects the missing binary and names the install command for your platform.
• Settings could be hand-edited into a dead drawer tab or an unbounded panel
  width; both are now validated and clamped on load.

Installing

Platform	File	Notes
Windows x64 / arm64	Limboo-Setup-*-<arch>.exe	If SmartScreen warns, choose More info → Run anyway.
macOS Apple silicon / Intel	Limboo-*-arm64.dmg / Limboo-*-x64.dmg	If Gatekeeper blocks it, right-click → Open, or xattr -dr com.apple.quarantine /Applications/Limboo.app.
Debian / Ubuntu	limboo-*-<arch>.deb
Fedora / RHEL / openSUSE	limboo-*-<arch>.rpm
Arch / Manjaro	limboo-*-<arch>.pacman	sudo pacman -U <file>
Any Linux	limboo-*-<arch>.AppImage	chmod +x first. On Ubuntu 24.04+ install libfuse2t64, or it fails with error loading libfuse.so.2.
Any Linux (no installer)	limboo-*-<arch>.tar.gz	Extract and run ./Limboo.

Once installed, Limboo updates itself from this feed — including the deb, rpm
and pacman builds, which apply updates through your package manager.

Verifying this release

Each artifact is listed in SHA256SUMS. Verify with sha256sum -c SHA256SUMS,
and verify build provenance with gh attestation verify <file> --repo limboo-ai/limboo.

3 commit(s) in this release.