Context Loom

Context Loom turns a chat request and a local project into a smaller, cited prompt you can review before sending. It preserves your exact message, stays local by default, and separates projected token savings from usage actually reported by a model provider.

How it works

1. Connect a project. Context Loom indexes eligible text files inside one folder you choose.

2. Prepare a message. Write the request exactly as you want the destination model to receive it.

3. Review and copy. Inspect the selected sources, fidelity checks, and complete rendered payload.

4. Track the conversation. Reuse a conversation name to see projected and observed token history.

Context Loom never sends the copied payload to a model unless you deliberately use an integration that performs an outbound request.

Related MCP server: reflens

Install from source

The primary install is Node-free and uses the workbench already bundled in the Python package. Python 3.11-3.13 and uv are required.

Clone the public source repository and install its bundled workbench:

git clone https://github.com/ownasquare/context-loom.git
cd context-loom
uv tool install .
context-loom demo
context-loom serve

Open http://127.0.0.1:8768. Context Loom is not currently distributed through PyPI; the source install above is the canonical install path.

If you already have a checkout, start at uv tool install .. Run uv tool update-shell and open a new terminal if context-loom is not found after installation.

Try the demo

context-loom demo creates a private generated project, indexes it, and prepares one sample message. Start context-loom serve, then use Home, Prepare, Project files, and Savings to inspect the complete flow. The demo does not call a provider or require credentials.

Use your own project

Start the workbench and choose Add project, then enter a local folder that the Context Loom process can read. It scans immediately, and the project switcher can add, select, and rescan multiple projects.

For a scripted setup:

context-loom workspace add /absolute/path/to/project --name "My project" --id my-project
context-loom workspace sync my-project
context-loom serve

The demo uses demo-workspace; the example above uses my-project, so the two flows do not collide. See Getting started for the first-success walkthrough and Docker setup.

Connect a chat tool

Copy and paste is the recommended first integration. Context Loom also offers an MCP server and a loopback-only HTTP API; provider-shaped output formats are available for advanced use.

context-loom adapter preview codex

adapter preview prints a standalone snippet for review. It does not edit harness configuration; after you add the snippet, the harness starts context-loom mcp serve --transport stdio when needed. See Harness integrations and Extending Context Loom.

Docker

Docker keeps state in a named volume and mounts one chosen project read-only at /workspace:

export CONTEXT_LOOM_PROJECT=/absolute/path/to/project
docker compose up --build --detach
docker compose exec context-loom context-loom workspace add /workspace --name "My project" --id my-project
docker compose exec context-loom context-loom workspace sync my-project

Then open http://127.0.0.1:8768. Without CONTEXT_LOOM_PROJECT, Compose mounts the bundled sample project. Host paths are not visible inside the container unless they are mounted.

What Context Loom guarantees

• The exact user message is retained in the canonical envelope and checked at renderer boundaries.

• Selected text remains tied to a current source version, hash, path, and line range.

• Unsafe summarization falls back to extractive or passthrough behavior.

• Telemetry, outbound access, secret-file indexing, and raw-message persistence are off by default.

• Projected, provider-observed, and verified counterfactual token figures remain distinct.

No system can guarantee the same model answer while withholding arbitrary source bytes. Read the fidelity contract, token-accounting contract, and limitations before making quality or savings claims.

Learn and contribute

• Documentation index

• Troubleshooting

• Security policy

• Contributing

• Changelog

Package users do not need Node. Contributors need Node 22 only when changing or validating the React workbench. Context Loom is currently a local single-user beta; hosted, production, paid-provider, and real-harness proof remain separate from credential-free local validation.

License

MIT