#2626th of 37 in Coding agents and assistants

jcode

Rust terminal coding agent with a shared daemon for multi-agent swarms

Documentation ↗ Website ↗ Repository on GitHub ↗

Stars: 20.7k
License: MIT
Last commit: Oct 2026
Last release: Oct 2026
Language: Rust

Stars, last 29 weeks+20,574

161 on 24 Mar 202620,735 on 13 Oct 2026

From GitHub's daily star counts.

Checked 14 Oct 2026 on GitHub.

Overview

jcode is a Rust coding agent for the terminal that runs multiple sessions against one shared server. Agents in the same repo are notified when another agent edits a file they read, and they can message each other or spawn worker agents. The README reports 14 ms time to first frame and about 3.1 MB extra RAM per headless session, measured against Claude Code, Codex CLI and others.

Who it is for: Developers running several terminal coding agents in parallel on one machine

Strengths

Sessions share one daemon; README reports ~3.1 MB per added headless session vs ~164 MB for Claude Code
Swarm tool: agents in one repo get edit notifications, DMs and broadcasts, and can spawn workers
Can resume sessions from Codex, Claude Code, OpenCode and pi
Built-in browser tool via Firefox Agent Bridge; Claude and OpenAI Codex OAuth supported

Weaknesses

Benchmarks are the author's own, run on one Linux machine, with differing versions between tables
Local embeddings raise single-session RAM from 27.8 MB to 167.1 MB
Self-dev mode is recommended only with a frontier model; weaker models can break the codebase
Browser automation needs separate Firefox Agent Bridge setup; provider list is only on the docs site

What it needs

no GPU
Needs Firefox Agent Bridge (optional, for browser tool)
Models: Claude (OAuth), OpenAI Codex (OAuth), Other providers listed in docs

Also in Coding agents and assistants

See all 37

Also in Coding agents and assistants
Rank	Project	Score
1	claw-codeRust CLI coding agent harness using Anthropic and OpenAI-compatible APIs194.9k starsMIT	83 out of 100
2	opencodeTerminal coding agent with build and plan modes, plus a desktop app213.4k starsMIT	79 out of 100
3	oh-my-openagentTerminal coding agent that fans work out across many models70k starscustom license	78 out of 100
#4	orcaDesktop app that runs CLI coding agents in parallel git worktrees92.1k starsMIT	77 out of 100
#5	openinterpreterTerminal coding agent, a Codex fork tuned for low-cost models68.6k starsApache-2.0	77 out of 100

How to choose

Check which models it can use: your own keys, local models, or only the vendor's.
See what it may do without asking (edit files, run shell, push) and how you approve.
Prefer agents that work in a branch or worktree you can throw away.

Health

Releases: 98 in the last 12 monthsLast one today
Top contributor: 98% of commits11,508 of 11,695 in the last 12 months
Security advisories: NoneOn GitHub, in the last 12 months
OpenSSF Scorecard: Not checked

Read from GitHub, deps.dev and OpenSSF on 14 Oct 2026. Bots and coding-agent accounts are left out of the commit counts. Not part of the score: how we check.

License in plain words

MIT Permissive

Use it at work: Yes
Change it and rebrand it: Yes
Sell it or host it for others: Yes

Your part: Keep the copyright and license notice in copies you ship.

A plain summary, not legal advice. Read the license on GitHub ↗ (opens in a new tab)

#26 of 37 in Coding agents and assistants on Archestack, as of 14 Oct 2026.

In your README

The badge updates twice a day.

[![Archestack](https://archestack.com/badge/1jehuang/jcode.svg)](https://archestack.com/best-of-vibe-coding/projects/jcode/)

How badges work

On your site or blog

A card with the rank, score and signals, in light or dark to match the reader.

<iframe src="https://archestack.com/embed/best-of-vibe-coding/jcode/" title="jcode on Archestack" width="400" height="270" style="border:0;max-width:100%" loading="lazy"></iframe>

Preview the card

Best of Vibe Coding on GitHub

Each review comes from the project's README and facts we check on GitHub. The fix form opens with jcode filled in.