Getting started

fibers puts every agent session you have running on one board, says which one needs you, and carries what a session learned into the next. It attaches through the runtime’s own hooks, so there is nothing to remember to run. Pick the path that matches where your sessions live.

Path 1: the desktop app

The macOS app walks a checklist: sign in, add the plugin to Claude Code, bind a repo, see the first row. It will be the shortest route once there is a signed build. There is not one yet: today it runs from source, so unless you are working from the repository, start with path 2. Download says when that changes.

Path 2: the plugin on its own

For Linux, for a machine without the app, or if you prefer the terminal. Start in a terminal with the installer, which puts fibers on your PATH and adds the plugin to Claude Code:

curl -fsSL https://fibers.dev/install.sh | sh   # in a terminal: the CLI, and the Claude Code plugin
fibers login   # in the same terminal: sign in, once per machine
fibers init --workspace <slug>   # in each repo: bind it to your workspace

The quickest start needs no account at all: four commands inside Claude Code put your sessions on a local board in fibers ls. Both routes are in install the plugin.

Path 3: Claude Code on the web

A cloud sandbox starts fresh every time and has no home directory to keep a credential in. Three pastes into the environment’s settings make its sessions land on the board. Follow cloud sessions.

What you have afterwards

• A row on the board for every session on a machine with the plugin, grouped into needs you, active, blocked and idle. Cloud sessions show in the work lane rather than as live rows. The terminal view is fibers ls. That is all a fresh install turns on; fibers features on work adds the work lane, and features lists the rest.
• With work on: a work lane. Sessions claim an item, log progress, and release it with a handover note. The backlog is fibers work ls.
• With work on: a morning brief, fibers catchup, that says what moved since you last looked.

Staying up to date

Claude Code can update the plugin by itself. In Claude Code, open /plugin, go to Marketplaces, pick the fibers marketplace and choose Enable auto-update. Without that, a session tells you when a newer release is out (checked at most once a day, or once an hour while the check cannot reach the marketplace), and fibers update installs it. Run fibers features off update-notice to turn that notice off on this machine. fibers doctor says whether auto-update is on. Restart your sessions after an update so they load the new hooks.

Read what is captured before you decide whether to trust it, and troubleshooting when a row does not appear.