Skip to content

v0.7.8: installs that work on the laptops people really have

Choose a tag to compare

View all tags
@batrapulkit batrapulkit released this 08 Oct 12:28
· 8 commits to main since this release
v0.7.8
0fddbbb

Installs that work on the laptops people really have

Every way we found a founder's install going wrong, fixed, each with a test.

Windows

  • Cursor on a profile with a space (C:\Users\Rahul Kumar) no longer blocks every action. Cursor runs hooks through PowerShell, where a quoted path isn't run. The hook line is now one word per path in cmd, PowerShell and bash, and squidbrake doctor checks it in PowerShell too.
  • Company proxies: the hooks reach the gateway on this computer directly and never through the system proxy. If something that isn't Squidbrake answers (a proxy's sign-in page), the call is blocked instead of run unchecked.
  • About 2 seconds faster per tool call: hooks use 127.0.0.1, not localhost. Windows tries IPv6 first and waits before falling back.
  • User folders in other scripts (Devanagari, Cyrillic, ...) no longer stop a command or the background service.
  • Windows on ARM installs: httptools has no wheel for it, so it's skipped there.
  • The background service waits longer each time the gateway fails to start (up to 5 minutes) instead of every 2 seconds. When stopped, it only ends a process that is Python.

First run, everywhere

  • If the port is taken, it says so before any key is printed or browser opened (the dashboard key used to land in the other app).
  • No browser over SSH or on Linux without a desktop.
  • squidbrake pilot join no longer asks the usage-stats question. With opposite defaults, pressing Enter on both put founders in the community pilot instead of theirs.
  • Saying no to the background service now explains that agents' actions wait while Squidbrake is off.

Antigravity

  • Its own housekeeping (checking background tasks and commands, notifying, reading pages and MCP resources) runs without asking. Typing into a running command and the browser agent still ask.

Installers (served from the pilots server, so already live)

  • Re-running upgrades in place. A failed download keeps the working install, and the background service is stopped and started again around the upgrade.
  • They show why pip or uv failed, and work behind HTTPS-inspecting proxies.
  • macOS: no developer-tools pop-up. Debian/Ubuntu: python3-venv is named. PATH goes in the file each shell reads. Home folders with spaces work. WSL is named.
  • If an install fails, it asks before sending the lines it printed, with your home folder shown as ~.

Upgrade: run the install line again, or pipx upgrade squidbrake

Assets 2
Loading