Constant/README.md

Constant

 ██████╗ ██████╗ ███╗   ██╗███████╗████████╗ █████╗ ███╗   ██╗████████╗
██╔════╝██╔═══██╗████╗  ██║██╔════╝╚══██╔══╝██╔══██╗████╗  ██║╚══██╔══╝
██║     ██║   ██║██╔██╗ ██║███████╗   ██║   ███████║██╔██╗ ██║   ██║
██║     ██║   ██║██║╚██╗██║╚════██║   ██║   ██╔══██║██║╚██╗██║   ██║
╚██████╗╚██████╔╝██║ ╚████║███████║   ██║   ██║  ██║██║ ╚████║   ██║
 ╚═════╝ ╚═════╝ ╚═╝  ╚═══╝╚══════╝   ╚═╝   ╚═╝  ╚═╝╚═╝  ╚═══╝   ╚═╝

      local-first orchestration for weird builders, fleet nerds, and AI cockpit addicts

Constant is a control room.

Not a chatbot skin. Not a SaaS wrapper. Not another “agent framework” that only looks good in slides.

It is a pragmatic, local-first orchestration layer that sits on top of:

• a 4-pane tmux machine cockpit
• a multi-machine fleet view
• host-local CLIs like claude, codex, copilot, and vibe
• a mission runner that can route work across machines
• a growing durable memory layer for repo context, decisions, and persona

The vibe is somewhere between:

• demoscene terminal
• distributed workshop
• AI pit crew
• electron rare engineering energy

What Ships Today

Current build status in this repo:

• a Rust front-controller for the canonical constant entrypoint
• a 4-pane host-local tmux session per machine
• a fleet cockpit with one window per machine plus a central Constant window
• Constant, the orchestration CLI on top of the cockpit
• a native Rust chat-first TUI with composer, threads, and cockpit panes
• live cockpit controls for focus, capture, send, and pane restart
• local mission planning and verification
• host-local execution for claude, codex, and vibe
• copilot as a manual lane
• local message bus + cross-machine bridge
• heuristic local routing and buddy/planner responses without a Python runtime
• workspace-first durable memory with lexical + local vector search

The canonical script surface is constant-*. Legacy zellij-ai-* aliases remain only as compatibility shims.

Runtime notes:

• the public runtime is now Rust-only
• doctor, agents, skills, models, memory, buddy, fleet, tui, cockpit, and mission commands all execute from the Rust binary
• the public ./scripts/Constant wrapper rebuilds the Rust binary when sources change, then launches it directly
• the wrapper ad-hoc signs the rebuilt binary on macOS when codesign is available
• chat thread indexes now live in persisted sidecars under ~/.local/share/constant/indexes/chat
• unread state persists separately per workspace/user view
• constant mission delete <mission_id> is now enforced in Rust and refuses draft, planned, or running missions
• constant cockpit status-line now powers the tmux chat dock and surfaces disabled autorestart warnings

macOS note:

• if Gatekeeper blocks a freshly built binary from your terminal, allow that terminal under System Settings -> Privacy & Security -> Developer Tools
• then rerun ./scripts/Constant --help

Why This Exists

Most AI tooling is designed like a vending machine:

1. send a prompt
2. get an answer
3. pretend orchestration happened

That breaks the moment you want:

• multiple machines
• multiple CLIs
• persistent sessions
• human supervision without tab hell
• routing by task type
• repo memory that survives a single run

Constant is for the opposite use case:

• the workstation is real
• the shell is real
• the repos are real
• the agents are messy
• the human is still the one in charge

Core Shape

1. Machine cockpit

Each machine runs the same 4-pane layout:

• left: claude
• top-right: codex
• middle-right: copilot
• bottom-right: vibe

Everything runs on the host by default. No Docker dependency is required for the standard session.

2. Fleet cockpit

From your command center machine, you open one tmux window per machine plus a central Constant window. Each machine window attaches to that machine’s own local tmux session.

That gives you:

• one place to supervise the whole fleet
• one active orchestration surface in the Constant window
• local clipboard behavior on the operator machine
• remote sessions that stay remote
• a clean separation between orchestration and execution

3. Constant CLI

Constant sits above the fleet and handles:

• mission creation
• route selection
• backend selection
• CLI selection
• buddy review
• verification
• delegation
• cockpit handoff
• SSH discovery and fleet deployment bootstrap

