Questions, answered
The things builders ask before they download: costs, safety, and what's supported.
Showing all 10 questions
What is Fredrin?
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.
Does Fredrin replace Claude Code, Codex, or my editor?
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.
How do I get an invite?
Fredrin is invite-only while we scale, so there is no self-serve signup. Request an invite with the form on the homepage and that puts you in the queue. Invites go out as we open up capacity, and yours arrives by email at the address you requested with. We would rather not promise a wait time we cannot keep, so we do not publish one.
How much does Fredrin cost?
Nothing to get started once you are in: Fredrin is invite-only while we scale, and the plan your invite unlocks is the Free plan at $0. The Pro plan is $20 per month if you outgrow it.
Do I need a separate AI subscription?
No. Fredrin runs on the AI coding subscription you already pay for, so agents use your existing plan instead of a separate metered bill.
Do I have to pay for private repos?
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.
How do parallel agents avoid conflicting with each other?
Each ticket runs on its own branch inside its own git worktree, so agents work in isolation and never overwrite one another's changes.
Can a Worker mess up my repository?
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.
What happens when a PR's build fails?
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.
Which platforms does Fredrin run on?
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.
Still got a question? The fastest answer is a repo and an afternoon.