IntelyIDE 1.4.0

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

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Website: intelyhome.com

IntelyIDE 1.3.3

IntelyIDE 1.3.3

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.3_x64.dmg	The app for Intel Macs (it also runs on Apple Silicon under Rosetta 2), 17.2 MiB	af9cb0066312b164000dc88634d04e24cfff7356b884bfc7276b65e26470f56b
IntelyIDE_1.3.3_x64.sbom.cdx.json	Software bill of materials (CycloneDX) of what is inside the disk image	e2726d5f3178e093cdee4aa4f1477f1744637c38b2bb3da244888bbca8854cec
SHA256SUMS	The checksums of the files above

Install

1. Open IntelyIDE_1.3.3_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

Added

• Runs on a server no longer assume that a repository is at <root>/<its folder name on this Mac>. In Settings > Servers > Repositories every repository shows where it is looked for (default or mapped) and you can set its folder on the server, or let Find on server search the usual places once (read-only, bounded) and confirm what it found. The checks before a run, the agent's working folders, approvals and Clone missing use the chosen folders; two repositories with the same folder name are refused only when they end up in the same folder on the server.

More

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Website: intelyhome.com

IntelyIDE 1.3.2

IntelyIDE 1.3.2

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.2_x64.dmg	The app for Intel Macs (it also runs on Apple Silicon under Rosetta 2), 17.1 MiB	6648ecb3690ae8e8ce34f2055bfbea651d3fba2cba826b4a795d870e74cd791e
IntelyIDE_1.3.2_x64.sbom.cdx.json	Software bill of materials (CycloneDX) of what is inside the disk image	811ffb8142104d7e066abcebd7621cf9070f1d50405c1ec0350afef693af4bda
SHA256SUMS	The checksums of the files above

Install

1. Open IntelyIDE_1.3.2_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 closed a few seconds after every start when a repository had an accented letter (for example á) before a translation key on the same line: the translation scan cut the line inside the character. Since 1.3.0 the scan runs at start for shared projects, so the app could not be used.

More

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Website: intelyhome.com

IntelyIDE 1.3.1

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

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Website: intelyhome.com

IntelyIDE 1.3.0

IntelyIDE 1.3.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.3.0_x64.dmg	The app for Intel Macs (it also runs on Apple Silicon under Rosetta 2), 16.7 MiB	f72a8a9aae2daacdb213f8c231f37833c43a478ef8278023d3ec68616e90866c
IntelyIDE_1.3.0_x64.sbom.cdx.json	Software bill of materials (CycloneDX) of what is inside the disk image	dc349f9c7315cbf9262f312fc92b0557c49ecf7b01eed9f5d5ec50e9a9b19ba8
SHA256SUMS	The checksums of the files above

Install

1. Open IntelyIDE_1.3.0_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

It contains everything of the 1.2.0 that was prepared but never published, and the changes below.

Added