3.5. Workflow skills

Constant now has a first-class workflow skill layer.

Public workflow skills:

• spec-planner
• architecture-brainstorm
• repo-onboarding
• task-decomposer
• pr-review-prep

Recommended minimal stack:

• spec-planner
• architecture-brainstorm
• task-decomposer

Recommended workflow:

1. spec-planner
2. architecture-brainstorm
3. task-decomposer
4. implementation on the selected agent / machine / CLI
5. pr-review-prep

Inspect them with:

./scripts/Constant skills --json
./scripts/Constant skills --public-only --json
./scripts/Constant agents --json

Create and route missions through these skills today with the Rust CLI:

./scripts/Constant mission create "Je veux ajouter un systeme de notifications" --workspace "$PWD"
./scripts/Constant delegate <mission_id> --skill architecture-brainstorm --json

The conversation-first chat surface is now native to the Rust TUI.

4. Durable memory

The memory layer is being built to support:

• workspace-first indexing
• weighted instruction fusion from .claude, .copilot, .agent, .agents, CLAUDE.md, AGENTS.md
• cross-mission summaries
• a durable decision graph
• persistent persona outside mission files

The design goal is simple: Constant should remember how you work, not just what you typed five minutes ago.

Quick Start

Requirements

• tmux
• git
• node
• npm
• uv
• claude
• codex
• copilot
• vibe

Recommended CLI install channels:

npm install -g @anthropic-ai/claude-code
npm install -g @openai/codex
npm install -g @github/copilot
uv tool install mistral-vibe

Start the cockpit

./scripts/constant-machine.sh --workspace "$PWD"

Start the fleet cockpit

./scripts/constant-fleet.sh --workspace "$PWD"

For non-interactive setup or tests, you can create the sessions without attaching:

./scripts/constant-machine.sh --workspace "$PWD" --ensure-only
./scripts/constant-fleet.sh --workspace "$PWD" --ensure-only

On first launch of the Codex pane, if auth.json is missing in its profile, the pane runs:

codex login --device-auth

Start Constant

./scripts/Constant
./scripts/Constant tui
./scripts/Constant doctor
./scripts/Constant cockpit doctor --json
./scripts/Constant cockpit status --json
./scripts/Constant cockpit status-line --workspace "$PWD"
./scripts/Constant cockpit focus --machine command-center --pane codex
./scripts/Constant cockpit capture --machine command-center --pane claude
./scripts/Constant mission create "audit the repo" --workspace "$PWD"
./scripts/Constant mission delete <mission_id> --json
./scripts/Constant mission status
./scripts/Constant memory rebuild --workspace "$PWD"
./scripts/Constant memory search "buddy rail" --workspace "$PWD"
./scripts/Constant memory sync-qdrant --workspace "$PWD" --json
./scripts/Constant cockpit open --workspace "$PWD"
./scripts/Constant fleet status --json
./scripts/Constant fleet sync --json

If Constant is on your PATH, you can also just run:

Constant

In interactive mode, Constant with no arguments now opens or attaches the full fleet cockpit by default.

That means:

• a top tmux tab bar for Constant, the local machine, and each remote machine
• the active tab is forced back to Constant when you launch constant
• the Constant TUI inside the central Constant window
• one machine window per host in the fleet

The central Constant window now runs the native Rust chat-first TUI directly.

The current interaction model is:

• chat-first by default
• prompt focused on launch
• / opens the workflow skill palette
• Esc drops into cockpit command mode
• f toggles between chat-focus and cockpit-detail

If you want only the standalone TUI without attaching the fleet session, use:

./scripts/Constant tui --workspace "$PWD"

Discover and deploy a fleet

Constant now ships with a public discovery/deployment CLI that:

• scans ~/.ssh/config
• scans ~/.ssh/known_hosts
• scans local arp -a neighbors
• validates candidates with a short SSH probe
• lets you select targets interactively
• asks for SSH user and machine labels
• writes ~/.config/constant/fleet.toml and a compatibility fleet.json mirror
• can immediately deploy the runtime to the selected machines

Examples:

./scripts/constant-deploy.sh scan --json
./scripts/constant-deploy.sh configure
./scripts/constant-deploy.sh deploy

You can pass raw SSH seeds such as:

• dev@builder-a
• root@192.168.0.119
• lab-a

If fleet.toml or fleet.json contains repo_dir, the shell launchers and fleet installer will reuse it automatically.

