kraal 0.3.0

A terminal workspace manager for SSH fleets and coding agents
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# Install

kraal is a single binary for Linux (x86_64, arm64) and macOS (Apple Silicon, Intel). Linux is the
primary target; macOS passes the test suite but is not used day to day yet. Windows is not
supported.

## The install script

```sh
curl -fsSL https://raw.githubusercontent.com/kraal-sh/kraal/main/install.sh | sh
```

The script takes the archive for your machine from the
[releases](https://github.com/kraal-sh/kraal/releases) and checks it against its checksum before
installing anything, into `~/.local/bin`. Settings:

| Variable | |
|---|---|
| `KRAAL_VERSION` | a release tag such as `v0.1.0` (the latest by default) |
| `KRAAL_INSTALL_DIR` | where the binary goes (`~/.local/bin` by default) |
| `KRAAL_DOWNLOAD_URL` | where the archives are, instead of GitHub (a mirror) |

## Updates

`kraal update` replaces kraal with the latest release the same way: `--check` only says whether
there is one, `--to v0.2.0` picks one. A kraal installed by Cargo or a package manager (Homebrew,
Nix, your distribution) is updated there instead.

A session's server keeps the version it started with. After installing, `kraal update` lists the
sessions still on an older kraal, with the programs a restart would stop in them, and offers to
[restart](workspaces.md#persistence) them: no by default when programs would stop, and without a
terminal to ask on; `--restart` or `--no-restart` answer beforehand. Later, `kraal ls` shows the
version each session runs, attaching to a session on an older kraal says so, and
`kraal restart` (or `ctrl+b W r`) restarts it.

## With Cargo

```sh
cargo install kraal                                  # the latest release, from crates.io
cargo install --git https://github.com/kraal-sh/kraal  # the main branch
```

`cargo install kraal` again updates it to the latest release; `kraal update` leaves a kraal that
Cargo installed to Cargo.

## By hand

Each [release](https://github.com/kraal-sh/kraal/releases) has an archive per platform, its
`.sha256`, and `SHA256SUMS`. The Linux builds are static (musl), so they run on any
distribution.

## On a server

`kraal remote-install <server>` copies the running binary to `~/.local/bin` on a server of the
same OS and CPU, for [remote sessions](servers.md#remote-sessions).