• Team collaboration (Beta): work together with colleagues through your own relay (Settings > Team, and the Team item in the rail). An admin creates a team and invites people with a one-time invite code; both sides compare a six-digit safety code before anything is shared. Everything the relay carries is end-to-end encrypted with a key only the members hold; removing a member (revocation) starts a new key that the removed person never gets.
• Live view of teammates' runs: tool calls, answers and diffs, shared per project and with secrets redacted before they leave the computer. A teammate can send a note into your run; it reaches the agent only after you approve it. Teammates can never answer permission cards or start runs.
• Workspace snapshot of a teammate (opt-in per project) so you can see the state of their files.
• Shared Claude memory (memory/*.md, opt-in per project): the notes stay equal on every teammate's computer, and a conflict is never merged for you; both versions are kept as conflict copies. CLAUDE.md is a separate opt-in (off by default, only while memory sharing is on); a teammate's change to it is never written automatically but shows as a pending change (View diff, Apply, Ignore) with a notification. Workspace requests are rate-limited per sender and a sender can hold at most 5 pending notes.
• The relay must be updated to get the Team Durable Object: Settings > Remote > update relay. See docs/team.md.
• Runs on your own servers (Settings > Servers, and "Where to run" in New run). Add a server by its ssh target, let the IDE set it up (Node.js 24 if missing, the agent files, the Agent SDK, optionally Claude Code), and start runs there: 3 on the build server and 2 on this Mac from one dialog, with a limit of agents per server. The agent's shell, file edits and the Claude CLI run on the server through your own ssh (keys and known_hosts as in a terminal, no password typed or stored, forwarding switched off). The permission broker stays in the IDE and judges the server's files through a read-only fs/query of the sidecar there; a look that cannot be answered denies the call. The git guard is made for the server's git and uploaded per run. A finished run gives up its place when the server is full, and its session is closed after ten minutes. See docs/remote-servers.md.
• Notifications (Settings > Notifications): a banner when a run needs a permission, asks a question, finishes or fails, a count of waiting runs on the Dock icon, a switch for each kind, a gap between two banners of one kind and run, at most twelve a minute over all runs, and an optional sound. A request that a saved rule answers within a second does not notify. The banner has a fixed sentence and the run's title, never a command or a file. Banners no longer depend on the menu-bar item. See docs/notifications.md.

Changed

• The disk image and the app are signed with the maintainer's Developer ID and notarized by Apple, with the notarization ticket stapled to both. macOS opens the app on the first launch without the "cannot verify" warning and without Open Anyway, also offline.
• The app runs with the hardened runtime. Its only extra permission is to send Apple Events, which the folder pickers and the notification banners need.
• Because the app's signature changes from ad hoc to the Developer ID, macOS may ask once, after the update, whether IntelyIDE may use the Keychain items an earlier version saved. Choose Always Allow. From now on the signature stays the same from release to release, so this question and the repeated folder-access questions do not come back after an update.

Fixed

• The Agent SDK installer made group-writable folders under a umask of 002 (the default of many Linux accounts) and then refused its own tree; the folders get an explicit mode and the installer sets its own umask.
• The check of the Agent SDK on a server (Settings > Servers > Test connection) gave up after 8 seconds, which a busy server or a slow disk exceeds while the SDK is fine; it has 40 seconds now.

Known limitations

• Team collaboration is a Beta: it was tested against a local relay and scripted stand-ins, not yet with many people over time. Only .md files up to 240 KB are shared as memory. See docs/team.md.
• Runs on a server do not support MCP servers, attachments, Rewind, providers other than Claude, the History view of server sessions or the Changes tree of the server's copy (review and commit on the server). A request of such a run is approved at the desktop, not from the phone. They were tried against a Linux container through a real ssh and against a scripted stand-in.
• Claude Code, when you let the setup install it on a server, comes from the npm registry in its current version without a hash check; Node.js and the Agent SDK are pinned and verified.
• Notification banners were checked in tests and logs; how macOS shows them on a given setup is not verified. A click on a banner brings the IDE forward and opens the run when the window gets focus within 90 seconds.

More

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Website: intelyhome.com

IntelyIDE 1.1.1

IntelyIDE 1.1.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.1.1_x64.dmg	The app for Intel Macs (it also runs on Apple Silicon under Rosetta 2), 16.2 MiB	cef2acce5b08374d5928c82b97ed180561e6282d028b65354a995dc6113ba346
IntelyIDE_1.1.1_x64.sbom.cdx.json	Software bill of materials (CycloneDX) of what is inside the disk image	4ad1be6db0bbe46d805da7765446072ee678b37a7793c55937fde62d3686c9df
SHA256SUMS	The checksums of the files above

Install

1. Open IntelyIDE_1.1.1_x64.dmg, drag IntelyIDE to Applications, eject the image and open the app from Applications.
2. The app is signed ad hoc and is not notarized, so macOS refuses the first launch. On macOS 15 and later open System Settings > Privacy & Security, scroll to the message about IntelyIDE, choose Open Anyway and confirm. On macOS 13 and 14 right-click the app and choose Open. Do this only for a file you downloaded from this repository's Releases page.
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

• Agents could not read or write although their role allowed it. Replaying the 431 shell commands of the recorded runs through the policy showed two causes, both fixed.
• Plan mode and the read-only roles (reviewer, researcher, manager) can read. 208 of the 431 commands that only read were refused as "not a read-only command" because the allow-list was too narrow: sed -n 140,175p file, grep ... 2>/dev/null, uniq, cut, tr, awk '{print $1}', echo "--- label", ls dir/*, cd a && ...; cd ../b; ls, git branch --show-current, git remote -v, git stash list, git reflog, and a find with -o (its -o was taken for an output option, which even hard-stopped Automatic). They run now without a card in Plan and Accept edits; 11 of the 208 remain refused, and they are the right ones (a folder outside the run, inline node -e, git add). sed stays a viewer (no -i, no w, e or r), awk only prints fields, uniq keeps one operand, and only /dev/null is a harmless redirect target.
• Automatic mode no longer refuses the commands developers write every day. 22 of the 289 shell calls of the biggest run (most of them reads and edits by developer sub-agents) were refused as "outside the run's folders" or "not known statically" although every path stayed inside the folders. The analyser now judges each operand where it really points, from the directory an earlier cd of the same command moved to; a search pattern or a sed or awk program is not a path; a variable the command assigns from literal words (f=src/a.js; git status $f) and a for loop over literal words are judged on the words the shell will see; a helper script kept in /tmp is scanned like one in a repository; and a git hidden behind a variable is found (g=git; $g commit is a hard stop).
• A value is read only when the command makes it certain: a quoted "$c" stays one word, a brace list or $(...) in a for list stays unknown, an assignment that may not have run (after ||, in a pipe, in the background) or that a loop leaves early is not followed, and read, printf -v, let, eval, mapfile, getopts, declare -n and IFS end the following.
• A glob is expanded and every match is judged like an operand, in every mode: cat .e* or ls ../* is refused when it names a secret or something outside the run's folders (before, nothing looked at it). Independent reviews of the new code (six rounds) closed the holes they found: option bundles that hid a file as the pattern (sed -nes/a/b/p .env) or carried a program (git grep -nOpager, git grep --op=cmd, git difftool -x cmd, git clone -u cmd and --up=cmd, git clone -c core.fsmonitor=cmd), options that follow links (grep -rS, rg -L, find -L, ls -LR, rsync -L, tar -h), a cd to a folder that does not exist, a .. after a link the same command makes (also behind env, xargs or find -exec, or made by tar x, unzip or code that says symlink), ~user, ~+ and ~-, which are not folders of the run, a command substitution inside ${...} (echo ${x:-$(git push)}), zsh forms (*(D), .e(n)v, ***/, setopt GLOB_DOTS, =git, $x[1,4], noglob git push, emulate zsh -c, a lone -, ${(e)x}, zmodload, autoload, functions[f]=..., the brace body of if cond { ... }), here-strings with environment variables, and a test of a path outside the run.
• The Claude CLI's own safety prompts for a redirect it cannot split, a skipped parse and the braces of a Python or Node program fed through a quoted heredoc are answered from the policy's verdict instead of ending the call; a sed program with a template literal stays a refusal that points to the Edit tool.

