Skip to content

IntelyIDE 1.4.0

Choose a tag to compare

View all tags
@ferencfarkas09 ferencfarkas09 released this 13 Oct 09:11
· 20 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.4.0
6809ff1

IntelyIDE 1.4.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.4.0_universal.dmg macOS 13.5 or later, Intel and Apple Silicon (one universal app), 30.9 MiB 8dabe0d13a8af6e42a5e178da8d03f513f923a262b92c795b3a72f33a6ec24fe
IntelyIDE_1.4.0.sbom.cdx.json Software bill of materials (CycloneDX) of what is inside the app 182efa22ad7a4c7af6d803c1f497f4430b1ebbdd08e3101b966989a7947024d9
SHA256SUMS The checksums of the files above

Install

macOS. Open IntelyIDE_1.4.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

  • Changes on a server. Under the Changes tree a new Server changes panel shows, read-only, the uncommitted changes of every repository a server run works in (and of any repository of a server you add): a "Server: " group with the branch, the changed files, the diff of each file in the usual diff viewer and the time of the last look. It reads with one bounded, hardened git status over the shared ssh connection, every 4 seconds while a run is active there, rarely when idle, and not at all while the panel is closed or the window is hidden. There is nothing to stage, commit, discard or stash on a server entry.
  • Bring changes here and Send my changes there: move uncommitted changes between this Mac and a server, only on a click and after a confirmation that lists the files and counts. Both copies must name the same origin and be on the same commit (nothing is fetched for you), the destination must be clean or you choose "apply on top" (the patch must then pass git apply --check), and the changes are applied to the working tree only: never staged, committed, pushed or checked out. Paths are validated (no .., absolute paths, .git, hooks folders, links or submodules), up to 200 new text files of 1 MB and 20 MB in all travel, binary and secret-looking new files stop the transfer, and sending is refused while a run is working in that repository (checked again under a lock right before the patch goes). The patch that is applied is byte for byte the one the dialog showed, modes are read from git (a link or submodule cannot hide behind 0120000), and environment files, editor tasks, hooks, make/npm configuration and files that become executable are highlighted in a diffstat and need an extra tick.
  • Your own runs can message each other, so a run on this Mac and a run on a server (or two runs here) work together. A Claude run gets two tools: peer_list (your other open runs: title, where, repositories, state; no transcript, no files) and peer_send (a message of up to 4 KB into a run that is working; the answer is that run sending one back). The IDE carries every message, also to a run on a server; nothing goes to teammates. By default a card asks once per pair of runs; Settings > Roles > Auto run > Messages between my runs can switch it to automatic or off. A message grants nothing: the receiving run keeps its own rules, and git push stays yours. Limits: 6 messages a minute per pair, 30 per run, 8 hops without a message from you ("Runs stopped messaging each other - your turn"). Both runs show the message as an agent message ("Sent to ..." / "From ..."), and the run list marks runs that talk. See docs/peer-runs.md.

More

Assets 6
Loading