Skip to main content

​
CLI Features

Loom’s command-line interface provides an interactive REPL (Read-Eval-Print Loop) for AI-powered coding assistance, conversation persistence, and remote execution environments.

​
Installation

# Build from source
cargo build --release --bin loom

# Or using Nix
nix build .#loom-cli-c2n

​
Quick Start

1

Start a new session

Launch the interactive REPL:
loom
2

Authenticate with server

Connect to the Loom server for conversation sync:
loom login --server-url https://loom.ghuntley.com
3

Resume a previous conversation

loom resume [thread-id]

​
Global Options

​
--config
path
Path to custom configuration file
​
--workspace
path
Workspace directory for file operations (default: current directory)
​
--log-level
string
Override log level: trace, debug, info, warn, error
​
--json-logs
boolean
Output logs in JSON format for structured logging
​
--server-url
string
Loom server URL for LLM proxy and thread syncDefault: http://localhost:8080
Environment: LOOM_SERVER_URL
​
--provider
string
LLM provider to use: anthropic or openaiDefault: anthropic
Environment: LOOM_LLM_PROVIDER

​
Commands

​
Session Management

loom
Private sessions are stored locally only and never sync to the server. Use for sensitive work or offline development.

​
Thread Operations

loom list
Displays all local threads with metadata:
  • Thread ID (UUIDv7 format: T-<uuid>)
  • Title (auto-generated from first message)
  • Message count
  • Last activity timestamp

​
Authentication

# Login to Loom server
loom login

# Logout
loom logout
Authentication tokens are stored in the system keychain using the keyring crate.

​
Version Information

loom version
Displays:
  • Loom version (from Cargo.toml)
  • Build timestamp
  • Git commit SHA
  • Rust version used for compilation

​
ACP Agent Mode

loom acp-agent
Runs Loom as an Agent Client Protocol (ACP) agent over stdio for VS Code extension integration. This mode is used internally by editor plugins.

​
Configuration

Loom loads configuration from multiple sources (in priority order):
  1. Command-line flags (--config, --workspace, etc.)
  2. Environment variables (LOOM_*)
  3. Config file (~/.config/loom/config.toml or custom path)
  4. Built-in defaults

​
Example Config File

[global]
default_provider = "anthropic"
workspace_root = "/home/user/projects"

[logging]
level = "info"
format = "pretty"

[tools]
[tools.workspace]
root = "/home/user/workspace"

​
REPL Usage

Once in the REPL, you can:
1

Type your request

> Add error handling to the user authentication function
2

Agent responds and executes tools

The agent will:
  • Read relevant files (read_file tool)
  • Suggest changes
  • Apply edits (edit_file tool)
  • Run tests (bash tool)
3

Review changes

All file modifications and command outputs are displayed in real-time
4

Continue conversation

The thread persists across sessions. Resume anytime with loom resume.

​
REPL Controls

  • Ctrl+C: Save thread and exit gracefully
  • Ctrl+D (EOF): Same as Ctrl+C
  • Empty input: Ignored, reprompts

​
Auto-Commit

Loom automatically commits changes when certain tools are executed:

Auto-commit triggers

  • edit_file: File modifications
  • bash: Commands that modify the working tree
Disable with: LOOM_AUTO_COMMIT_DISABLE=1
Configuration:
  • Model: claude-3-haiku-20240307 (fast, cheap)
  • Max diff size: 32 KB
  • Commit message: Auto-generated based on changes

​
Git Integration

Loom captures git metadata for every thread:
  • Initial state: Branch, commit SHA, dirty status
  • Final state: Current branch, commit SHA, dirty status
  • Commits made: List of all commit SHAs created during the session
  • Remote URL: Git remote origin (normalized slug)
This metadata enables:
  • Thread search by branch/repo/commit
  • Workspace history tracking
  • Collaboration insights

​
Git Credential Helper

# Configure git to use Loom for SCM authentication
git config --global credential.https://loom.ghuntley.com.helper 'loom credential-helper'

​
Advanced Commands

​
Spool (VCS)

loom spool <subcommand>
Jujutsu (jj)-based version control with tapestry naming.

​
Tunnel Management

# Start WireGuard tunnel
loom tunnel up <weaver-id>

# Check tunnel status
loom tunnel status

# Stop tunnel
loom tunnel down

​
SSH to Weaver

loom ssh <weaver-id>
Establishes SSH connection through WireGuard tunnel to a remote weaver.

​
Exit Codes

  • 0: Success
  • 1: General error (check stderr)
  • 2: Invalid arguments

​
Environment Variables

​
LOOM_SERVER_URL
string
Server URL for LLM proxy and thread sync
Default: http://localhost:8080
​
LOOM_LLM_PROVIDER
string
LLM provider: anthropic or openai
Default: anthropic
​
LOOM_AUTO_COMMIT_DISABLE
boolean
Disable automatic git commits
Values: true, 1, yes
​
LOOM_THREAD_SYNC_URL
string
Override thread sync endpoint (advanced)

​
Troubleshooting

Check if the server is running:
curl http://localhost:8080/health
Or use the hosted version:
loom --server-url https://loom.ghuntley.com
List available threads:
loom list
Thread IDs use UUIDv7 format starting with T-.
Enable debug logging:
loom --log-level debug
Check workspace permissions and file paths.
Verify you’re in a git repository:
git status
Check if auto-commit is disabled:
echo $LOOM_AUTO_COMMIT_DISABLE

Build docs developers (and LLMs) love

Get started for freeTalk to us