This project provides a Loom implementation as an Obsidian plugin, enabling users to interact with large language models like GPT-3 through a recursively branching interface. It's designed for exploratory text generation and experimentation, offering a modular and extensible alternative to existing tools.

How It Works

Loom operates by allowing users to trigger text completions from their current cursor position within Obsidian. Upon activation (Ctrl+Space), it generates multiple child nodes, each representing a different completion of the preceding text. This is complemented by a tree interface in the sidebar for navigation and a pane displaying the full text of the current node and its siblings. The plugin supports various LLM providers, including OpenAI, Azure OpenAI, Cohere, and TextSynth, with extensibility for custom proxy implementations.

Quick Start & Requirements

• Installation: Installable directly from the Obsidian Community Plugins store or manually by downloading the latest release zip and placing it in [vault]/.obsidian/plugins.
• Source Build: Clone the repository, run npm i, and npm run build within the plugin directory.
• Prerequisites: Obsidian application. API keys for chosen LLM providers are required.
• macOS Hotkey Note: Default hotkeys (Alt+s, Alt+c, Alt+m) may conflict with system-level special character bindings; users may need to disable system shortcuts or rebind Loom hotkeys.

Highlighted Details

• Supports multiple LLM providers: OpenAI, Azure OpenAI, Cohere, TextSynth.
• Extensible via openai-cd2-proxy implementations.
• Offers a dedicated tree interface for navigating generated content.
• Includes a comprehensive set of hotkeys for efficient workflow.

Maintenance & Community

The project is developed by cosmicoptima. Support is available via Patreon.

Licensing & Compatibility

The repository does not explicitly state a license in the provided README. Users should verify licensing for commercial use or integration with closed-source projects.

Limitations & Caveats

Some default hotkeys on macOS may conflict with system-level shortcuts, requiring user configuration. The README does not specify the current development stage (e.g., alpha, beta, stable).