Skip to content

IntelyIDE 1.9.0

Choose a tag to compare

View all tags
@ferencfarkas09 ferencfarkas09 released this 19 Oct 12:09
· 10 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.9.0
062535a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

IntelyIDE 1.9.0

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.9.0_universal.dmg macOS 13.5 or later, Intel and Apple Silicon (one universal app), 31.3 MiB 556cc7966604ac970fd51d9e4298010725c656ad3143ae75a5a6f85d22d6a34c
IntelyIDE_1.9.0.sbom.cdx.json Software bill of materials (CycloneDX) of what is inside the app 45256ad382027a2b59a9158d61dc59620bb5160ba2e45a2be34397558d0c7de2
SHA256SUMS The checksums of the files above

Install

macOS. Open IntelyIDE_1.9.0_universal.dmg, drag IntelyIDE to Applications, eject the image and open the app from Applications. 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.

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 (on macOS: 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

Added

  • Team mode for New run. When you start more than one run, Run 1 now leads and the others work for it (on by default, with a switch to keep every run independent). The lead splits the task, hands each worker a subtask through the existing messages between your runs, is the only run that asks you questions, and gives the combined summary; the workers do not ask you anything and write to the lead when they are blocked. Workers have exactly the permissions of an independent run, and the message rules and limits of docs/peer-runs.md apply. See docs/remote-servers.md.

More

Assets 6
Loading