Changed

• The transcript says why a call was refused: one line under the refusal (the full reason on hover), "Declined by the run's rules" or "Denied by the role" instead of always the role, and a localized sentence for the Claude CLI's own prompt. A read-only role is told which commands run, and a call whose agent the Claude CLI did not name is told to run again.
• A few shapes that were allowed by accident are refused now: a path after a cd to a folder that does not exist (or after a cd that may not have run) that leaves the run's folders from the place the shell may really be in, a parenthesis stuck to a word that zsh reads as part of a glob (*(D), .e(n)v), a cd in a pipe or in the background, and a glob that matches more than 5000 files. zsh's =git is read as git, so the git hard stops apply to it.

Known limitations

• The static check still does not see the files a recursive search (grep -r ., rg --hidden) touches inside the folder it starts in, the names xargs hands to a program, a link that a script or a build tool makes (bash x.sh, make, npm install), or a secret that was once committed and is read from the history.

More

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Website: intelyhome.com

IntelyIDE 1.1.0

IntelyIDE 1.1.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.1.0_x64.dmg	The app for Intel Macs (it also runs on Apple Silicon under Rosetta 2), 16.1 MiB	39e3814b276127752dec99986d9bd621481325d05d7bbb5f3c2cb0de2da8856a
IntelyIDE_1.1.0_x64.sbom.cdx.json	Software bill of materials (CycloneDX) of what is inside the disk image	87627f9a734a9b3f1bdacb8451e038e5b2584073176a34293f14519a253fa56d
SHA256SUMS	The checksums of the files above

Install

1. Open IntelyIDE_1.1.0_x64.dmg, drag IntelyIDE to Applications, eject the image and open the app from Applications.
2. The app is signed ad hoc and is not notarized, so macOS refuses the first launch. On macOS 15 and later open System Settings > Privacy & Security, scroll to the message about IntelyIDE, choose Open Anyway and confirm. On macOS 13 and 14 right-click the app and choose Open. Do this only for a file you downloaded from this repository's Releases page.
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

