Karneleon Terminal

One terminal. Many repos. Modular by design.

Karneleon Terminal is the agentic command surface for managing modular, multi-repo projects — clone, link, build, test, release, and let Leon drive cross-repo work safely from one workspace.

View Repo Install

Rust-nativeLocal-firstCapability-securedAgent-driven

kterm — my-product

$ kterm sync
$ → core      ✓ pulled  (v0.4.2)
$ → ui        ✓ pulled  (main → 9f2a1c)
$ → api       ✓ pulled  (main → 31bb04)
$ → infra     ✓ pulled  (stable)
 
$ kterm run build
$ [core ] cargo build  ─ ok  4.1s
$ [api  ] pnpm build   ─ ok  6.8s
$ [ui   ] pnpm build   ─ ok  7.2s
$ ✓ workspace built in 7.4s (3 modules, topological)

Capabilities

Built for modular multi-repo work

Karneleon Terminal treats every linked repo as a first-class module — composable, releasable, and orchestrated from a single command surface.

Workspace Graph

Compose many repositories into one virtual workspace with declarative manifests, version pins, and dependency graphs.

Multi-Repo Git

Clone, branch, status, commit, and PR across every linked repo with one command. Atomic operations, per-repo overrides.

Modular Projects

Each module is its own repo with a manifest. Karneleon links them at runtime — keep ownership, reuse, and release cadence independent.

Orchestrated Tasks

Run build, test, lint, deploy pipelines that fan out across repos with topological awareness and parallelism.

Skill-Aware

Every command is a Karneleon skill. Leon can drive the terminal, propose plans, request approvals, and execute safely.

Unified Observability

Stream logs from all repos in one TUI. Filter by module, severity, or task. Time-aligned views for cross-repo debugging.

Workspace Manifest

One manifest. Many repos.

Declare your modules, pin versions, define cross-repo tasks, and codify policy. The workspace becomes a versionable, reproducible unit — without forcing a monorepo.

Each module keeps its own repo, history, and release cadence.
Pin to tags, branches, or commits for reproducibility.
Tasks fan out with topological order and parallelism.
Policy gates dangerous operations behind approvals.

karneleon.workspace.json

{
  "name": "my-product",
  "modules": {
    "core":     { "repo": "github.com/kordspace/karneleon-core",   "ref": "v0.4.2" },
    "ui":       { "repo": "github.com/acme/product-ui",            "ref": "main" },
    "api":      { "repo": "github.com/acme/product-api",           "ref": "main" },
    "infra":    { "repo": "github.com/acme/product-infra",         "ref": "stable" }
  },
  "tasks": {
    "build":  { "fanout": ["core", "api", "ui"], "ordered": true },
    "deploy": { "fanout": ["api", "ui"], "requires": "approval" }
  },
  "policy": {
    "deny": ["git push --force", "rm -rf"],
    "approval": ["deploy", "release"]
  }
}

Command Surface

A small, sharp CLI

Composable verbs that work the same way against one repo or a hundred.

$ kterm init my-product

Create a new modular workspace with a karneleon.workspace.toml manifest.

$ kterm add github.com/kordspace/karneleon-core

Link a repo as a module. Pin a tag, branch, or commit.

$ kterm sync

Clone or pull every linked module in parallel, respecting the dependency graph.

$ kterm run build

Run a task across all modules with topological ordering and live log multiplexing.

$ kterm status

Cross-repo status: dirty trees, ahead/behind, failing tasks, unresolved approvals.

$ kterm release v1.4.0

Coordinated release train: bump versions, tag, push, publish — guarded by policy.

$ kterm agent plan 'upgrade tokio to 1.40 everywhere'

Ask Leon to draft a multi-repo change plan and walk it through approval.

Why Karneleon Terminal

Monorepo ergonomics. Polyrepo freedom.

Without giving up ownership boundaries, independent release cadence, or the ability for agents to safely operate across the whole product.

Modular > Monolithic

Monorepos centralize everything; lonely repos lose context. Karneleon Terminal gives you composable repos with monorepo ergonomics.

Capability-Secured

Inherits Karneleon's deny-by-default policy. Risky actions (force-push, deploy, rm) require explicit capabilities or approvals.

Agent-Native

Built so Leon and sub-agents can plan and execute multi-repo work — refactors, dependency bumps, release trains — under your watch.

Local-First

Runs entirely on your machine. No SaaS lock-in, no remote runners required, no source code leaves your filesystem.

Quick Start

Install and link your first module

Karneleon Terminal ships as a single Rust binary. Once installed, your workspace lives in any directory you choose.

install — kterm

$ cargo install karneleon-terminal
$ kterm init my-workspace
$ cd my-workspace
$ kterm add github.com/kordspace/karneleon-core
$ kterm sync
$ kterm run build

kordspace/karneleon-terminal Karneleon Core

Open source · Kordspace LLC · v0.1 in active development