open-mercato

Cezar — Productivity skill for Claude Code

Productivity community

Cezar is a parallel coding agents orchestrator.

How to install Cezar

This entry records only its repository, not the path inside it, so there is no exact command to give. Open open-mercato/cezar and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cezar does

Cezar is a parallel coding agents orchestrator. Type a task, pick a workflow and an agent — Claude Code, Codex or OpenCode, or a mix of them per step — and watch it work live: steps, tool calls ... or: fire and forget, PR will land and issue will be fixed. Run ot locally (Linux, Mac, WSL2) or on VPS!

Alternatives in Productivity

Skill Context Detection — Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type 2.8k ★
Pi Subagents — Claude Code like Sub-Agents & Workflow Orchestration for Pi — parallel execution, live widget, fleet view, cus 967 ★
Agentacct — See what your coding agents did and what it cost 665 ★

README

cezar ⚡

**Parallel coding agents orchestrator** — a local cockpit for running and tracking AI coding-agent tasks in your repo.

Type a task, pick a workflow and an agent — **Claude Code, Codex, OpenCode or pi (the latter two experimental), or a mix of them per step** — and watch it work live: steps, tool calls, tokens, diffs, in a browser cockpit that runs entirely on your machine. Your CLI logins, your `gh`, your files. No accounts, no database, no cloud.

🔥 **Fire and forget.** Queue a stack of autonomous coding and maintenance tasks and let them run — cezar orchestrates them across isolated worktrees, in parallel. Flip the **Autonomous** flag and a run never stops to ask; it just finishes. Leave it on a VPS and you get a dev team that's *always on* — a mobile-friendly cockpit you can check from your phone, working your backlog while you're away.

[A look inside](#a-look-inside) · [What cezar does best](#what-cezar-does-best) · [What it solves](#what-it-solves) · [Who it's for](#who-its-for) · [Quick start](#quick-start) · [How it works](#how-it-works) · [Core concepts](#core-concepts) · [Cockpit tour](#cockpit-tour) · [Agent backends](#coding-agent-backends) · [Remote access](#remote-access-host-cezar-on-a-server)

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) ![Node 20+](https://img.shields.io/badge/Node-20%2B-339933) ![TypeScript 7.x](https://img.shields.io/badge/TypeScript-7.x-3178c6) ![Zero config](https://img.shields.io/badge/config-zero-success) ![No database](https://img.shields.io/badge/database-none-success)

cd your-repo
npx cezar-cli        # → cockpit at http://localhost:4321

That's the whole setup. If your `claude` CLI is logged in (Pro/Max) and `gh` is authenticated, there is nothing else to configure. State lives in `.ai/cezar/` inside your repo — plain JSON, NDJSON and Markdown you can `cat` and fix by hand.