Skip to content
Commands

Command reference

Quick reference

CommandDescription
kobe statusShow endpoint status, auth methods, and pool summary
kobe versionShow CLI and endpoint versions
kobe runLease an executable resource, run one command, release it (details)
kobe execRun a command in a lease that supports exec
kobe logsRead output from a lease that supports logs
kobe cancelCancel a running execution
kobe attachOpen an interactive session through an attach capability
kobe port-forwardForward a declared port through a port-forward capability
kobe loginAuthenticate with the kobe service
kobe logoutRemove stored credentials
kobe lease <pool>Lease the resource provided by a pool
kobe release <lease-id>Release a lease
kobe config viewPrint current configuration
kobe config editOpen the configuration TUI
kobe config listList named targets
kobe config currentShow the current target
kobe config use <name>Switch the current target
kobe config set <name> --endpoint ...Create or replace a named target

kobe status

kobe status

Queries GET /v1/status on the configured endpoint. Shows the operator version, available auth methods, active sessions, and pool summary. Does not require authentication.

Useful for verifying connectivity and checking which auth methods the endpoint accepts before logging in.

Authenticated pool rows include the pool phase and a quarantined count. A non-zero count means cleanup evidence is incomplete and that capacity remains withheld; it is not reported as healthy or available.


kobe version

kobe version

Prints the local CLI version and, when reachable, the endpoint version reported by GET /v1/status.


kobe login

kobe login

Authenticates with the configured kobe endpoint. The flow depends on the configured auth mode:

  • ssh — challenges your SSH agent to sign with your Ed25519 key
  • token — validates the token set in config or KOBE_TOKEN
  • oidc — opens a browser for OIDC authentication

On successful login, kobe stores a session token locally. Subsequent commands use the stored token without re-prompting.


kobe logout

kobe logout

Removes the stored session token and credentials from the local config. The next command that requires auth will prompt you to log in again.


kobe lease

kobe lease <pool> [--ttl <duration>] [--kubeconfig <path>] [--metadata-json <json|@path>] [--no-wait]

Creates a lease from the specified pool. The pool's resourceKind determines what is allocated and which actions are available. Cluster leases write a kubeconfig; executable resources expose actions such as exec and logs.

kobe lease ci-small
kobe lease ci-small --ttl 30m
kobe lease ci-small --kubeconfig /tmp/kube.yaml
kobe lease agents --ttl 30m
kobe lease ci-small --metadata-json '{"github":{"actor":"lenij","pullRequest":3835}}'
kobe lease ci-small --metadata-json @lease-metadata.json
kobe lease ci-small --no-wait

Prints the lease ID, resource kind, capabilities, and expiry on success.

Flags

FlagDefaultDescription
--ttlpool defaultRequested lease TTL. Capped by AccessPolicy maxTtl.
--kubeconfig~/.kube/kobe-<id>Cluster resources only: path to write the kubeconfig.
--no-waitdisabledReturn after creating the lease instead of waiting for readiness.
--wait-timeoutunsetMaximum time to wait for the lease to become usable.
--metadata-jsonunsetOpaque descriptive JSON object, passed inline or read from @path. Metadata is bounded by the server and never affects lease behavior.

Metadata is stored with the lease and returned to its owner. Do not include credentials or secrets; cluster administrators can inspect it. When --ensure reuses an existing named lease, that lease keeps its original metadata.


Lease visibility

kobe status

The current CLI does not expose a standalone kobe leases command anymore. Use kobe status for an endpoint summary plus your active leases, or query GET /v1/leases directly.


kobe release

kobe release <lease-id>

Releases a lease immediately. Kobe performs the cleanup required by that resource kind and makes the pool capacity reusable. Use this when work finishes before the TTL expires.

kobe release lease-a1b2c3d4e5f6

kobe config

kobe config view
kobe config edit
kobe config list
kobe config current
kobe config use work
kobe config set work --endpoint https://kobe.example.com --auth ssh

The CLI stores named targets in ~/.config/kobe/config.json. Most users set up one or more targets and switch between them with kobe config use.

Common subcommands

CommandDescription
kobe config viewShow the full config, including named targets
kobe config editOpen the TUI editor
kobe config listList named targets
kobe config currentShow the current target
kobe config use <name>Switch the active target
kobe config set <name> ...Create or replace a named target
kobe config set work --endpoint https://kobe.example.com --auth ssh
kobe config use work
Available for:
Apple macOS logomacOSMicrosoft Windows logoWindowsLinux logoLinux
Download Kunobi