PROJECTS

Back to Projects

2026 / OPEN SOURCE / DEVELOPER PREVIEW

A self-hosted system for coordinating projects, knowledge, applications, storage and machines, for people and AI agents.

Building software is getting easier.
Making it work together is not.

An agent can help build an application in an afternoon. But that application still needs somewhere to run, access to its data, a way to recover, and a record of why it was built the way it was. Multiply that by a collection of personal tools and the coordination becomes a project of its own.

LOOM is my attempt to give that work a common foundation. It connects projects, services, knowledge and storage across machines, while leaving room for ordinary files, independent applications and the agents you choose to work with.

LOOM / Portal
Full recorded LOOM Portal home screen, including status, attention findings and navigation.
$ loom enterRecorded session
Recorded from LOOM on September 16, 2026. Original terminal output, including the development system's reported warnings; not live status.
Recording details and text transcript

The real command, boot animation and complete home screen were captured at 120 columns by 62 rows. Playback runs at 2x speed. The opening idle pause was shortened; Portal output was not rewritten. This player has no connection to Main and accepts no shell input.

Read the captured screens

The system

Explore LOOM

Six connected areas

How it connects

Shared infrastructure. Distinct responsibilities.

LOOM / shared system
LOOMCoordinate.
Remember. Recover.

Independent environments

  • People
  • Hermes / MINA
  • ORCA
  • Codex
Use LOOM through its interfaces. Keep their own sessions and tools.
A conceptual map, not a deployment topology. The six areas share a system; agent harnesses remain outside its ownership boundary.

LOOM is not an agent harness. Hermes runs an agent's sessions, memory and messaging gateway. ORCA and Codex provide their own working environments. MINA is one optional agent configuration. They can use LOOM without becoming part of its core.

Nor does everything need to go through LOOM. Editing a file or making a Git commit remains ordinary work. LOOM becomes involved where a project declares resources, a capability runs, or information enters one of its shared services.

Open development

Working, open, and still being built.

LOOM is available as an Apache-2.0 developer preview. Its current development use includes application deployment, source search, decision-candidate registration and retrieval, cloud backups, and agent interaction through terminal and messaging sessions.

It is not a turnkey installation. Setup is still operator-specific, and broader document-processing, recovery and project-lifecycle workflows need further real-use testing. Guided installation and clearer everyday workflows are part of what comes next.

Based on the public source reviewed on . Source snapshot