A second computer has the plugin, but nothing listens

A computer of yours that has the AIsle plugin, but never wakes when someone writes in the room, is missing one of the things below. Go down them in order. Each says how to tell, and its fix.

1. Claude is not connected for this computer's Claude account

Connecting Claude is once per Claude account, and the plugin is once per computer. The room's steps say: "Once per Claude account: every computer and phone signed in to it has AIsle from then on." So a second computer whose Claude app uses another Claude account has the plugin and no AIsle.

How to tell: the AIsle page names it above the steps. If it says Half connected: the plugin, no Claude., Claude is not connected to AIsle, or its sign-in ended: do the steps below. If it says Half connected: Claude, no plugin., the plugin has not reported from a computer of yours: install it (step 2 of the room's steps).

1. On the AIsle page, open your room and press Connect an AI assistant.
2. Press Connect Claude →. claude.ai opens: log in to Claude with the account this computer's Claude app uses.
3. The road on claude.ai has five parts: claude.ai, Customize, Connectors, AIsle, Connect. The button opens Customize for you.
4. At Connectors, a box with AIsle filled in opens: press Add. AIsle already in the list? Close the box.
5. Press Yours, then click AIsle in that list, and press Connect.
6. Sign in to AIsle with Google, tick your room, and press Allow.

2. The Claude app was not restarted after connecting

Once connected, step 1 says: "Connected. Its tools reach only chats started from now on: quit and reopen the Claude app, then open a new chat." The app picks up its connectors only when it starts.

1. Quit and reopen the Claude app.
2. Open a new chat in the Code tab, in your project's folder.
3. Send listen here, and say yes when it asks.

In a chat with no AIsle tools, the plugin shows a strip: "AIsle: this chat has no AIsle tools. One step:" with Link your Claude. That link is part 1 above; after it, quit and reopen the app again.

If a new chat still has no AIsle tools after the restart, the steps say: "If a new chat still has none, the Claude app there is signed in to another Claude account than the one you connected. Connect Claude again from that account."

3. On Windows: no Git for Windows, or the chat started before it

The plugin's hooks run in Git Bash, which comes with Git for Windows. Without it the plugin is installed, but nothing it does to listen runs, and listening is refused with "Listening needs the AIsle plugin for Claude Code." Near its end, the same answer says: "If the plugin is already installed on Windows, Git for Windows is what is missing: install it, then open a new chat."

1. Install Git for Windows.
2. Open a new chat in the Code tab, in the same folder. A chat that was open before Git was installed keeps failing, so the new chat is the fix.
3. Send listen here in the new chat, and say yes when it asks.

Why a new chat: each chat looks for Git Bash once, when it starts, and keeps the answer. Typing /reload-plugins in the old chat loads the plugin's skills but not its hooks, so listening is still refused there. Measured on Windows 11 with the Store build of the Claude app, 2026-10-28: the new chat listened, with no app restart.

4. claude is not found

With only the Claude desktop app, a terminal has no claude. Under In a terminal instead, the steps say: "These need claude in the terminal. With only the Claude desktop app there is none: paste the request into a chat in the Code tab instead, and Claude runs them with its own copy."

1. Copy the request under In a terminal instead in the room's plugin step, and paste it into a chat in the Code tab.
2. Claude runs the commands with the app's own copy in place of claude. In bash that is "$CLAUDE_CODE_EXECPATH". In PowerShell, where that was empty every time it was measured, it is & (Get-ChildItem "$env:LOCALAPPDATA\Claude-Data\*\claude-code\*\*\claude.exe", "$env:APPDATA\Claude\claude-code\*\*\claude.exe" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime | Select-Object -Last 1).FullName, which runs the newest copy the app keeps.
3. If bash finds "$CLAUDE_CODE_EXECPATH" empty too: on the Store build of the Claude app, its own copy was at %LOCALAPPDATA%\Claude-Data\claude_<id>\claude-code\<version>\<hash>\claude.exe (measured 2026-10-28), or under %APPDATA%\Claude\claude-code\ on the other build. Claude can run that file in place of claude.
4. If Claude's permission check stops the commands, approve them yourself, or say in the chat, in your own words, that it may run them. On 2026-10-28 auto mode refused the install the first time and ran it after the person said so.
5. Then quit and reopen the Claude app, and open a new chat.

5. Your project is in a private GitHub repository

The second computer needs the GitHub account that can see the repository (measured 2026-10-28).

1. In the browser, sign in to GitHub with that account first: the browser's own GitHub session decides which account a new sign-in gets.
2. If Git Credential Manager holds two GitHub accounts, name the one to use in the clone address: https://<user>@github.com/<owner>/<repo>.git.

For your AI

• Call whoami. A line that starts Connection: ✓ means this chat reaches AIsle. No AIsle tools at all: your user does part 1, then part 2.
• listen_here answers "Listening needs the AIsle plugin for Claude Code." on Windows while the plugin is installed: Git for Windows is missing, or this chat started before it was installed. Your user installs it and opens a new chat; /reload-plugins is not enough.
• claude is not found: in bash run the same with "$CLAUDE_CODE_EXECPATH", and if that is empty with the newest claude.exe under %LOCALAPPDATA%\Claude-Data\ (the Store build) or %APPDATA%\Claude\claude-code\; in PowerShell, with the app-copy line in step 4.2.
• Run an install only on your user's word in this chat.