FredrinThe setup checklist will not go green
The preflight probes each prerequisite and reports a detected version. A red row is a genuinely missing tool, not a false alarm.
Git-Bash on Windows is the most common one. Install Git for Windows and make sure Git-Bash is included: it ships in the default install but is easy to untick, and without it Fredrin falls back to cmd.exe, which corrupts the commands agents run.
jq missing fails ticket completion specifically, so it looks like a Worker problem rather than a setup problem.
An agent CLI missing means no Worker can start at all.
Cloning a repository fails
Fredrin inherits your GitHub CLI configuration, including its git protocol.
If gh is configured for SSH and this machine has no known-hosts entry for GitHub, the clone fails at host verification, before authentication is ever attempted. The error usually names host key checking rather than credentials.
Either add the host key by making one manual SSH connection to GitHub, or switch gh to HTTPS.
This matters more than it sounds: a new user with no projects cannot get past onboarding until one clone succeeds.
A ticket says it is running but nothing is happening
Three different situations that look identical from the board. When a Worker stops covers all three, but briefly:
- It is waiting for you. Open the chat tab; an unanswered question is right there.
- It is waiting at an approval gate. The card shows gate progress.
- Its session died. Fredrin offers recovery: resume, or reset the build.
A port is already in use
Fredrin can start your dev servers, and a server left running from a previous session holds its port.
The servers panel lists what is running and can stop it. If a process outside Fredrin holds the port, Fredrin will tell you rather than silently picking a different one.
Windows says "unknown publisher"
Not a signing failure. See install.
A Worker is doing the wrong thing
Do not wait for it to finish. Talk to it: anything you send lands in its live session and it adapts. Correcting mid-run is much cheaper than reviewing a wrong diff and sending it back.
If it is fundamentally off track, Reset build clears the ticket's jobs and conversation and returns it to the backlog, which also unlocks the model picker so you can try a different one.
Still stuck
Get in touch. Include what the ticket was, which runtime it was on, and what the chat tab showed.
Next steps
- When a Worker stops - the three stall shapes.
- Install - prerequisites in full.