Skip to content

IntelyIDE 1.3.1

Choose a tag to compare

@ferencfarkas09 ferencfarkas09 released this 12 Oct 06:56
· 22 commits to main since this release
Immutable release. Only release title and notes can be modified.

IntelyIDE 1.3.1

The stable release of IntelyIDE, a desktop Git client for several repositories at once, with coding agents that can edit but never commit or push.

Download

File What it is SHA-256
IntelyIDE_1.3.1_x64.dmg The app for Intel Macs (it also runs on Apple Silicon under Rosetta 2), 17.1 MiB 7289ba9a8d42a564e151ed6ac00b230b08a8f3e151ebcc313de1889b2f7d567a
IntelyIDE_1.3.1_x64.sbom.cdx.json Software bill of materials (CycloneDX) of what is inside the disk image 2849dc25a6e1605e2bff251f0f9505657ad964d8dcded6eb7f493a01d2706a7c
SHA256SUMS The checksums of the files above

Install

  1. Open IntelyIDE_1.3.1_x64.dmg, drag IntelyIDE to Applications, eject the image and open the app from Applications.
  2. The app is signed with the maintainer's Developer ID and notarized by Apple, so it opens without a Gatekeeper warning. To check: spctl --assess --type execute --verbose /Applications/IntelyIDE.app prints accepted and source=Notarized Developer ID.
  3. Agent runs also need Node.js 24 or newer, your own Claude Code login and the Claude Agent SDK, which you install once with the installer inside the app: node '/Applications/IntelyIDE.app/Contents/Resources/sidecar/sdk-install.js' --yes (run it with --plan first to see what it would download). The Git features work without any of this. Details: docs/install-macos.md and docs/getting-started.md.

Verify the download

In the folder with the files: shasum -a 256 -c SHA256SUMS. This detects a damaged download. The checksums come from the same page as the files, so they cannot prove who made them.

What's changed

Fixed

  • The app asked for the Keychain password many times after the update to 1.3.0. All secrets (provider keys, Remote, Team, relay deploy, Servers, Mongo) now live in one Keychain item that is read once per start; the old per-secret items that exist are copied into it on first use and recorded as taken over, so they are never read again (they are not deleted, which could cause a second dialog). Expect one question per old item the first time (choose Always Allow), then at most one per start and none after Always Allow.
  • Deploying or updating the Remote relay from the installed app failed with "relay kit not found". The disk image now carries the Worker source and the built web bundle; the app copies them to its data folder, and Prepare installs the pinned wrangler there (it still needs Node.js and pnpm on your computer).
  • Creating or joining a team on a relay deployed before 1.3.0 ended in a bare HTTP error. The relay now reports its features in /api/status, and Settings > Team says "Your relay does not support teams yet", with a button to Settings > Remote. Other relay failures are shown as sentences.

More