Repository navigation
IntelyIDE 1.0.1
·
65 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
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
- Open
IntelyIDE_1.0.1_x64.dmg, drag IntelyIDE to Applications, eject the image and open the app from Applications. - 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.
- 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--planfirst 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.intelyideand the Keychain services arecom.intelyhome.intelyideandcom.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 folderIntelySwitchIDEare 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.beforeBuildCommandbuilds it forpnpm tauri build. - CI: the JavaScript and licence jobs install
remote-webandremote-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/sidecarandContents/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 readsIntelyIDE/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 denyFileHandle.chmodinside 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-statusmessages; 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 neededsleepon 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