Skip to content

Loom v2.1.0

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 04:09
· 1 commit to main since this release
6d2d60d

Loom 2.1: plan, steer, and share the work

Loom 2.1 gives you more control over the crew: preview a plan before workers start, retry one task on another model, and save a run as a recipe. Model routing, memory review, phone continuity and team sharing build on Loom 2, with more integrations and tighter permission boundaries.

Orchestra and fleets

  • Plan previews: loom orchestra "<goal>" --plan-only waits for explicit approval before workers start. The existing --plan mode still writes Markdown specs.
  • Task retries and stalls: reassign failed, blocked or stalled tasks to another agent/model while preserving their worktrees. Per-kind parallel limits supplement the overall limit, and budget controls let you explicitly raise a paused run's budget.
  • Reusable recipes and visible progress: save a goal, resolved fleet and run options; export task graphs with loom orchestra:graph; inspect durable per-attempt timelines; send signed completion webhooks.

Models and routing

  • Aliases, fallbacks and effort: name models, edit model-agent fallback candidates, and set project reasoning defaults with loom models:effort. Explicit agent, chat and turn selections take precedence.
  • Health and spending: loom models --health probes configured models; composer estimates show known context and estimated costs; daily model caps aggregate recorded usage across projects and reset at midnight UTC.
  • Results you can take away: loom scoreboard --csv exports standings, and loom digest --scoreboard summarizes seven days. Agent option validation rejects invalid settings before replacing valid configuration.

Brain and memory

  • Filter search by kind, learning agent and creation dates; import Markdown files or public URLs, and export Markdown with loom brain:export --md docs/BRAIN.md.
  • Pin and prioritize memories, review near-duplicates before merging, and archive or restore stale memories without losing history. Chat-only memories stay within their chat.
  • Inspect who changed a memory and revert a revision; loom brain:why explains the actual text, scores and selection reasons saved for a turn.

Git and review

  • Generate commit subjects from the prompt and diff, draft editable PR descriptions with loom pr:describe, and opt into a branch per chat on its first reported edit.
  • Use standard, security or release review checklists, inspect per-agent change statistics, and suggest CHANGELOG bullets from merged branches.
  • Orchestra integration predicts merge conflicts before merging. Orchestra and crew commits honor repository hooks, and turn commits preserve unrelated staged files.

Phone

  • Queue messages offline with their chat, agent and plan selection; reconnect using durable delivery receipts and review failed or uncertain deliveries.
  • Home-screen quick actions on supported builds, optional biometric lock, configurable haptics, project notification groups, and text sharing into a destination you review before sending.
  • Search chats, preserve drafts and navigation through theme changes, and hold a diff line to stage a question with its file and code context. Web diff questions also support split diffs and Alt+Enter.

Desktop and web shell

  • Customize shortcuts, reopen the saved split mode and active project tab, and find recent commands or global chat results in the palette.
  • Search notification history, set a persistent reduced-motion preference, and synchronize appearance and selected chats between ordinary windows while split panes stay independent.
  • Empty tabs offer direct actions. The phone remembers its project, chat and tab per machine and gains the web accent presets.

Ops

  • loom doctor --fix --json includes repairs and checks in one report; web and phone Operations expose safe repairs and stale-session recovery.
  • Schedule retained backups, inspect project disk usage with loom du, and preview configurable worktree retention with loom worktrees:prune --dry-run.
  • Admin-authenticated Prometheus metrics, live daemon log rotation, redacted crash bundles, and update checks that show intervening release notes.

Teams and sharing

  • Share a read-only Orchestra run with loom share --run; choose 1h, 1d or 7d expiry presets and revoke links from project sharing controls.
  • Filter the team activity feed, mention teammates, and see project presence. Share encrypted team fleets and import them into the local Orchestra picker.
  • Set project approval roles for paired devices, list and revoke team invites, and export a complete selected audit period with loom audit --csv.

Integrations

  • Signed GitHub /loom issue comments from repository collaborators start fresh chats; linked Linear issues move to Done after their PR merges; Jira adds assigned-issue intake.
  • Attach GitLab merge requests for pipeline failures and trusted review feedback. Slack /loom commands start Orchestra goals; Discord can keep a progress thread per run.
  • Preview webhook templates without firing work, export or subscribe to schedule calendars, and configure, preview or send SMTP activity digests over TLS or STARTTLS.

CLI and agentic Loom

  • loom send --stream and loom ask --json stream NDJSON; loom watch --run follows Orchestra progress. Queued sends wait for their own request's outcome.
  • Literal command aliases, option-aware Bash/Zsh/Fish completions, dependency-free starter templates, disk config validation, and standalone HTML chat export.
  • MCP adds scoreboard, fleet listing, demo creation and memory listing tools with the caller's access scope. The TUI gains a Scoreboard view.

Safety and permissions

  • Project allow/deny tool rules, protected paths and shell denylists apply with deny precedence; adapters refuse hard policies they cannot enforce.
  • Secret scanning covers manual and automatic commits and pushes, including outgoing history. Explicit owner/device overrides are scoped to one operation.
  • Configure approval deadlines and permission presets, inspect effective sandbox status, and review risky activity with loom audit --risky. Credential redaction now covers transcripts, previews, streams and exports.

Chat

  • Pin messages, find project bookmarks, quote replies with linked source Markdown, and share composer drafts between desktop and phone with revision checks.
  • Save named prompt templates with variables, copy source Markdown, and retain expanded tool outputs across visits and devices.
  • Chat headers show recorded cost, tokens and completed turns; chats open at their first unread reply, including replies beyond the latest history page.

Fixes

  • Correct queued-send outcomes, route startup failures, TUI prompt targeting and Source Control draft preservation; phone relay reconnects recover missed replies and settle interrupted requests without unpairing another machine.
  • Close path and credential leaks in model tools, attachments, agent pictures, skill installs, previews, scoped APIs, notifications and revoked sockets. Preserve memory privacy, trust and expiry through sharing and import/export.
  • Settle interrupted ACP requests and queued turns; serialize runtime, goal and trigger admission; protect dirty worktrees and unrelated merges; prevent workers from starting after abort; fix transfer recovery and linked-worktree checkpoints.
  • Improve phone-connected shutdown, IPv6 sockets, directory previews, empty-file reads and Loom Cloud forwarding with --tailnet.

Upgrade notes

  • Automation compatibility: loom send --wait --json still prints one JSON object. The new NDJSON stream is loom send --stream; loom ask --json streams one outcome per model chat. Existing scripts that parse the final send object can keep doing so.
  • Phone starter templates moved to /api/init-templates. Update API consumers to that endpoint; /api/templates is for named prompt templates.
  • Hosted team-hub migrations: a hosted hub needs 0013_chat_move.sql (sealed chat_move jobs with runner authorization), 0014_zones_and_confirmations.sql (lease claims and extensions check every hard zone; editing or republishing a memory resets its confirmations) and 0015_teams_sharing.sql (encrypted team fleets, invite listing and revocation, validated encrypted mentions in the team feed). Apply them in order. Updating the CLI alone isn't enough for the hosted team features and fixes that use them.