The Karma Yoga CLI · in development

You direct.
The crew does the work.

The Karma Yoga CLI runs Claude Code and Codex as a crew in one terminal session. You talk to the manager on the left. It starts agents on the right, sends them work and knows who is busy.

Read the guide What the CLI does

Not released yet. Nothing to install today.

karma attach reports

manager claudeprotected

› Add a CSV export to the reports page. Build it, test it, have it reviewed.

● I will set up a crew for this.

$ karma agent create builder

$ karma crew tell builder "Add the export"

$ karma agent create tester

$ karma crew tell tester "Test the export"

$ karma agent create reviewer

$ karma crew tell reviewer "Review it"

$ karma agent create docs

$ karma crew tell docs "Document it"

$ karma crew status

builder idle tester idle

reviewer busy docs busy

›

builder codexidle

› Add the export

Reading src/reports

Adding an Export CSV button

Writing exportCsv for the report rows

Export added to the reports page.

›

tester codexidle

› Test the export

Waiting for the export button

Writing tests for empty and large reports

6 tests pass.

›

reviewer claudebusy

› Review it

Waiting for builder and tester

Reviewing the export diff

›

docs claudebusy

› Document it

Adding Export to the reports help page

›

One window. A manager on the left.
A crew on the right.Scroll to assemble the crewSee how it works

How a session works

Say what you want.
The manager runs the crew.

The Karma Yoga CLI is one command for every agent session on your Mac. Each session is one window with one fixed layout.

Start a session.
karma new creates a session from a template. A protected manager sits on the left. The agents it starts stack on the right.
Talk to the manager.
The manager is a real Claude Code or Codex session. Tell it what you want done.
Let it run the crew.
The manager creates agents and messages them. karma crew status shows who is busy or idle and which messages are still waiting.

One fixed layout

The manager stays put.
The crew comes to it.

A protected manager

The manager is always the left pane, and it is protected. karma kill is the only way to stop the session.

A column that scrolls

Every agent pane is 20 rows tall. The column on the right grows past the screen and scrolls, up to 12 agents by default, while the manager stays where it is.

Claude Code and Codex, in any mix

Each agent is the real tool, running as it always does. A session can be all Claude, all Codex or both.

Messages that arrive

A message to an agent is sent in one step and comes back with a receipt. If the agent is busy, the message waits and is delivered when its pane is ready.

Built to keep going

One conversation per session, for life.

A session created today is the same manager conversation a year from now, kept going by auto compaction.

Agents come back

When an agent's process exits, its pane stays where it is and the agent starts again in the same conversation. After three failures in two minutes it is parked and reported.

Park and bring back

karma agent deactivate parks an agent and keeps its conversation. karma agent reactivate brings it back in the same conversation.

Commands that stay out

Typing /clear, /new or /logout in a session pane is blocked. If a conversation changes anyway, the Karma Yoga CLI notices and returns to the pinned one.

After a reboot later

Sessions are rebuilt at login with their layout, and each agent resumes its conversation.

Its own tools

Pinned Claude Code and Codex, with their own login.

Separate from yours

The Karma Yoga CLI downloads a pinned version of Claude Code and Codex from their official sources into ~/.karmayoga. You log in once inside it. Your own claude and codex stay exactly as they are.

Updated only when they pass

The tools never update themselves under a running session. The Karma Yoga CLI installs a new release next to the current one, tests it and switches only when the tests pass. The version before stays on disk.

One file

The Karma Yoga CLI ships as one binary, written in Rust. On another machine it needs nothing installed, and sessions there keep running when the connection drops.

One background process

One server runs in the background and owns every pane. Everything else is a command that starts, does its job and exits.

Where it stands

Nothing is released yet.

The Karma Yoga CLI comes first. The Mac app follows it.

done
The session serverSending as one step, pane identity, recovery, held messages, the input guard, the scrolling agent column and the fixed layout are done.
building
Claude and Codex modulesEverything that depends on how each tool behaves, tested against its latest release.
building
karma crew and karma agent in RustThe crew commands, rebuilt on the server with no extra background process.
first release
The Karma Yoga CLI binaryOne file with new, attach, ls, kill, karma agent, karma crew and doctor, with karma usage coming.
later
Reboot restore, Linked Macs, the Mac appSessions rebuilt at login, sessions on every Mac on your account, and a native view for each agent.

Work you direct, not work you do.

Read how a first session goes, or leave your email for the Mac app.

Read the guide Mac app

You direct.The crew does the work.

Say what you want.The manager runs the crew.

Start a session.

Talk to the manager.

Let it run the crew.

The manager stays put.The crew comes to it.