v0.3.0

fold 0.3.0

You can see why a worker failed and start it in a new Claude Code session while keeping its task claims. The main agent also has its own area for project setup work.

Workers and sessions

• Choose New session on the Agents screen or run fld worker restart <name>. The worker keeps its name, claims, and workers it started. Its new session receives the review comments, conflicts, and failed checks it needs to address. You can ask the main agent to restart a worker too.
• Failed turns show their errors on the Agents screen and in the top bar. After three turns fail without reaching a model, Needs you shows Model access and fold notifies the main agent and the worker's starter.
• The Agents screen shows session IDs and transcript paths. Run fld transcript <agent> to get the current transcript path, or add --tail N to read its last N lines. Earlier worker session IDs remain available.

Work for the main agent

• Use the built-in area main for work the main agent builds itself, such as project instructions and checks configuration. The task area menu includes Main agent and Decide automatically.
• You approve proposals from main by default. Reviewer agents do not take these tasks, and the main agent can approve its own work only with your explicit permission for that task. When a task leaves main, fold removes the review requirement it set for that area.

Agent instructions

• All agents receive default engineering practices, including passing checks, recording changes through fold, and writing in Simplified Technical English. Your instructions, project rules, role limits, and approved scope take priority. Agents request fixes for failing checks outside their own work.
• The fold skill also includes a local reference for checks, configuration, commands, and tools, so agents can look these up when planning work.

Improvements and fixes

• The daemon reads your login shell's environment at startup to find claude and git. fld doctor checks the Claude Code installation and sign-in state that workers use. Run fld restart after changing your shell setup.
• Leads receive waiting tasks and reviews when the daemon restarts or a pause ends. Claims held by stopped or failed workers do not hide that work.
• Sessions keep receiving notices after daemon restarts, including sessions that started before their agent registered. The app and fld doctor show agents that fold cannot reach.
• When a workspace matches its submitted version, board cards and task details show that version and what it awaits. Workers do not appear stalled while their proposals wait for others. Their stall time starts again when changes, conflicts, or failed checks need attention.
• fold ignores model placeholders in Claude Code error messages and repairs affected workers at their next start.
• start_worker names the existing lead when it resumes one.
• Message recipients appear once, and diff selections explain why you cannot add a comment.
• The web app uses fold's conductor icon.

Breaking changes

• The area and label main are reserved. The area cannot have a lead or profile, and its label cannot be renamed or deleted. Review agents cannot claim, batch, or approve its tasks.
• The database upgrade stops if another area owns the main label. It also stops if an existing main area has another label, a lead, or a profile. The error gives the recovery steps.

Install or upgrade

• Install or update fold:

  curl -fsSL https://omukk.dev/fold/install.sh | sh

• The installer puts fld in ~/.local/bin. Set FOLD_VERSION to choose a release or FOLD_INSTALL_DIR to choose another folder.

• After updating, run fld restart to use the new version.

• Binaries support Linux x86_64 and aarch64, and macOS 13 or newer on Apple silicon. Linux binaries are static. The web app comes with fld.

• Use Claude Code 2.1.299 or newer and sign in before starting fold. Projects with Git require Git 2.36 or newer.

Full changelog