Dauno/crew

One shared core for Claude Code, Codex and Pi on any machine with Nix. Same
instructions, skills and private memory in every CLI. Worker nodes in Kitty
tabs coordinate work across repositories.
## Requirements
Use Nix with flakes enabled, Kitty for worker tabs and a configured Claude
Code, Codex or Pi CLI.
## Install
sh
nix profile add github:Dauno/crew
## Update
sh
nix profile upgrade --refresh crew
This installs the latest commit on main. Open a new crew session to use
it.
## Use
Run any supported CLI in the current repository:
sh
crew claude
crew codex
crew pi
Outside a remote-controllable Kitty session, crew opens its own Kitty
window. Ask the agent to open workers and describe their tasks. The agent uses
the nodes skill and helper to open Claude Code, Codex or Pi worker nodes as
Kitty tabs. Workers send completion notices to their parent through mailboxes.
Helper reference:
sh
crew-nodes spawn \
--name reviewer --cli claude --cwd "$PWD" --task review [-- ARGS...]
--task takes a short label, such as review. It identifies the task in
$CREWRUNS/ / and the worker's CREWTASK variable. Arguments after
-- pass unchanged to the CLI. Pass them only when the human requests a model
or option; otherwise, workers use their CLI's default model.
## Native messages
Each crew session has a UUID and a private mailbox under
$CREWHOME/mailboxes/. crew-nodes send ID uses the Kitty window ID to find
that session and atomically stores a message. Success means stored, not read.
Messages may contain up to 8 KiB of UTF-8 text. Send a report path for longer
content. The receiver delivers through its CLI integration, never by typing
into the editor.
Claude and Codex agents run crew-nodes ack MESSAGEID after reading a
message. Pi automatically runs ack only after verifying the exact custom
message in the active Pi session branch and persisted JSONL file, whose header
matches that Pi session. This records persisted incorporation, not model
reading or task completion. Manual Pi acknowledgements remain supported.
Acknowledgements do not promise exactly-once work.
notify STATUS REPORT uses the same mailbox and keeps its current notice text
and one metrics record per call.
Use crew-nodes type ID [--enter] only for deliberate terminal input.
Native task messages never fall back to type. Pending messages stay with
closed sessions; crew does not migrate them to a new session automatically.
Codex messaging stops if its TUI switches to another root conversation.
Restart the crew session before sending to that conversation.
## Memory and permissions
Memory stays on each machine. By default, it lives at
~/.local/share/crew/memory; it follows $XDGDATAHOME when set. Memory has
global, machine and repository scopes. The coordinator writes entries;
workers propose them. The human's current request takes precedence.
Claude Code's human session keeps confirmation prompts; a settings rule
permits the nodes helper. The human's Codex session runs with
--sandbox danger-full-access. Pi keeps its usual configuration. Workers
always run without tool confirmation prompts. Pi 1.4.0 needs no permission
flag. Pi can ask whether to trust project resources under .pi.
The human answers project trust dialogs.