Lab / Concept

Agent protocol

JIVA: one terminal, many souls

A small crew of AI coding sessions that share one terminal: a desk that talks to you, a boss that splits the work, workers that do it, and a watchdog that swaps any of them before its memory fills up.

Open source, alpha Updated 6 min read

The problem it answers

One AI coding session is a capable pair of hands with a short memory. Give it a big job and two things happen. Its context window fills up, and the quality of its work slides well before the window is actually full. And you become its babysitter: you watch it, answer its questions, restart it when it drifts, and copy notes from one session to the next.

Opening five sessions does not fix that. It gives you five short memories to babysit, all editing the same files.

The idea

JIVA treats a group of sessions as a small crew with jobs, not as a row of chat windows. It runs them in a private terminal server on your own machine and gives each one a role:

  • The desk is the only session that talks to you. Questions from the rest of the crew reach you there, as typed asks with options and a default.
  • The boss splits the work into task cards of twenty lines or less and hands them out.
  • Workers each take one card, claim the folders they are going to touch so two workers never edit the same files, and report back when they are done or stuck.
  • The watchdog is a plain shell script, not an AI. Every five seconds it checks each session. Before any of them gets past about 200,000 tokens of context, it writes a handoff, retires that session and boots a fresh one in its place, which reads the handoff and carries on.

You keep one window open. The rest of the crew stays out of your way.

The rule underneath all of it: if a script can do a job, a script does it. The AI does the parts that need judgement, and nothing that only needs a timer.

Why a protocol and not a product

Most of JIVA is conventions written down: how a task card is shaped, what a handoff has to contain, where a session records a question for the human, how a claim on a folder works, and a short, append-only board that every session can read. The tooling enforces those conventions with small checks. Files stay under 150 lines, notes under 30, and the checks fail the build if they grow. Budgets are tests, not hopes.

Because it is conventions plus a few scripts, it fits any repository and any language. You install it once, run jiva init in a project, and start a crew with jiva up.

Crosstalk: sessions on different servers

The same idea stretches across machines. Crosstalk is a short paste-in kit that lets a session on one server leave a message for a session on another, over the SSH and terminal tools you already have, through a handful of task-runner recipes. No message broker, no new service to keep alive. It is how one desk can ask a question of a crew working on a different box and get the answer back in its own window.

What it is not

  • It is not a hosted service. It runs on your machine, under your own account, with your own AI subscription.
  • It does not approve things for you. Workspace trust prompts, spending and deploys stay with the human; JIVA only routes the question to you.
  • It is not finished. It is a public alpha, used every day to build the other things on this site, and it changes as that work teaches us something.

Where it came from

JIVA grew out of running many long coding jobs at once and losing track of which session knew what. Everything in it was a fix for a specific failure: a session that forgot its task after a long run, two sessions overwriting each other, a question that sat unanswered for an hour in a window nobody was looking at. It is open source under the MIT licence.