Skip to content

github install

ai coding agent orchestratorwindows · linux · macos

all your agents. one terminal.

Claude Code, Codex, OpenCode, Kilo, Antigravity, Grok, Qwen Code and Kimi Code side by side, across all your projects. orkai shows who's working, who's done and who's waiting for you, and takes you straight there with a single key.

install orkai view on github

single native binary
no runtime
self-updating
free

Orkai

workstation

› default0

session-20

session-30

+ new session

f1 help

write a task

pc workstationwho claudeworktree offwhere ~/dev/acme/web

live simulation of the overviewagents grouped by project, with status, time and what each one is doing

works with

claude codecodexkiloopencodeantigravitygrok buildqwen codekimi code

and your terminalpowershellbashzshwindowslinuxmacos

the problem01

which one is waiting for you?

claude · checkout-redesign

Committing changes…
git commit -m "checkout"

codex · payment-tests

Run the migrations now?
(y/n) ▌

claude · simulator-builds

Compiling SimulatorKit
(12/48)

opencode · physics-merge

Merging the new physics
engine

bash · localhost-server

ready on localhost:5173
GET / 200 in 12ms

agy · container-ssh

docker exec -it api sh
…

kimi · folder-icon-update

Done.
3 files changed

claude · docker-install

Installing docker-ce…
apt-get install -y

‖1 ✔2 · Orkai

acme/web › 2

1 ✔checkout-redesignclaudeRunning design update and committing changes

2▸‖payment-testscodexwaiting for you · Run the migrations now?

acme/mobile › 1

3 ⠋simulator-buildsclaudeBuilding and launching both apps in simulators

studio/game › 2

4 ⠋physics-mergeopencodeMerging the new physics engine

5 $localhost-serverterminalnpm run dev

lab/infra › 1

6 ●container-sshagyRetrieving container SSH credentials

orkai/cli › 2

7 ✔folder-icon-updatekimiFolder icon update

8 ⠋docker-installclaudeInstalling Docker inside the container

payment-tests is waiting for you · alt+n opens it

Ten tabs, six projects. You flip between them to find out who finished, who got stuck and who asked for approval twenty minutes ago.

orkai brings every agent from every project into one screen, grouped by folder, with each one's status live. When one of them needs you, it lets you know.

in 56 seconds02

watch orkai at work.

features03

built for running ten agents at once.

03.1

type the task. the agent spawns.

Pick the folder with ctrll and who runs it with tab. Type the task and press enter: the agent starts working on it right away and shows up in the project's group, with its timer and a line saying what it's doing.

03.2

one of them needs you.

When an agent you're not looking at asks for approval or finishes, the terminal rings the bell, shows a notification and the window title counts who's waiting, even with orkai in the background.

03.3

`altn` and you're there.

Jumps straight to the agent that's been waiting the longest, from any screen, even from inside another agent. Want the alert on your phone? A notify_command sends it through ntfy or wherever you like.

03.4

two agents. one repo.

With ctrlt, each agent spawns in its own git worktree, on the orkai/<name> branch. Multiple agents work on the same repository without stepping on each other. /diff shows what changed; /merge brings it into your branch.

03.5

rebooted your machine?

Each agent runs in its own process, which owns its terminal: closing or updating the interface takes no one down. After a reboot, ctrlr resumes every conversation right where it left off.

03.6

exact status, instantly.

Hooks, plugins and each agent's own protocol tell orkai when it's working, waiting for you or done. No guessing from screen text: a reply that ends with “Would you like to…?” isn't mistaken for a question.

Hooks only record the event type. Your prompts, commands and responses never touch the disk.

⠋working

‖waiting for you

✔done

●idle

$terminal

↻interrupted

✗exited

UserPromptSubmitworking
PreToolUse · Bashworking
PermissionRequestwaiting for you
Stopdone

03.7

plan usage at a glance.

The 5-hour, weekly and monthly windows (or the balance) of every agent you're logged into, with a countdown to the reset. Green, yellow from 70%, red from 90%. Agents you're not logged into don't show up.

usage · updated 34s ago

claude5h━━━━━━━─────62%resets 2h14m

week━━━─────────23%resets 4d05h

codex5h━───────────12%resets 3h41m

week━━━━━━━━━───76%resets 58h00m

kimi5h━━━━━━━━━━━─93%resets 48m00s

skills on /

Each agent's skills and commands show up in autocomplete. /skill args starts an agent that invokes the skill right away.
subagents in view

The subagents that Claude Code and Codex spawn show up right below their agent, with their description and the tool in use.
!command

!npm run dev runs the command in a new terminal, without changing who runs your next tasks.
terminals that become agents

Ran claude inside a terminal? Within 2 seconds it shows up in the overview with its type, status and subagents.
remote control

Every Claude Code session started by orkai opens with Remote Control on: pick it up in the Claude app or at claude.ai/code.
self-updating

Every new build is verified by size and SHA-256 before it replaces the executable. Running agents aren't affected.

supported agents04

eight agents and your shell. one screen.

orkai never touches any of your config files. Hooks, plugins and environment variables apply only to the process it launched, and add to your own.

