Troubleshooting
The fixes below are grouped by what’s going wrong: viewing the board on other screens, connecting your Claude Code sessions, and installing the app. If none of them help, email help@glanceable.com and tell us exactly what you see.
Everything here stays on your Mac: board views are served only across your local network, never through our cloud. More in Trust.
Viewing the board on other screens
The board won't open on my TV, iPad, or phone#
On another device, localhost means that device, not your Mac. Open the hub menu, and under Live board choose Copy address for other screensto copy your board’s address, or Show QR for other screens to scan it from a phone. Then open that address on the TV, iPad, or phone. Both devices must be on the same Wi-Fi network.
Other devices still can't reach the board#
On first launch, macOS asks to allow local-network access. That’s the hub serving your board. If you dismissed or denied it, no other device can connect. Open System Settings › Privacy & Security › Local Network, turn Glanceable Hub on, then quit and reopen the hub.
The Mac firewall is blocking the board#
If your Mac’s firewall is on and blocking incoming connections, port 8787 won’t be reachable from other devices. Open System Settings › Network › Firewall › Options and make sure Glanceable Hub is allowed to accept incoming connections. The hub only ever serves your local network.
Port 8787 is already in use#
If another app is already using port 8787, the board won’t start. Find what’s using it, quit that process, then reopen the board:
lsof -i :8787Connecting your Claude Code sessions
The board says “No sessions running” after I connected#
The hooks apply when a Claude Code session starts, so an already-open session won’t report until it restarts. Start a new Claude Code session, or quit and reopen the one you have, and your session should appear within a few seconds.
I see hook errors in my terminal#
Open the hub menu (the G in your menu bar) and choose Claude Code › Reconnect / repair. That rewrites the hooks cleanly. If the errors continue, choose Disconnect Claude Code, then connect again.
Connecting fails with “python3 not found”#
The hooks run on Python 3, which comes with Apple’s developer tools. Install them once by running this in Terminal, then connect again:
xcode-select --installMy sessions are on a different Mac#
Each hub watches the Claude Code running on the same Mac. If you run Claude Code on another machine, install and connect the hub there too. One hub for many machines is on our roadmap.
“LLM verdict (Apple Intelligence)” is greyed out#
The AI-phrased verdict only applies to Glance view, so LLM verdict (Apple Intelligence) is greyed out while you’re in Detail view. It runs on Apple Intelligence on-device; on a Mac without it you get the plain state sentence instead. The board works fully either way.
Installing and opening the app
macOS won't let me open the app#
Glanceable Hub is signed and notarized, so this is rare. If macOS says it can’t verify the app, open System Settings › Privacy & Security, scroll to Security, and choose Open Anyway next to Glanceable Hub, then confirm once. You should only ever have to do this on first launch.
How do I undo the connection?#
In the hub menu, choose Claude Code › Disconnect Claude Code. It removes Glanceable’s hooks and status line from your Claude Code settings and leaves everything else as it was. Your settings are backed up first, and Reveal settings backup in the same menu opens the backup in Finder.
I deleted the app but still see hook errors#
The hooks live in your Claude Code settings, not in the app, so deleting the app leaves them behind. The easiest fix is Uninstall Glanceable Hub, the app sitting next to the hub in the disk image you installed from. It removes the hooks, the status line, and the hub’s own data, and it needs no Terminal. If you still have the hub itself, Claude Code › Disconnect Claude Code does the settings half of the same job.
If you have neither, paste this into Terminal. It backs up your settings first, puts back any status line of your own that the hub had replaced, and leaves every other entry alone. It won’t remove the hub’s data folder, which the uninstaller does.
python3 - <<'PY'
import json, os, datetime
p = os.path.expanduser("~/.claude/settings.json")
if not os.path.exists(p):
raise SystemExit("No settings.json at " + p + ", so there is nothing to clean.")
try:
d = json.load(open(p))
except ValueError as e:
raise SystemExit("REFUSING to touch " + p + ": it does not parse as JSON (" + str(e) + "). Fix the file first.")
open(p + ".glclean-backup." + datetime.datetime.now().strftime("%Y%m%d_%H%M%S"), "w").write(open(p).read())
for ev in list(d.get("hooks", {})):
d["hooks"][ev] = [e for e in d["hooks"][ev] if "command-center-v0" not in json.dumps(e)]
if not d["hooks"][ev]:
del d["hooks"][ev]
if not d.get("hooks"):
d.pop("hooks", None)
sl = d.get("statusLine")
if isinstance(sl, dict) and "command-center-v0" in str(sl.get("command", "")):
# The hub keeps whatever status line it replaced. Put it back rather than
# deleting it along with ours, and never leave the bookkeeping key behind.
prev = d.pop("statusLineReplacedByCommandCenter", None)
if prev is None:
d.pop("statusLine", None)
else:
d["statusLine"] = prev
else:
d.pop("statusLineReplacedByCommandCenter", None)
json.dump(d, open(p, "w"), indent=2)
print("Cleaned. Restart your Claude Code sessions.")
PYThen restart your Claude Code sessions.
Still stuck? Email help@glanceable.com.