Where does Jev fit in here? I cannot find it in the README.

It does not. The README never mentions Jev, TypeSafe, or typed decisions, and nothing in the described workflow routes or scores anything through a decision model. What it does describe is a desktop workspace for the coding agents you already have installed: parallel tasks in Git worktrees, a review pass before integration, MCP tools and task-owned browser sessions. Judge it on that basis or skip it.

Do I need an account to try it from source?

For building and testing, no: the README says building the source and running the automated tests require no Jackalope cloud account, deployment secrets or reporting endpoint. Running native tasks does require an approved Jackalope account in every build, source builds included. That is a real gate on evaluating the product itself rather than just its code.

How isolated are the parallel worktrees, really?

They isolate Git changes and nothing more. The README is explicit that worktrees do not isolate the operating-system privileges of agents or tools, so anything a task runs has your user's permissions regardless of the worktree boundary. Treat that as the real risk model for autonomous runs, not the directory separation.

Which agents work, and what will it cost me?

Six named agents: Codex, Claude Code, Grok Build, OpenCode, Kimi Code and Antigravity, each with documented provider-specific capabilities and limits. You supply the accounts and models, and agents use your own provider credentials, so provider charges land on you. Capacity-aware routing and bounded quota handoff are built in; remote execution and monetary budgets are not.

What toolchain do I need to build Jackalope from source?

Node 26.9+ within Node 26 and pnpm 10.11.0; native development also needs Rust 1.98.1 and your platform's Tauri prerequisites, plus MSVC build tools and WebView2 on Windows. Install and sign in to the agent CLI you want to use.

What can a task use besides running the agent?

MCP tools and task-owned browser sessions, recurring local scheduling and recoverable task history, alongside project guidance and codebase context. You can answer agent questions mid-run, run checks and review the patch before integration.

What is still future work in Jackalope?

Remote execution, monetary budgets and team collaboration are roadmap items, as are signed installers and platform acceptance. Provider charges land on you because agents use your own accounts, while capacity-aware routing and bounded quota handoff are already built in.

CommunityJev Tools & CLIs

Jackalope

A Tauri desktop workspace for running coding agents side by side: parallel task queues in isolated Git worktrees, your existing agent sign-ins, and a review step before anything is merged.

See highlights

Open github.com

Stars: 2
Language: Rust
License: APACHE-2.0
Published by: Community
Author: Jackalope-Dev
Last verified: Oct 2026

Jackalope-Dev/jackalope

Organization repository on GitHub

View on GitHub

A desktop workspace for coding agents, parallel Git worktrees, and code review.

Forks: 1
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

About this project

A desktop workspace for coding agents. Bring your installed agents and existing sign-ins, run tasks in parallel Git worktrees, and review changes before merging. Website · App tour · User guides · Documentation · Contributing · Apache-2.0.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import awesomejev

Works forJev for Classification Jev for Routing Jev for Tool calling

Used inJev for Software & DevTools

Languages: Rust

Highlights

Works with Codex, Claude Code, Grok Build, OpenCode, Kimi Code and Antigravity, with provider-specific capabilities and limits documented.
Tasks run as parallel queues in isolated Git worktrees, and you can answer agent questions mid-run, run checks and review the patch before integration.
MCP tools and task-owned browser sessions are supported, alongside recurring local scheduling and recoverable task history.
Prerelease: you can build from source today, while signed installers and platform acceptance are still in progress.

Watch out

Read this one carefully before assuming what it is: the README describes no Jev integration at all. There is no mention of Jev, TypeSafe or typed decisions anywhere in it, so this is a general agent workspace rather than anything in the Jev lineage. Running native tasks requires an approved Jackalope account in every build, including source builds, although building the source and running the automated tests need no account, secrets or reporting endpoint. Worktrees isolate Git changes, not the operating-system privileges of the agents or tools they run. Agents use your own provider accounts and may incur provider charges, and remote execution, monetary budgets and team collaboration are still roadmap items. The toolchain is pinned tightly: Node 26.9+ within Node 26, pnpm 10.11.0, Rust 1.98.1 and the Tauri prerequisites, plus MSVC build tools and WebView2 on Windows. Apache-2.0 for project-authored code. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

doc-router

Rust CLI that checks each PDF page for a usable text layer, extracts text pages locally, sends only the rest to an OCR model via LiteLLM, and merges a page-ordered result.