Skip to content
Fredrin
Documentation

Get started

Fredrin documentation

Fredrin is a desktop app for running many AI coding agents at once: every ticket gets its own branch, its own worktree, and its own agent session. These docs cover the whole loop, from installing the app to shipping a pull request, and the concepts underneath it.

What is an agentic development environment?

An agentic development environment (ADE) is a workspace built for coding with AI agents at its center, where planning, execution, project context, and review all live on one surface instead of being scattered across a chat window, a terminal, and a separate issue tracker. It treats the agent as the primary way work gets done and wraps the whole loop, from an idea to a reviewed pull request, in a single tool.

Fredrin doesn’t compete with your agent: it works alongside Claude Code, Codex, and the shell you already use, and gives every ticket its own branch, worktree, and agent session. Instead of babysitting one terminal, you run a whole board of work in parallel and stay in command of what ships.

It is one shape among a wider field: see how the AI coding tools compare to place it against the editors, builders, and agents around it.

FIG 0.1 · One surface

The loop

Everything in Fredrin serves one cycle. It is worth reading once, end to end, before anything else.

FIG 0.5 · Install to merge

  1. 01You file a ticket

    One unit of work, described the way you would brief an engineer who does not know the codebase. The description is the prompt.

  2. 02Fredrin gives it a lane

    A branch, a real git worktree, and an AI agent session that belongs to this ticket and nothing else.

  3. 03The Worker builds it

    It reads the project context relevant to this ticket, does the work, and commits. You can watch, or leave. Meanwhile the next ticket is already running in its own lane.

  4. 04You read the diff

    The ticket lands in Review with its diff, its plan, its acceptance checks, and its pull request. Ship it, or send it back and the same session picks up where it left off.

  5. 05Merging completes it

    The pull request merges, the ticket moves itself to Completed, and anything the Worker learned along the way is proposed back into project memory.

The part that changes how you work is that this loop runs many times at once. Running a ticket covers what one lane does; review and merge covers the half that is still yours.

FIG 0.3 · Parallel lanes

Core concepts

Five ideas explain how everything on the board fits together. Each one has its own page.

FIG 0.6 · Anatomy of a ticket
Ticket
A ticket is one unit of work. It runs through a single AI agent in its own git branch and worktree, and it carries its plan, its diff, and its pull request in one place. New tickets land in the backlog; running one spawns its agent.
Worker
A Worker is the AI agent session that builds a ticket. One ticket gets one Worker, so you can run many at once, each in its own lane, and throughput comes from parallelism rather than a single faster agent.
Worktree
Every ticket runs in its own real git worktree: a separate, isolated checkout of your codebase. Agents work side by side without overwriting one another, and you can check out any ticket's branch in a single click.
Project memory
Project memory is plain files in your repo: a wiki of concepts plus an append-only log of decisions, all cross-linked. Each Worker pulls the slice relevant to its ticket before it writes a line, so context compounds instead of scattering across one-off chats.
Bring your own subscription
Fredrin licenses the app, not the compute. Agents run on the AI coding subscription you already pay for (Claude Code or Codex today, with more agents on the way), with no per-token bill and no markup on model usage.

Where to start

Three doors, depending on what you came for. The sidebar has everything else.

  • Run your first ticket install, connect a repository, and merge one pull request, in about fifteen minutes.
  • Understand the board the five columns, what moves a card between them, and why that matters.
  • Build on Fredrin the REST API, the CLI, and the MCP server, for driving a board from your own tools.

The documentation is here, and the product it documents is already running.

Download FredrinExplore features