Shipped
Agent-to-agent messaging
Agents communicate freely with each other to get work done. J5 integrates A2A with the platform managing your agents. Messages flow reliably and feel natural to you and your agents.
Steer fleets of agents,
not just a few chats
We believe the next frontier of agentic work will come from giving your agents tools that help them work effectively in groups. We're building J5 Code to push the tooling further and explore this frontier.
Early software, in daily use by its author. Expect rough edges.
Built on T3 Code. Kept up to date.
Everything T3 Code does, J5 Code does: six agent harnesses on your own subscriptions, desktop, web and mobile clients, remote control over your tailnet, a checkpoint on every turn, and the one-button PR. J5 adds a layer above it and works hard not to fork the hull.
- Bring your own subscription. No keys resold, no quota caps.
- Desktop, web, and mobile. Control a server from a phone.
- A strong commitment to performance and quality.
- Commit, push, and open a PR from one button.
- MIT licensed, both of us.
Want normal T3 Code? It is excellent.Get it at t3.codes
How J5 stays in sync
- Upstream
- pingdotgg/t3code · tracking its main branch
- Pinned upstream commit
70d60e0· as of 2026-10-17 · in J5 Code 0.0.51- Cadence
- We stay as up to date as we can, but these guys are shipping like crazy. Please be patient.
- Policy
- Read our FORK.md to see how we're merging with T3 Code, and the register of divergences to see where we chose to differ from it.
The commit on this card is the one in the latest stable release, read from FORK.md when the site builds.
Tools to Make Your Agents Better
ShippedReady to useChartedIn dry dock, being builtHorizonOn our roadmap
Shipped
Cross-server A2A
Peer the machines you run J5 on and agents message each other across them, no matter where they are. Give each machine its own capabilities and let an agent borrow them from anywhere.
How peering worksShipped
Personas
Pick the right model for the job. Give it a personality. Share it with everyone on your team.
Shipped
Playbooks
Keep agents on track during long running work. Steer a crew towards a common goal. See how the work is going at a glance.
1Build and testBuilder
2Independent reviewCritic
3Sit on CI, triage failuresSitter
4Is the migration safe to run?Captain
5Merge and reportSitter
Shipped
Crews
Spawn a group of agents with a single goal. Use personas to give each agent a role. Talk to the Captain to keep your attention focused.
Shipped
Inbox
Agents can send you messages to get your attention. Reply from a single place instead of hunting down the chat.
Shipped
Fleet page
See what all your agents are doing at a glance. Stalled or stuck agents show up here, making it easy to keep things moving.
Every card above has a definition of record, with acceptance criteria, in the product docs.
On the Horizon
These features will take your agents even further. Other people in front of your agents, more platforms, and a fleet that's easier to keep in view.
Charted
Share chats with others
Put someone in front of your agent instead of copying its answers to them.
- Share links can be opened in the browser. Nothing to install.
- Let them talk to your agent, or just see what the agent is saying.
Charted
Collaborate with your whole team
Share agents on a single server or project.
- Agents always know who's talking.
- Tools to help you manage agents in a shared environment.
Horizon
Windows support
Run J5 clients on Windows.
Horizon
Better fleet management UX
Keep the right agents in front of you, while letting the background ones reach you as you need them.
Q&A
- Why did you build this?
- We found that the existing tools were great for single agent use cases, but multi-agent orchestration features were few and far between. So, we decided to fork the tool with the best starting point and build the things we wanted to see.
- Why did you call it J5 Code?
- We wanted to make sure that you could install this alongside T3 Code and not clash with your existing setup. Having a separate app, separate workspace, and separate server needed a different name. "J5" is just the first and last character of the original maintainer's GitHub username. Nothing special.
- Can I fork this and build my own thing?
- Of course!
- Will you be contributing back to T3 Code?
- Gladly, following their contribution guide. In practice that means bug fixes: they've said they aren't taking new features from outside right now, so we don't try to send ours upstream.
Take the helm.
Free, MIT licensed, and a tracking fork of T3 Code. Bring the subscriptions you already have.
Apple Silicon app today. The installer puts a self-contained server on macOS or Linux x64.All download options