Question 1

What is Fredrin?

Accepted Answer

Fredrin is an agentic development environment for vibe coding, a vibe coding ADE. Every ticket gets its own git branch, worktree, and AI agent, so one person can run a whole board of work in parallel.

Question 2

Does Fredrin replace Claude Code, Codex, or my editor?

Accepted Answer

No. Fredrin doesn't reinvent the powerful TUIs you already love. Claude Code, Codex, and your shell run exactly as they are, live in every ticket. Fredrin is the glue that ties them together with a board, isolated worktrees, and PRs, so you keep the tools you know and skip the app-switching between them.

Question 3

How do I sign up?

Accepted Answer

Signup is open — there is no invite code and no waiting list. Download Fredrin for macOS, Windows or Linux, sign in with GitHub or an emailed link, and you are in. The old invite wall was removed because it turned away more people mid-signup than the waiting list behind it ever converted.

Question 4

How much does Fredrin cost?

Accepted Answer

Nothing to get started: signup is open and every new account lands on the Free plan at $0. The Pro plan is $20 per month if you outgrow it.

Question 5

Do I need a separate AI subscription?

Accepted Answer

No. Fredrin runs on the AI coding subscription you already pay for, so agents use your existing plan instead of a separate metered bill.

Question 6

Do I have to pay for private repos?

Accepted Answer

No. The Free plan your invite unlocks includes a private repo and project memory, with no card on file. Pro adds unlimited private repos and projects for $20 per month: a flat monthly plan per workspace, never per repo, so there's no metered repo charge or surprise invoice line.

Question 7

How do parallel agents avoid conflicting with each other?

Accepted Answer

Each ticket runs on its own branch inside its own git worktree, so agents work in isolation and never overwrite one another's changes.

Question 8

Can a Worker mess up my repository?

Accepted Answer

No. Every ticket runs in its own branch and worktree, an isolated working copy, so a Worker never touches your main branch or another ticket's work. Changes come back as a pull request you glance at in the Review column and either ship or send back. Nothing reaches your base branch until you merge, and merging is what auto-completes the ticket.

Question 9

What happens when a PR's build fails?

Accepted Answer

Each Worker runs its plan's acceptance checks as its final act and reports the real exit codes, which stamp CI status on the board's PR pill. If a check goes red, the ticket is flagged needs-work and the failing checks are written into the PR body. The PR still opens, so you can read the diff and the failure together. Send the ticket back with a chat message describing the fix. That resumes the Worker, which picks up your feedback and re-runs the checks until the build is green.

Question 10

Which platforms does Fredrin run on?

Accepted Answer

Fredrin is a desktop app for macOS, Windows and Linux: macOS 13+ on both Apple Silicon and Intel, Windows 10+ (x64), and Linux on x64 as an AppImage — make it executable and run it, no package manager needed. The board itself runs against your own GitHub repositories, so your code and Project Context always stay in your repos.

We ship Fredrin from a Fredrin board

Finally, an app for vibe code teams

Used by developers from

Run unlimited agents in parallel

Run your agents from anywhere

Turn every ticket into an AI workflow

Build together, in real time

Go from conversation to execution

Turn big goals into autonomous execution

Plan tickets hands-free

Try it now

Start shipping in parallel

We ship Fredrin from a Fredrin board

Finally, an app for vibe code teams

Used by developers from

AWS

Google

Microsoft

Tesla

Corgi

SeatGeek

Whatnot