Added

• Notes to a working agent. While a run works, the message box adds a note for the lead and a running subagent has its own note field. The agent reads the note with its next tool call; the transcript shows each note as queued, delivered or not delivered, and why. Claude runs only; other providers answer that they cannot take notes.
• A Usage view (command "Open Usage", and Settings > Usage): the plan limits of the Claude subscription (5-hour session and 7-day week, with the time they reset), tokens and API-equivalent cost for today, the last 7 and 30 days and all time, a daily bar chart, a year-long grid of days that is darker the more was used, the busiest days, the models, and usage by hour of the day and by weekday. It counts the runs the IDE started, from their run logs, in your own time zone.
• Sentry issues (Settings > Sentry, command "Open Sentry issues"): the issues of one organization with search, status, period, sort and project filters, event and user counts and times, an issue's newest event with its stack, and "Fix with agent" (assigns the issue to you, starts a run with the issue as its prompt, offers "Mark as resolved" when the run is done). The token is kept in the Keychain; the app reads issues and changes one only on your click.

Changed

• The website is intelyhome.com. It is the only web address besides GitHub that the project names (the contact check enforces it); the About menu, the README, SUPPORT, the issue forms and the release notes link to it. The earlier intelyide.com was never registered and is gone from every link.
• Dependencies: base64 0.23, rfd 0.17 (the folder and file pickers), rcgen 0.14 (the certificates of the test fakes) and TypeScript 7 for the phone relay. The third-party licence inventory is regenerated.

Fixed

• Three mongo tunnel tests asserted that the sweep file was empty before the entry was removed; they wait for it now.

Known limitations

• The Claude Agent SDK is not shipped with the app. Agent runs need Node.js 24 and Claude Code on the Mac, and the SDK installed once with the installer inside the app.
• The Agent SDK card in Settings > Providers does not appear yet: the app does not ask the sidecar for the state of the SDK. A run that cannot start names the command instead.
• The Sentry view follows Sentry's documented API (issues, an issue's newest event, assign, status) but has not been tried against a live Sentry server yet; please report what you see.
• The Usage view counts only the runs this IDE started, from its own run logs; the plan limits come from the signed-in Claude account and show for a subscription only.
• Notes reach Claude runs only. The phone remote does not show notes, Usage or Sentry.
• The agent protections are layered and best-effort, not a guarantee. The installed app starts in normal (writable) mode. Use it on repositories you can restore.
• Intel (x64) build only; Apple Silicon Macs run it under Rosetta 2.
• Not notarized: macOS asks you to confirm the first launch (see docs/install-macos.md). Ad-hoc builds get a new identity with every release, so macOS may ask again for Keychain and folder access after you replace the app.
• The app only tells you that a newer release exists; you replace it with the new disk image yourself.
• Some features still need files of the source tree: deploying the Remote relay, the Mongo Studio AI helper and the component preview harness.
• Experimental: providers other than Claude, Happy, MongoDB Studio and Remote are proven only against mocks or on a local machine; Remote and MongoDB Studio have not been verified against every real setup (a Cloudflare account, an iPhone, Atlas).
• The state folder is still named IntelySwitchIDE; a rename with a migration is planned.

More

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Website: intelyhome.com

IntelyIDE 1.0.1

IntelyIDE 1.0.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.0.1_x64.dmg	The app for Intel Macs (it also runs on Apple Silicon under Rosetta 2), 16.0 MiB	6bf957750e8aa2c695c0da2a6eadce724a5d7f7b9a87b944b5886d6043f519f5
IntelyIDE_1.0.1_x64.sbom.cdx.json	Software bill of materials (CycloneDX) of what is inside the disk image	cf040357154d00ab291ada2d29a4266f84cc7c43c243e02c5a0fad8717efe73f
SHA256SUMS	The checksums of the files above

Install

1. Open IntelyIDE_1.0.1_x64.dmg, drag IntelyIDE to Applications, eject the image and open the app from Applications.
2. The app is signed ad hoc and is not notarized, so macOS refuses the first launch. On macOS 15 and later open System Settings > Privacy & Security, scroll to the message about IntelyIDE, choose Open Anyway and confirm. On macOS 13 and 14 right-click the app and choose Open. Do this only for a file you downloaded from this repository's Releases page.
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

