Loom Core
Loom Core is the orchestration layer behind Loom Suite: a registry-driven generator for MCP client configs, a local daemon for server lifecycle management, and an Agent HUD that makes agent work observable.
A command center for agent work
Loom ships a local Agent HUD that connects to the daemon and makes tasks, workflows, memory tiers, and server health inspectable. Click any screenshot to zoom.
Local-first, no cloud dependency. Designed for multi-tool, multi-agent workflows.
You can see what’s blocked, what’s slow, and what changed without scraping logs.
Pair Loom Core policy boundaries with MentatLab for visual DAG orchestration and run visibility in private environments.
MentatLab →



Loom Companion for iOS
Fleet monitoring, session management, and real-time alerts from iPhone and iPad. Connects to your Loom HUD instance over LAN or zero-trust gateway.
Direct local connection or remote access with mandatory TLS, OAuth PKCE, and per-actor rate limiting.
Read-only fleet access by default. Session create/end and sandbox start/stop require explicit scope grants.
18 endpoints with stable contract. Bearer token auth, structured audit logging, and device ID tracking.
API docs →


In progress for private enterprise deployments
Loom Core is actively adding enterprise control surfaces for gateway routing, role-aware access, and Kubernetes-native execution.