Connection Diagnostics
Step-by-step guide to diagnose connection and latency problems.
When things aren't working, random retries waste time. Use this sequence to isolate the problem.
Step 1: Classify the symptom
| Symptom | Likely cause |
|---|---|
| Can't connect at all | Network or endpoint misconfiguration |
| Connects but terminal is slow | Network latency or Mac under load |
| Connects but output is stale | Session state issue |
| Notifications missing | Hook delivery or iOS permissions |
Step 2: Check the server
On your Mac, verify the server is listening:
You should see a node process. If nothing appears, the server isn't running.
If using Cloudflare Tunnel, also check:
Step 3: Test network reachability
From another device on the same network (or your Mac itself):
If the port isn't reachable, check:
- Mac firewall settings
- The correct network interface (
en0for WiFi,en1for Ethernet) - Whether devices are on the same subnet
Step 4: Check Mac performance
If the connection works but feels slow:
A Mac under heavy load will delay terminal output, making it look like a network problem.
Step 5: Refresh the session
If output looks stale or the terminal is blank:
- Open the session selector in the iPhone app.
- Re-select the session.
- This re-attaches to the tmux session and refreshes output.
If the session no longer exists (deleted or server restarted), create a new one.
Step 6: Check notification delivery
If push notifications aren't working:
- iOS permissions: Settings > Tactic Remote > Notifications > Allow.
- Hook events: Claude Code fires hook events that the server relays. Make sure the server is receiving them:
- App version: Make sure both the Mac app and iOS app are on the latest version.
When to open a support issue
If none of the above resolves the problem, contact support with:
- App version (Mac and iOS)
- Connection mode (Local or Tunnel)
- Steps you tried
- Screenshots or error messages (redact any API keys)