Icarus · macOS · alpha
I · The ascent
Ask why your code is the way it is. Icarus answers from your repository's own pull requests and issues, shows the evidence, and says "no one wrote this down" when nobody did.
II · Too near the sun
The part nobody else demos
Other assistants guess, confidently, and never say it was a guess. Icarus refuses instead — and the refusal is enforced by code, not by asking a model nicely.
A reason that was recorded
Why does requests not support HTTP/2?
HTTP/2 is a complex protocol, and it is unlikely that Requests will achieve good support for it in its current form anytime soon. Additionally, support is likely blocked by the lack of HTTP/2 support in the underlying urllib3 library.
A reason that was never recorded
Why is the redirect limit 30?
Honest unknown
No one wrote this down.
searched: doc:docs/user/quickstart.rst#L496–L573, code:tests/test_requests.py#L262–L275, code:src/requests/exceptions.py#L106–L107, issue:7209, code:tests/test_requests.py#L251–L260, issue:6942, issue:7248, issue:6481, issue:6946, issue:6981, pr:7501, code:src/requests/sessions.py#L186–L307, issue:6758, issue:6407, issue:6784, issue:6471, pr:7487, issue:7020, issue:6546, issue:6723
III · The wings
Sign in with GitHub, point Icarus at a repo. It indexes source, pull requests and issues — 22 file types, ~17 languages.
Hold Right Option anywhere on your Mac and speak, or press ⌘⇧I to type.
A one-line spoken answer, with the quoted evidence on screen linked to the exact lines on GitHub. Or nobody recorded a reason, and it says so.
IV · The wax
A tool that hides its limits is asking to be trusted rather than checked.
V · What he carried
VI · The descent
Four steps, about two minutes. Not notarized — that needs a paid Developer ID this alpha does not have — so every install path is below with the checksum, and you can verify the download yourself.
Get started · macOS, Apple Silicon · ~2 minutes
Download the .dmg below, or use one of the terminal paths that follow.
Open Icarus, click "Sign in with GitHub." Asks for your identity only — nothing else, yet.
Type owner/repo and press Connect. Icarus indexes it — seconds to a few minutes.
Settings → Connect, approve Keychain access. Skip if you don't use Claude Code.
Terminal — recommended
curl -fsSLO https://icarus-website-kappa.vercel.app/install.sh less install.sh # ~100 lines, half of them comments — read it sh install.sh
Or with Homebrew
brew install --cask alankritxghosh/icarus/icarus xattr -dr com.apple.quarantine /Applications/Icarus.app
Or the disk image, by hand
1. Download Icarus.dmg below and open it
2. Drag Icarus onto the Applications folder beside it
3. Open Icarus. macOS says it "cannot be opened because Apple
cannot check it for malicious software" — this is expected
4. System Settings → Privacy & Security, scroll down, then
click "Open Anyway" beside the Icarus message and confirm
VII · A second pair of wings
Optional. Select lines in a file on GitHub, ask what they do or why they are there, get the same cited answer or the same honest unknown without leaving the page.
1. Download icarus-extension.zip below and unzip it
2. Open chrome://extensions and turn on "Developer mode"
3. Click "Load unpacked" and choose the unzipped folder
4. Click the Icarus toolbar icon, then "Connect Mac app"
(or "Sign in with GitHub" if you don't have the app installed)
VIII · What your agent cannot see
A merged pull request leaves a commit. A refused one leaves nothing — so git log,
git blame and the working tree are blind to every change your team tried and closed.
Your agent reads exactly those three. Icarus reads the rest.
Claude Code
claude mcp add --transport stdio --scope user icarus -- /Applications/Icarus.app/Contents/MacOS/Icarus --mcp
The config
{
"mcpServers": {
"icarus": {
"type": "stdio",
"command": "/Applications/Icarus.app/Contents/MacOS/Icarus",
"args": ["--mcp"]
}
}
}
Repair and permissions