Troubleshooting
What to check when sync stalls, a review will not start, sign-in fails or a page stays empty.
On this page
Most problems have a short message in the app or the terminal that names the cause. Find the message or the symptom below. Limn prints its own log in the terminal where you started it, which is the first place to look when something fails without a message.
#Limn will not start
“GitHub CLI not found or not authenticated.”
- Install the GitHub CLI from
cli.github.com. - Run
gh auth login, thengh auth statusto check. - Start Limn again.
The port is already in use
Another program, or another copy of Limn, is using port 4000. Stop it, or start Limn on another port with npx limn-review --port 4100.
An old Node.js
Limn needs Node.js 22 or later. Check with node --version.
#Sync is slow or paused
“Paused — GitHub rate limit”
GitHub limits how much each account can ask for in an hour. Limn waits instead of failing, and the line says when it will carry on. Nothing is lost; the sync resumes by itself. If you also run other tools on the same GitHub account, they share the same hourly allowance.
“Waiting for another sync…”
Limn syncs one repository at a time when you add several. The rest wait their turn.
The first sync takes a while
A new repository syncs the last 14 days first, so you can start work, then fills in the rest of the 90 days in the background. A busy repository with thousands of pull requests can take some time. Reports appears once a repository has finished its 90 days.
Something on GitHub has not shown up
Limn checks GitHub every few seconds for busy repositories and less often for quiet ones. A pull request you have open in Limn refreshes every few seconds. To force a full refresh of a repository, use its Deep re-sync button in Manage repos & workspaces.
#The AI features are not ready
“Setting up AI…” or “The download failed.”
Limn downloads Claude and Codex the first time it starts. Wait for it to finish. If it failed, select Retry on the AI tab, or run limn ai install in a terminal and read its message. limn ai status says whether it is set up. A firewall that blocks the npm registry stops the download.
“Sign in to Claude Code or set ANTHROPIC_API_KEY.”
Run claude in a terminal and sign in, or start Limn with an Anthropic API key. Restart Limn if you set the key after it started. See Claude (Anthropic).
Codex reads “Not signed in.”
Select Sign in with ChatGPT on the AI tab, or run limn ai login codex. Your own Codex sign-in does not count: Limn uses its own. See Codex (OpenAI).
The AI tabs and buttons are missing
Limn was started with the AI features turned off (LIMN_AI_DISABLED=true). Start it without that setting.
#An automatic review did not run
- Check that Review new PRs automatically is on for that workspace. It covers only pull requests opened after you turned it on.
- Drafts wait until they are marked ready. Pull requests opened by bots are skipped.
- The workspace may have reached its daily limit of auto reviews (20 by default). The rest run the next day (UTC).
- Limn may have used its share of your week: a message says when automatic runs resume. See When Limn’s share is used.
- A teammate’s Limn may already be reviewing that commit with the same provider.
If a review ran but did not post, the AI Review tab says why and keeps the Post button. When a post reports that it is on GitHub but not visible yet, wait: it will show up shortly. Do not post it again.
#AI Fix or Implement will not start
“No container runtime is running on this computer.”
- Install and start a container runtime: Colima on a Mac, Docker Engine or Podman on Linux, Docker Engine in WSL2 on Windows.
- Give it at least 8 GB of memory.
- On the Sandbox tab, select Check again.
To use Podman, start Limn with SANDBOX_CLI=podman. Step-by-step setup: Docker and microsandbox.
A build in the sandbox cannot download packages
The sandbox reaches only allowed hosts. Open the session’s Network list and select Allow for this session or Always allow on the blocked host.
The disk is filling up
Stop Limn and run limn sandbox prune. Add --dry-run to see what it would remove first.
Sandboxes keep running
A session with nothing to do closes after 15 minutes, and its sandbox goes with it. To stop them all now, select Stop all in Settings → Sandbox.
#Bot comment scoring
Scoring needs a one-time download of about 240 MB. Select Set up (one-time ~240 MB download) on the Bots tab, or run limn ml install; limn ml status checks it. Scoring is slow on purpose so it never slows your computer, and it pauses while your computer is on battery, so a backlog of comments can take a while.
#A page is empty or missing
- Everything is empty: the current workspace may have no repositories. Add some, or switch workspace. See Add your repositories.
- Reports is missing: it appears once your first repository has finished syncing 90 days.
- This Sprint is missing: it appears once a Jira, Linear or Notion tracker is set up, or Limn finds a GitHub milestone with a due date or a current Projects iteration.
- A page you hid: switch it back on in Features.
- Tickets show no details: the tracker needs read access. See Integrations settings.