Quilltap 4.2.1
Quilltap 4.2.1 Release Notes
It is a truth universally acknowledged that a plugin in possession of eighteen perfectly good system prompts must be in want of a working require statement.
The trouble, as is so often the case in these affairs, was one of introductions. The Default System Prompts plugin — that steadfast provider of example prompts for Claude, GPT, Gemini, Grok, and all the rest — arrived at the Electron ball with its dance card in order, its prompts pressed and ready, and promptly tripped over a footman named openai who had not, in fact, been invited.
The mechanism was this: the plugin's build configuration declared @quilltap/plugin-utils as an external dependency, which is to say, "I shan't pack this myself; I expect my host to provide it." A reasonable assumption in development, where the main application's pantry is well-stocked. But in a standalone or Electron deployment — where the plugin must make do with its own modest luggage — the full plugin-utils package attempted to load, dragging along provider utilities that demanded the openai module, a package the plugin had neither need of nor access to. The entire plugin collapsed in the foyer. No prompts were served.
Meanwhile, the legacy fallback — a prompts/ directory at the project root that once held these very same templates — had been cleared away in an earlier renovation. Both doors were locked. The Import Template modal stood empty, offering only the gently devastating suggestion to "Create templates in Settings > Prompts."
The fix is surgical: @quilltap/plugin-utils is no longer treated as external. Instead, esbuild bundles only what the plugin actually uses — the createSystemPromptPlugin function — directly into the output, tree-shaking away the provider utilities and their inconvenient appetites. The prompts arrive. The modal fills. The demonstration proceeds without embarrassment.
What Changed
- fix: System prompt plugin (
qtap-plugin-default-system-prompts1.1.4) failed to load in standalone/Electron builds due to a transitiveCannot find module 'openai'error. The esbuild config now bundles@quilltap/plugin-utils(tree-shaken) instead of treating it as an external runtime dependency.
Installation
Desktop App
Download from the quilltap-shell releases page:
macOS:
- Download the
.dmgfile and open it - Drag Quilltap to your Applications folder
- Launch Quilltap from Applications
Windows:
- Download and run the
.exeinstaller - If SmartScreen warns about an unknown publisher, click "More info" → "Run anyway"
- Launch Quilltap from the Start Menu or desktop shortcut
Linux:
- Download the
.AppImagefile, make it executable (chmod +x), and run it - Or install the
.debpackage:sudo dpkg -i quilltap_*.deb
Node.js (any platform)
npx quilltapOr install globally:
npm install -g quilltap
quilltapOpen http://localhost:3000 in your browser. Requires Node.js 22+. First run downloads ~150–250 MB and caches locally.
Docker
docker pull foundry9/quilltap:4.2.1Or use the startup scripts:
# Linux / macOS
curl -fsSL https://raw.githubusercontent.com/foundry-9/quilltap-server/refs/heads/main/scripts/start-quilltap.sh | bash
# Windows (PowerShell)
irm https://raw.githubusercontent.com/foundry-9/quilltap-server/refs/heads/main/scripts/start-quilltap.ps1 | iexOne does not blame the footman. One simply stops inviting him to parties where he isn't needed.
— The Foundry, with regrets
Installation
Desktop App (recommended)
The Quilltap desktop app (Electron) is available from
quilltap-shell 4.1.0.
Download the release for your platform (macOS, Windows, or Linux).
The quilltap-linux-arm64.tar.gz and quilltap-linux-amd64.tar.gz rootfs
tarballs attached to this release are used by the shell's Lima (macOS) and WSL2 (Windows) VM modes.
Node.js (any platform)
npm install -g quilltap
quilltapOn first run, the CLI downloads the application files (~150-250 MB)
and caches them locally. Subsequent launches start instantly.
Docker
docker pull foundry9/quilltap:4.2.1See the README for setup instructions.