Weft v0.1.1

Sites that log in with a header now work. Weft 0.1.0 worked with sites that use cookies (Medium, GitHub, Linear and most dashboards). Single-page apps that send Authorization: Bearer …, a CSRF token or an API-key header returned 401. In 0.1.1 the extension remembers the latest value of those headers while capturing and adds it to your AI's requests inside your browser tab. The value never reaches the Weft app or your AI; they only see the header's name (get_auth_context → authHeaderNames). It's kept in the browser's memory and cleared when the browser closes.

Install / update

• macOS: Weft-macOS.dmg (signed & notarized, Apple Silicon + Intel)
• Windows: Weft_0.1.1_x64-setup.exe or .msi
• Linux: .AppImage, .deb or .rpm
• Chrome extension: weft-extension.zip. Unzip it, then in chrome://extensions click Load unpacked (or replace the folder and click ↻ on your existing Weft extension).

Requires Node.js 20+. Docs: https://vilvaathibanpb.github.io/weft/docs.html · Demo: https://youtu.be/nOrxH0BQnvU

Also in this release

• The app's version label comes from the build, not a hardcoded string.
• Download links on the site and in the README use version-less file names.
• New extension test for auth-header handling, run in CI.

Weft v0.1.0

Weft turns any website you're logged into into a local MCP server for Claude Code, Claude Desktop, Codex and Cursor. No API keys, no OAuth apps, no cloud.

▶️ 2-minute demo: Medium → Weft → Claude Code · 🌐 Website · 📖 Docs

Install

1. App
   • macOS: Weft_0.1.0_universal.dmg (Apple Silicon + Intel, signed & notarized)
   • Windows: Weft_0.1.0_x64-setup.exe or .msi
   • Linux: .AppImage, .deb or .rpm
2. Chrome extension: unzip weft-extension-0.1.0.zip, then in chrome://extensions enable Developer mode → Load unpacked.
3. Connect your AI: in the app, click Open in client on a ready site and pick your client. Restart the client.

Requires Node.js 20+ (your AI client starts Weft's connector with it).

What's in 0.1.0

• One-button capture from the Chrome extension: Weft maps a site's API from your own browsing.
• Local MCP server with 9 tools: list/search endpoints, OpenAPI synthesis, auth surface (names only), and live call_endpoint through your browser session.
• Non-GET calls require explicit confirm: true.
• Desktop app: library, endpoint detail, audit log, ⌘K, one-click client install, and a library that persists across restarts.
• Privacy: everything on 127.0.0.1; the extension forwards only method, URL and status. No headers or bodies, no account, no telemetry.

Weft is young. See the status table for what's done and what's next.