Fredrin documentation
People decide, Workers build. Learn the loop from install to merged pull request, and everything the Workers can see along the way.
Start here
- QuickstartInstall, connect a repository, merge one pull request.
- InstallSystem requirements, first-launch checks and updates.
- The boardThe five columns and what moves a card between them.
- WorkersOne agent session per ticket, many running at once.
- BrainPlain files in your repo that every Worker reads first.
- API, CLI and MCPThe REST API, the CLI and the MCP server.
Core concepts
- Ticket
- One unit of work, run by one agent in its own branch and worktree, carrying its plan, diff and pull request.
- Worker
- The agent session that builds a ticket. One per ticket, so throughput comes from running many at once.
- Worktree
- A separate git checkout per ticket, so agents work side by side without overwriting each other.
- Brain
- Plain files in your repo: a wiki of concepts and a log of decisions. Each Worker reads the slice its ticket needs.
- Bring your own subscription
- Workers run on the Claude Code or Codex plan you already pay for. No per-token bill from Fredrin.
Popular guides
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 runs alongside Claude Code and Codex rather than replacing them. See how the AI coding tools compare, or read what a software factory is and how an ADE runs one.
Need help?
Ask the community, check the common fixes, or write to the team.