iloom
Scale understanding, not just output — AI code you and your team can trust

A VS Code extension that turns AI chaos into structured workflows. Every decision documented. Every task isolated. Every PR reviewable.

The Problem
Nobody wants to review your AI's work. Including you.
AI coding assistants are powerful, but working with them introduces new challenges:
- Invisible reasoning: You can't review what you can't see—AI makes decisions without documenting why
- Team trust: You don't trust your AI's code. Neither does your team.
- Context decay: AI starts hallucinating or forgetting requirements mid-task
- Branch chaos: Parallel tasks create port conflicts, stale branches, and environment collisions
- Mental overhead: You're juggling 5 branches, but it's your brain that has the merge conflict
iloom solves these through structured workflows, visible & persisted reasoning, and complete isolation for each task.
How iloom Works
Starting a loom doesn't just create a branch. It launches a multi-agent workflow that:
- Aligns on requirements before any code is written
- Surfaces assumptions and creates a structured plan
- Captures key decisions, risks, and insights along the way
- Persists everything in your issue tracker—analyses, plans, results and a summary when you're done
- Executes with full context in an isolated environment
- Verifies tests and lint before completion
The result: AI-generated code with a clear paper trail, isolated from your other work, ready for meaningful review.
Requirements
The iloom CLI is required. This extension is a UI layer for the iloom CLI tool.
Install the CLI before using this extension:
npm install -g @iloom/cli
Prerequisites:
- macOS (Linux and Windows support coming soon)
- Git
- Node.js 18+
- GitHub CLI (
gh) — for GitHub integration
- Linear CLI (optional) — for Linear integration
- Claude Max subscription (strongly recommended)
Quick Start
- Install the extension from the VS Code Marketplace
- Install the CLI:
npm install -g @iloom/cli
- Open a project folder in VS Code
- Find iloom in the left-hand activity bar—look for the lightbulb
- Set up your project: You'll be prompted to configure iloom for this project—main branch, issue tracker, and more
- Create your first loom: Click
+ New Loom and enter an issue number
Core Workflows
Create a Loom
Start from a GitHub or Linear issue number, PR, or free-form description. iloom takes you through a structured workflow:
- Requirements alignment: AI analyzes the issue and surfaces questions before coding
- Research & analysis: Deep dive into the codebase to understand context and constraints
- Plan creation: A detailed implementation plan is posted to your issue tracker
- Isolated execution: Work happens in a separate worktree with its own resources
- Verification: Tests and lint run before completion
Supports issue numbers (#123, ENG-123), PR numbers, or branch names.
Manage Looms
The iloom explorer panel in the activity bar shows all active workspaces across your projects:
- Type indicators: Issue, PR, or branch-based looms
- Session status: See when your AI needs your attention
- Quick actions: Switch, finish, rebase, or remove looms

Complete a Loom
When your work is done, click the 🏁 finish flag to wrap up:
- Validates tests and lint pass
- Rebases onto main (or parent loom), resolving conflicts with AI assistance
- Merges or creates PR based on your configured merge behavior:
local (default): Merge directly into main branch locally
github-pr: Push and create a pull request
github-draft-pr (default when contributing to open source): Create draft PR on start, mark ready on finish
- Cleans up the worktree and closes the workspace window
Isolation Features
Each loom runs in complete isolation from your other work:
| Resource |
How iloom Isolates It |
| Git worktree |
Separate filesystem—no stashing, no branch switching, no conflicts with other looms |
| Database branch |
Schema changes isolated from main and other looms (Neon integration) |
| Unique port |
Web apps run on deterministic ports (base port + issue number)—no more "port taken" mysteries |
| Isolated binary |
CLI tools get workspace-specific binaries (e.g., my-cli-25 when working on issue #25) |
This means you can have five looms running simultaneously, each with their own dev server, database state—without interference.
Child Looms
For long-running or complex tasks, create nested looms within a loom:
- Break down large features into smaller, reviewable PRs
- Fix bugs discovered mid-task without losing context on the parent feature
- Child looms inherit the parent's database state and branch—not main
Start a new loom while inside an existing loom, and iloom will ask if you want to create a child.
Open Source Contributions
Maintainers shouldn't be overwhelmed by unexplained AI-generated code. With iloom, your analysis and plans post directly to the PR—giving reviewers full context on why the code looks the way it does.
il contribute n8n-io/n8n
This forks the repo, clones your fork, configures iloom, and sets up draft PR mode automatically.
Run il contribute with no arguments to contribute to iloom itself.
Features
iloom Explorer
The activity bar panel provides a central view of all your active looms:
| Feature |
Description |
| Project grouping |
Looms organized by project |
| Type icons |
Visual distinction for issues, PRs, and branches |
| Session status |
Know which loom needs your attention and why |
| Quick switch |
Click to open any loom workspace |
Commands
Access via Command Palette (Cmd+Shift+P / Ctrl+Shift+P):
| Command |
Description |
iloom: Start New Loom |
Create a new loom from issue or description |
iloom: Quick Switch Loom |
Fast switch between active looms |
iloom: Refresh |
Refresh the iloom explorer |
iloom: Settings |
Configure iloom for the current project |
Recap Panel
Track your workflow progress with the Recap panel:
- Timeline of insights, decisions, and artifacts
- Links to issue comments, new issues and PRs created during sessions
- Risk and assumption tracking

AI Integration
iloom integrates with AI coding assistants to provide workflow context:
- Session status indicators: See when Claude Code or other AI tools are actively working
- Context sharing: Looms provide structured context about the task at hand
- Artifact tracking: Automatically tracks issue comments, PRs, and other outputs
- Conflict resolution: AI helps resolve merge and rebase conflicts
- Commit messages: AI generates helpful, context-aware commit messages
FAQ
Q: Why do I need the CLI installed separately?
The extension is a thin UI layer. All git operations, worktree management, and issue tracker integration are handled by the CLI. This separation allows CLI updates without extension reinstallation.
Q: What issue trackers does iloom support?
iloom supports GitHub Issues and Linear. JIRA support is on the roadmap.
Q: What AI tools does iloom support?
iloom is focused on supporting the Claude Code command line tool.
Q: How do looms differ from regular branches?
Looms are git worktrees—separate working directories that share the same repository. Combined with isolated ports, database branches, and CLI binaries, you can work on multiple issues simultaneously without any resource conflicts.
Support
For extension issues, feature requests, and questions:
github.com/iloom-ai/iloom-vscode-support/issues
For CLI issues, visit github.com/iloom-ai/iloom-cli/issues.
License
© 2026 iloom AI. All rights reserved.
This extension is proprietary software. The iloom CLI is separately licensed under BSL-1.1.
This software is provided "AS IS", without warranty of any kind.