First stable release. It contains everything of the 0.1.1 that was prepared but never published, and the changes below.

Changed

• IntelyIDE is no longer labelled alpha. The README, the docs, the issue forms and the website describe a stable release; the limits that were true stay stated as plain facts (see Known limitations).
• The bundle identifier is com.intelyhome.intelyide and the Keychain services are com.intelyhome.intelyide and com.intelyhome.intelyide.mongo (the old names were built on a domain that is not part of this project). Secrets that earlier versions stored under the old service names are read once, copied to the new names and left in place; deleting a secret deletes both. The identifier also names the app's WebKit storage, so interface preferences kept there by 0.1.0 are not carried over; the settings files and the state folder IntelySwitchIDE are unchanged.
• Community files for contributions: SECURITY, SUPPORT, CONTRIBUTING and CODE_OF_CONDUCT describe the real flow (one maintainer; every pull request is reviewed and approved manually; bugs and feature requests in GitHub Issues, questions in Discussions, vulnerabilities through GitHub private vulnerability reporting), with issue forms and a pull request template. A check (release:check-contacts) fails when the tree names an e-mail address, a phone number or a web host other than the repository, intelyhome.com, intelyide.com and the listed technical references.
• One command, pnpm release, builds the disk image, writes the checksums and the SBOM, tags and publishes the GitHub release (see docs/releasing.md).
• A Rust build of the app crate needs the built sidecar (pnpm --filter @intely/sidecar build), because the bundle resources are copied on every build. beforeBuildCommand builds it for pnpm tauri build.
• CI: the JavaScript and licence jobs install remote-web and remote-relay, the gates run to the end instead of stopping at the first failure, a failed job prints the failed steps of the gate logs, and two tests that failed once in a handful of runs are re-run once.

Fixed

• Agent runs from the disk image. The agent sidecar, the Agent SDK installer and the pin files of the SDK now ship inside the app (Contents/Resources/sidecar and Contents/Resources/sdk-pin). The 0.1.0 image had no sidecar, so every run stopped at once with "the agent sidecar bundle is missing".
• The setup text of the Claude Agent SDK named a folder the app does not read (IntelySwitchIDE/sdk; the app reads IntelyIDE/sdk) and its three commands needed npm and the right working folder. A Claude run that cannot start because the SDK is missing, unverified or of another version now stops with the exact command of the installer inside the app: a plan that only lists what would be downloaded, then the install, which checks every hash and the whole file tree against the shipped list.
• The Agent SDK installer stopped with cannot write @anthropic-ai/claude-agent-sdk (ERR_ACCESS_DENIED) on Node 24.21 and later, which deny FileHandle.chmod inside the permission model the installer runs under. It sets the file modes by path now, and its tests run on both Node 24.13 and 24.21.
• The protocol package mirrored the old classification of a malformed MCP tool name and did not know the session/mcp-status messages; its tests failed.
• Tests that depended on the machine they ran on: the order of keys in a golden file when another crate turns on preserve_order, a probe script that needed sleep on its own PATH, the date notation of older git versions, the name of the temp folder on Linux.

Known limitations

• The Claude Agent SDK is not shipped with the app. Agent runs need Node.js 24 and Claude Code on the Mac, and the SDK installed once with the installer inside the app.
• The Agent SDK card in Settings > Providers does not appear yet: the app does not ask the sidecar for the state of the SDK. A run that cannot start names the command instead.
• The agent protections are layered and best-effort, not a guarantee. The installed app starts in normal (writable) mode. Use it on repositories you can restore.
• Intel (x64) build only; Apple Silicon Macs run it under Rosetta 2.
• Not notarized: macOS asks you to confirm the first launch (see docs/install-macos.md). Ad-hoc builds get a new identity with every release, so macOS may ask again for Keychain and folder access after you replace the app.
• The app only tells you that a newer release exists; you replace it with the new disk image yourself.
• Some features still need files of the source tree: deploying the Remote relay, the Mongo Studio AI helper and the component preview harness.
• Experimental: providers other than Claude, Happy, MongoDB Studio and Remote are proven only against mocks or on a local machine; Remote and MongoDB Studio have not been verified against every real setup (a Cloudflare account, an iPhone, Atlas).
• The state folder is still named IntelySwitchIDE; a rename with a migration is planned.

