Project Loom

• Project Repository: https://github.com/gsuquet/loom
• Project Maintainer: Gabriel Suquet (@gsuquet)

Table of contents

1. Project description
2. Project status
3. Who this project is for
4. Project dependencies
5. How to use Loom
6. Guidelines for contributors
7. Additional documentation
8. How to get help
9. Terms of use

Project description

Loom keeps all the work that I have to do in one prioritized list, for all my contexts (personal, company, clients). It records all the work that I or agents do.

• With Loom you can triage all your items in a single list, in the order of priority. The items are merge requests to review, tickets, incidents, alerts, support requests and your own ideas. The list shows one context or all of them.
• With Loom you can edit and create Jira, GitLab and GitHub issues locally and sync them upstream. You can also review merge requests from the terminal.
• With Loom you can delegate a task, or a part of it, to specialist agents. Typed contracts, quality gates and approval rules control the agents, and you can watch the agents work live.
• Unlike a tracker or an agent wrapper, Loom keeps an auditable ledger of all work on disk, with one ledger for each context. Learnings go from one context to the next, but client data stays in its context.

Project status

v0.2.0 has these functions:

• It installs, runs loomd as a user service and keeps itself up to date.
• It indexes the git repositories of the machine: contexts, repo cards, loom search, automatic fetch and fast-forward.

v0.3 (tasks and TUI) is in progress on the dev channel. The changelog gives the shipped changes. The design is in docs/design/, and the plan is in the roadmap.

Who this project is for

Loom is for software engineers and consultants who:

• Work in several contexts (clients, employer, personal projects).
• Use many forges and trackers.
• Want to delegate a part of their work to coding agents, and keep control and traceability.

Project dependencies

• mise: toolchain manager (installation guide). It installs the pinned Rust toolchain (1.99.0) and the linters.
• Git: with worktree support.
• Agent CLI (optional, from v0.7): Claude Code, or another supported harness, to delegate tasks to agents.

How to use Loom

Install loom and loomd into ~/.local/bin (macOS and Linux, arm64 and x86_64). Then run loomd as a user service:

curl -fsSL https://github.com/gsuquet/loom/releases/latest/download/install.sh | sh
loom service install
loom status

1. Define your contexts in ~/.loom/config.toml (configure contexts).
2. Check them with loom repo doctor.
3. To register the repositories that the shell enters, use eval "$(loom shell-init zsh)" (shell integration).

To work on Loom, run these commands:

git clone https://github.com/gsuquet/loom.git
cd loom
mise install
mise run check

Guidelines for contributors

Read the Contributing Guide and the Code of Conduct. Coding agents also read AGENTS.md.

Additional documentation

The documentation uses the Diátaxis framework:

• Reference: CLI conventions, loom and loomd commands (generated), install script, releases (channels, assets, signature), configuration, loomd API, task files (task.md, events.jsonl), style guide. The reference gets new file formats when their features ship.
• How-to guides: install loom, run loomd as a service, upgrade and roll back, configure contexts, recurring tasks, shell integration, local traces.
• Explanation: auto-upgrade, repository updates, task store, search.
• Tutorials: to come when features ship (from v0.3).

Design and plan, outside Diátaxis (target behavior, not shipped behavior):

• Design: vision, architecture, domain model, storage, repositories, tracker sync, capture and learnings, agent orchestration, user workflow.
• Decisions: architecture decision records.
• Plan: roadmap.

How to get help

• Issue Tracker: tell us about bugs or ask for features on GitHub Issues.

Terms of use

Project Loom is licensed under the MIT License.