For a fully non-interactive run, pass explicit hosts and --yes:

./scripts/constant-deploy.sh configure \
  --host builder-a \
  --host builder-b \
  --user dev \
  --repo-dir '$HOME/constant' \
  --local-label command-center \
  --yes

TUI keys

Constant tui now gives you:

• a chat-first central conversation surface
• a thread sidebar
• a chat-focus mode that behaves closer to Claude Code
• a detailed cockpit view you can toggle back in when needed
• a capture popup for pane output
• persistent unread tracking across sessions
• a bottom status / key strip

Useful keys:

• j / k: move between missions
• f: toggle chat-focus / cockpit-detail
• [ / ]: move between machines in the runtime view
• 1..4: select claude, codex, copilot, vibe on the selected machine
• o: focus the selected machine + pane in the real cockpit
• r: restart the selected pane
• x: open a capture view of the selected pane
• z: open the full fleet cockpit
• q: quit the TUI

Fleet Configuration

For a public setup, think in terms of roles, not personal machine names.

Example shape:

command-center=local
builder-a=dev@builder-a
builder-b=dev@builder-b
edge-a=dev@edge-a
lab-a=dev@lab-a

The command-center machine is where you run:

• Constant
• the fleet cockpit
• local heuristic orchestration
• any human-in-the-loop supervision

The workers are where execution happens.

Public example config:

mkdir -p ~/.config/constant
cp examples/fleet.example.toml ~/.config/constant/fleet.toml

Legacy ~/.config/constant/fleet.json and fleet.yaml are still read for compatibility, but the native format is now TOML. The shell launchers and Rust CLI read both fleet.toml and fleet.json, so fleet tabs, install/check, and bridge helpers stay aligned.

Messaging

Each machine exposes a local bus:

~/.cache/constant/cockpit/<session>/bus

Use it from any pane:

ai-msg.sh send --to codex --message "look at the failing test"
ai-msg.sh send --to vibe --message "explore two alternatives"
ai-msg.sh broadcast --message "new constraints in README"
ai-msg.sh inbox --for claude

Bridge between machines from the command center:

./scripts/ai-bridge.sh send \
  --from-machine command-center \
  --from claude \
  --to-machine lab-a \
  --to codex \
  --message "take over the deep refactor"

Clipboard

Clipboard behavior is split on purpose:

• local macOS sessions can use pbcopy
• remote tabs rely on OSC52
• the command center keeps ownership of the actual system clipboard

The current runtime relies on tmux clipboard forwarding and terminal OSC52 behavior when you are driving remote sessions from the command center.

Constant Philosophy

Constant is not trying to hide the terminal.

It assumes:

• the shell matters
• sessions matter
• state matters
• local files matter
• naming things matters
• supervision matters

The system should feel like:

• a cockpit
• a score
• a routing table
• a machine that keeps its shape under pressure

Not like a magic trick.

Public Repo Roadmap

Planned layers for the public Constant repo:

• a real demoscene-style TUI
• durable memory with vector + lexical search
• mission summaries and decision graph browsing
• richer repo context and instruction fusion
• cleaner public fleet templates
• screenshots, gifs, and a proper visual identity

Repo Layout

src/                              Rust CLI, missions, cockpit, native TUI, memory, and chat store
tests/                            Rust integration tests
examples/fleet.example.json       public fleet template
examples/fleet.example.toml       public fleet template in the native config format
scripts/Constant                  canonical CLI entrypoint
scripts/constant-deploy.sh        discovery + selection + fleet deployment CLI
scripts/constant-machine.sh       canonical single-machine cockpit entrypoint
scripts/constant-fleet.sh         canonical fleet cockpit entrypoint
scripts/constant-fleet-install.sh canonical fleet installer/checker
scripts/ai-msg.sh                 local agent bus
scripts/ai-bridge.sh              inter-machine bridge

Current Caveats

• the shell runtime still keeps some historical compatibility wrappers
• the public-facing TUI is still evolving
• some setup paths and local assumptions are operator-oriented
• copilot is manual-only in the current autonomous flow
• remote tmux introspection is best when targets expose tmux on a non-interactive shell PATH

That is acceptable for now. The system is being built in the open, from the terminal outward.

Contributing

If you open this repo and think:

“this is a little unhinged, but technically serious”

then you probably understood the assignment.