More

• Safety model and the limits of the agent protections: docs/safety.md
• Privacy and the network destinations of the app: docs/privacy.md
• Questions: GitHub Discussions. Bugs and feature requests: GitHub Issues. Pull requests are welcome; every one is reviewed and approved by the maintainer. Security reports: private vulnerability reporting.
• Websites: intelyide.com, intelyhome.com

IntelyIDE 0.1.0 (alpha)

First public release. This is alpha software: use it on repositories you can restore.

Download

• IntelyIDE_0.1.0_x64.dmg for Intel (x64) Macs. It also runs on Apple Silicon under Rosetta 2.
• SHA256SUMS holds the checksum of the disk image. Verify it with shasum -a 256 -c SHA256SUMS. The checksum detects a damaged download; it does not prove who made the file.

Install

The app is signed ad hoc and is not notarized, so macOS asks you to confirm the first launch. The steps are in docs/install-macos.md. Agent runs also need Node.js 24 or newer, your own Claude Code login and the Claude Agent SDK; see docs/getting-started.md.

What is in this release

Added

• Multi-repository Changes tree with tri-state selection, shared or per-repository commit messages, per-repository commit and push, a push preview, and typed confirmation for pushes to live branches.
• Git tools: hunk staging, log, blame, branch graph, split and unified diff, rebase, cherry-pick, stash and rollback.
• Coding-agent runs through your own Claude Code installation, with five permission modes (Plan, Ask, Accept edits, Automatic, Bypass), an approval drawer, per-role model and effort, an Automatic mode with a lead agent and delegates, History and an Inspector.
• Agent runs that follow the Claude Code experience: a / menu in the composer (/mcp, /agents, /mode and the commands and skills your Claude Code installation reports), an MCP chip in the run header with the live state of each server and a reconnect action, a Continue button when a run reaches its step limit, and your own global ~/.claude/CLAUDE.md read into every run (a switch in Settings > Roles). Sub-agents always run inside the turn, so Stop and the approval cards work at every point of a plan.
• Layered, best-effort protections that fence agents off from committing and pushing: policy hard stops on tool calls, host-side checks, a git shim, a read-only test jail and an enforcement suite you can run on your machine (see docs/safety.md).
• Rewind: a snapshot of the working tree before each agent run, with a restore action per repository.
• Workspaces with a Welcome screen, a folder picker and repository scanning.
• A small built-in editor, a project tree, a terminal, and a preview with an element inspector.
• 53 interface languages. English and Hungarian are hand-written; the other 51 are machine-translated and await native review. Some newer screens are not translated yet and show English there.
• Optional modules, off by default: Remote (a phone view through a relay you deploy on your own Cloudflare account), MongoDB Studio, an integrations module for one company's services (time tracker, chat, tasks) and other agent providers.
• An open-source licenses view and GPL-3.0-or-later notices.
• A macOS disk image for Intel (x64) Macs, ad-hoc signed and not notarized. It runs on Apple Silicon under Rosetta 2.
• A new-version notice: once a day, after a one-time notice, the app asks GitHub for the latest release and links to its page (Settings > Updates, with an off switch). It does not download or install anything.
• No telemetry. A script in the repository checks this claim (pnpm release:no-telemetry).

Known limitations

• Alpha: the installed app starts in normal (writable) mode, and the agent protections are best-effort, not a guarantee. Use it on repositories you can restore.
• Intel (x64) build only; no native Apple Silicon build yet.
• Not notarized: macOS asks you to confirm the first launch (see docs/install-macos.md).
• The app only tells you that a newer release exists; you replace it with the new disk image yourself. Verified in-app updates are planned.
• Some features still need files of the source tree and therefore work only in a build from source: agent runs (the agent sidecar is not in the disk image), deploying the Remote relay, the Mongo Studio AI helper and the component preview harness. Everything else, including the Git features, the editor, the terminal, the preview and workspaces, works from the disk image.
• The Claude Agent SDK is not shipped with the app and is installed by you under Anthropic's terms.
• Providers other than Claude, Happy, MongoDB Studio and Remote are proven only against mocks or on a local machine.
• Version 0.1.0 still stores its state in the folder IntelySwitchIDE and uses Keychain services named after the earlier bundle identifier; a switch to com.intelyhome.intelyide with a migration is planned.