tusharmewara

Homebrew Loom

Name: Homebrew Loom
Author: tusharmewara

AI community

SOURCE https://github.com/tusharmewara/homebrew-loom

Description

Loom is a unified agentic ecosystem that enables seamless collaboration between multiple AI tools (jcode, crush, claude-code, opencode, goose, etc.) while sharing skills, sessions, and MCP servers. While also giving flexibility to use it as workflow engine for your task and you can choose to use any agent per task.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

homebrew-loom

Homebrew formula for [Loom](https://github.com/tusharmewara/loom) — the shared ecosystem for AI coding tools.

[![Latest Release](https://img.shields.io/github/v/release/tusharmewara/loom?label=loom)](https://github.com/tusharmewara/loom/releases)

The Problem

If you use multiple AI coding tools (Claude Code, jcode, Cursor, Goose, opencode, crush...), you've probably noticed they don't share anything. Skills you install in one are invisible to the rest. MCP servers need to be configured separately each time. Sessions are locked inside whichever tool created them.

Loom is the **shared layer** between all of them.

Quick Start

# Install
brew tap tusharmewara/loom
brew install loom

# Initialize the ecosystem (creates ~/.loom/)
loom init

# Optional-but-recommended: start the background daemon
brew services start loom

That's it. Run `loom status` to confirm everything is set up.

First Steps

Once Loom is installed, these are the first things to try:

# See what Loom knows about — tools, skills, MCP servers
loom scan

# Check the health of your setup
loom doctor

# List installable MCP servers from the registry
loom mcp list-known

# Install one (e.g., Playwright for browser automation)
loom mcp install playwright

# List registered skills
loom skills list

Everything you add (MCP servers, skills, tools) becomes available to **every** tool in your ecosystem — no per-tool configuration needed.

Real-World Scenarios

Share an MCP server across tools

# Install once
loom mcp install filesystem

# Use from any tool — Claude Code, jcode, Goose, etc. — all share it
# without needing separate configs

Export a session and continue elsewhere

# After a session in any tool, export it to Loom's shared storage
loom sessions list
loom sessions export  --output session.jsonl

# Resume it in a different tool with full history
loom sessions resume  --provider anthropic --