Fredrin
Log in
The agent developer environment

Harness your agents.
Ship in parallel.

You spent the year babysitting one Cursor tab while Twitter founders out-launched you. Fredrin gives every ticket its own agent harness — branch, worktree, and session — so ten ship in parallel while you sleep.

Download for MacOpen source on GitHub

free · BYOK · macOS 13+ · apple silicon + intel

10×

tickets in parallel.
One human.

Review = glance & ship

Look at the diff, ship it or send it back. Merge auto-completes the ticket.

fredrin · solo-empire3 agents · 3 branches · 1 human
Planning1
PLAN-104queued

Stripe webhook for churn

Building3
PLAN-101agent

Onboarding email sequence

PLAN-102agent

Landing copy A/B test

PLAN-103agent

Supabase migration

Review1
PLAN-099PR ready

Add referral codes

GitHub-wired tickets

Branches, PRs, and CI status flow straight back to the board.

BranchPRCI status
Features

Built for throughput, not one-tab babysitting

Fredrin handles the harness engineering—branches, worktrees, and isolated sessions—so you can drop tickets, run agents in isolation, and ship without waiting on a single terminal.

  • Parallel shipping

    One ticket, one Worker. Throughput comes from running many lanes at once—not fanning a single prompt.

  • Isolated worktrees

    Every ticket gets its own agent harness—a dedicated branch and worktree—so agents never step on each other's changes.

  • Real-time kanban

    Live multiplayer board via Ably—simultaneous editing, live status, no stale columns.

  • Keyboard-first UX

    Full keyboard navigation and a cmd-K palette—every action in milliseconds, no mouse required.

  • GitHub-wired tickets

    Branches, PRs, and CI status flow back to the board. Merge auto-completes the ticket.

  • BYOK

    Bring your own API keys. You control the meter—no vendor lock-in on model spend.

See it in action

From backlog to shipped, on one screen

A look at the surface where you drop tickets, run agents in isolation, and ship—without ever leaving the board.

The board

Every ticket runs in its own lane

Drop work into the kanban and watch agents pick it up in parallel—each ticket on its own branch and worktree, so nothing collides.

fredrin · solo-empire
Planning1
PLAN-104queued

Stripe webhook for churn

Building2
PLAN-101agent

Onboarding email sequence

PLAN-102agent

Landing copy A/B test

Review1
PLAN-099PR ready

Add referral codes

The Worker

Watch an agent build, live

Open any running ticket to follow its Worker session in real time—plan, edits, and commits stream in as the agent ships.

PLAN-102 · landing copy A/B test
Landing copy A/B testWorker running
  • Reading landing-copy.tsx and variants config
  • Edit landing-copy.tsx · +18 −4
  • Edit experiments.ts · +6 −0
  • Wiring A/B assignment into the hero
  • Committed: feat(landing): add headline A/B test

The review

Glance the diff, then ship

When a ticket lands in Review, you skim the PR and either ship it or send it back. Merge auto-completes the ticket.

PR #418 · add referral codes
src/server/checkout.ts+3−1
export function checkout(cart: Cart) {
const total = sum(cart.items);
const code = cart.referralCode;
const total = applyReferral(sum(cart.items), code);
return total;
CI passed
Send backShip it
Compare us with others

One surface beats three tabs

Fredrin collapses the Cursor + Linear workflow into one agent developer environment—a kanban built for parallel AI shipping, not babysitting one agent at a time.

Feature comparison of Fredrin versus Cursor alone, Linear, and Cursor plus Linear
CapabilityFredrinParallel AI shipping in one surfaceCursor aloneOne IDE agent, one tab at a timeLinearIssue tracking, no AI workersCursor + LinearThe stack you stitch together today
Parallel AI agents (one per ticket)YesNoNoPartial
Isolated git worktree per ticketYesPartialNoPartial
Kanban board tuned for agent throughputYesNoPartialPartial
GitHub PR + CI status on the ticketYesPartialPartialPartial
Real-time multiplayer boardYesNoYesPartial
BYOK (your API keys)YesPartialNoPartial
Review = glance diff and shipYesPartialNoPartial
Roadmap

Where Fredrin is headed

What's shipping today, and what's next as we push parallel AI shipping further.

Shipping now

10 live
  • Parallel shipping
  • Isolated worktrees
  • Real-time kanban
  • Keyboard-first + cmd-K
  • GitHub PR + CI tickets
  • BYOK
  • Project Context
  • Per-ticket token usage
  • Embedded terminals
  • Desktop auto-update

On the roadmap

9 planned
  • Next

    Cloud agents

    Run Workers on Fredrin's hosted compute—no local machine tied up babysitting a build.

  • Next

    Better planning sessions

    Richer plan drafting—scoped action items, clarifying questions, and revisable plans before a Worker runs.

  • Next

    Throughput analytics

    Ship-rate, cycle time, and tickets-in-flight—measure the throughput Fredrin is built to optimize.

  • Next

    Merge queue & auto-merge

    Auto-merge green PRs through a queue—extend “glance the diff, then ship” to zero clicks.

  • Later

    Remote agents via SSH / Openclaw

    Point a ticket at any box over SSH—or Openclaw—and let its Worker build there.

  • Later

    Team support

    Multi-seat workspaces—shared boards, roles, and assignment beyond today's invitations.

  • Later

    Context Pack marketplace

    Install portable Project Context bundles—conventions, ADRs, glossary—into any project via PR.

  • Later

    Hosted compute tier

    Managed keys and compute for builders who'd rather not bring their own.

  • Later

    Windows & Linux apps

    Native desktop builds beyond macOS, so any machine can run the cockpit.