`who`	Agent	Program	Exact status	Usage in overview	Resume after reboot
`claude`	Claude Code	`claude`	hooks (`--settings`)	5h and weekly	`--resume <id>`
`codex`	Codex	`codex`	`notify`	5h and weekly	`codex resume <id>`
`kilo`	Kilo CLI	`kilo`	event plugin	balance (`funds`) and Kilo Pass	`--session <id>`
`opencode`	OpenCode	`opencode`	event plugin	OpenCode Go (5h and weekly)	`--session <id>`
`agy`	Antigravity CLI (successor to Gemini CLI)	`agy`	OSC 7501	5h and weekly	`--conversation=<id>`
`grok`	Grok Build	`grok`	window title	weekly or monthly	`--resume=<id>`
`qwen`	Qwen Code	`qwen`	hooks (system defaults)	no usage API	`--resume <id>`
`kimi`	Kimi Code	`kimi`	screen	5h, weekly or monthly	`--session <id>`
`terminal`	PowerShell, bash…	`shell`	output activity	—	reruns the command

how it works05

the interface comes and goes. the agents stay.

Each agent runs inside its own detached holder process, which owns the pseudo-terminal (ConPTY on Windows, PTY on Unix). The interface just connects to them.

interfaceorkaican close, crash or update

127.0.0.1 + token

holderConPTY / PTY⠋ claude

holderConPTY / PTY⠋ codex

holderConPTY / PTY⠋ pwsh / bash

closed it?
Closing, restarting or updating orkai takes down no agent. When you open it again, it reconnects to all of them.
↻ reboot?
Agents show up as interrupted and ctrlr relaunches each one in its folder, resuming the conversation.
and the history?
Every agent's full output is recorded, with rotation. orkai logs <id> prints the transcript.

keyboard06

all from the keyboard.

try it: press enter, tab or altn now

enterstarts an agent with the typed task
tabpicks who runs it: an agent or the terminal
ctrllpicks the project folder
ctrltturns on a dedicated worktree for the next agents
altnopens the next agent waiting for you
ctrl]goes back from the agent's tab to the overview
ctrlrrecovers interrupted agents
!cmdruns the command in a new terminal
/orkai commands and agent skills

also on the command line

orkai ls [-s session]            lists agents with their live state
orkai new -k <agent> -C <folder> starts an agent with a task
orkai send <id> <text...>        types into the agent and presses enter
orkai attach <id>                attaches this terminal to the agent
orkai logs <id> [-n lines]       the agent's recorded transcript
orkai recover [-s session]       relaunches interrupted agents
orkai update                     downloads and installs the newest version

security07

your code, your machine.

127.0.0.1
Holders listen on localhost only, on a random port.
256 bits
One token per agent, stored only in your data folder.
0
of your config files changed. Hooks and plugins apply only to the launched process.
SHA-256
verified, along with the size, on every update before the binary is swapped.

To show usage, orkai reads each agent's login token in memory only and sends it, over HTTPS, solely to the service that issued it. orkai never stores, logs or refreshes it.

install08

install in one minute.

target=orkai-x86_64-unknown-linux-musl
mkdir -p ~/.local/bin
curl -fL -o ~/.local/bin/orkai "https://github.com/lucasmarujo/orkai-cli/releases/latest/download/$target"
chmod +x ~/.local/bin/orkai

If ~/.local/bin isn't on your PATH yet, add export PATH="$HOME/.local/bin:$PATH" to your ~/.bashrc or ~/.zshrc. The binary is static and runs on any distro.

target=orkai-aarch64-apple-darwin
mkdir -p ~/.local/bin
curl -fL -o ~/.local/bin/orkai "https://github.com/lucasmarujo/orkai-cli/releases/latest/download/$target"
chmod +x ~/.local/bin/orkai

Intel Mac: change the target to orkai-x86_64-apple-darwin. If ~/.local/bin isn't on your PATH yet, add export PATH="$HOME/.local/bin:$PATH" to your ~/.zshrc.

$setup = "$env:TEMP\orkai-setup.exe"
Invoke-WebRequest "https://github.com/lucasmarujo/orkai-cli/releases/latest/download/orkai-setup.exe" -OutFile $setup
Start-Process $setup -Wait

Run it in PowerShell: it installs orkai for your user, without admin rights and without a SmartScreen prompt, and offers to add it to your PATH. The installer isn't code signed yet, so an orkai-setup.exe downloaded with a browser may get the prompt: More info › Run anyway. Then open a new terminal and type orkai in PowerShell, Bash or zsh.

git clone https://github.com/lucasmarujo/orkai-cli.git
cd orkai-cli
cargo install --path .

With Rust 1.88+, it lands in ~/.cargo/bin. Local builds show up as dev and don't self-update; orkai update turns one into an official build.

important

To use an AI agent, its CLI must be on your PATH: claude, codex, kilo, opencode, agy, grok, qwen or kimi. Keep orkai in a folder your user can write to: auto-update replaces the executable itself.

type orkai.

All your AI agents. One terminal.

install orkai view on github