Juggler vs qarunbook: Features, Pricing & Which Is Better (2026)

A side-by-side comparison of Juggler and qarunbook — features, pricing, and ideal use cases — to help you decide which AI tool fits your workflow.

Juggler

Julian Storer

Free

A native desktop workbench for AI coding agents with branching conversation trees, inspectable tool calls and editable context.

Branching Conversation Trees: Fork the session at any point, recursively, so competing approaches and tangents run side by side without polluting the main context.
Miller Column Navigation: A Finder-style column layout lays out tool calls, item properties and nested sub-threads for long reading and editing sessions.
Transaction Inspector: Open any model transaction to see the assembled system prompt, messages, tool definitions, output, token use, timing and stop reason.
The Context Surgeon: Fold history into a new thread, move or copy items between branches, expand a branch back into its parent, and undo structural changes.
Local or Remote Sessions: Run the desktop app locally or the headless binary on the machine holding the code, then attach from the app, a browser or a phone.
Durable Sessions: Sessions are stored on disk as live-synced Yjs documents, so quits, relaunches and dropped connections do not lose the conversation.
Automatic Context Sizing: Juggler measures the full request before each call, reserves room for the answer and compacts older history before limits become an error.
Inspectable MCP Tools: Follow an MCP handoff end to end - schema offered, arguments generated, approval, result and errors - with server status, logs and per-tool filtering.
JavaScript Extension SDK: Context items, LLM loop strategies, slash commands, viewers and Pinboard tabs are extensions you can fork or replace, under a permissive Apache-2.0 SDK.

Exploring Competing Fixes: Branch a thread into two sub-threads to try different approaches to the same bug and compare results before committing.
Auditing Agent Behavior: Inspect exactly what the model received and returned when an agent makes a surprising edit to the codebase.
Remote Development: Run the server on a dev box or GPU machine where the repository lives and drive the same live session from a laptop or browser.
Long Refactors: Keep a multi-hour session alive across quits and reconnects, with the agent paused awaiting approval for its next step.
Provider Comparison: Drive Claude Code, Codex, Copilot, Gemini and local Ollama models through one interface to compare behavior on the same task.
Custom Tooling: Write JavaScript extensions that add slash commands, file viewers or new LLM loop strategies to the workbench.

Freemium

qarunbook is an app testing runbook where AI drafts a test plan from your code and your team or AI works through it, tracking issues and retests.

AI-Drafted Test Plans: The /test-checklist skill looks through your app and drafts checks with steps and expected results already filled in.
MCP Connection: Connect Claude Code, Claude Desktop, Codex, Cursor or any MCP client so the assistant can read the plan and record results.
Issue-to-Check Linking: Every issue sits on the check that found it with the affected platforms, and raising one removes the pass.
Retest Flow: When an issue is fixed the check waits for someone to look again before being marked passed.
Roles and Join Links: Give people access to only the projects they need and invite whole groups with a join link.
Multi-App Workspaces: Keep each app's sections and platforms separate so web, driver and marketing sites are tested side by side.
GitHub and Linear Integration: Connect issue trackers so problems found in testing flow into existing engineering workflows.
QA Runbook Skill: The /qa-runbook skill works through the plan on web and mobile, recording each result and re-checking fixes.

Release Testing: Run a structured test plan before each release across web, Android and iOS.
AI-Assisted QA: Let a coding assistant execute checks and record pass/fail results through MCP.
Team Test Coordination: Split test checklists among teammates and see progress and results in one workspace.
Regression Follow-up: Track bugs against specific checks and retest them after fixes ship.
Solo Developer Testing: Generate a test plan from the codebase so a one-person team knows what to check.
Agency Multi-Client QA: Manage separate apps and clients with scoped access and a flat workspace price.