Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,15 @@ has a matching GitHub release whose body comes from its section below.

## [Unreleased]

## [v0.6.0] - 2026-11-14

v0.6.0 gives each card a schedule and makes Berth explain its choices. `berth schedule` books an engine's hours,
a priority change or downtime up to 14 days ahead, agents book their own runs through the gateway, and the
harbor's SCHEDULE tab shows the week. `berth train` runs a training that nothing automated can interrupt.
`berth fit`, `berth contract`, `berth queue` and `berth why` say where a request would run, what an engine costs,
who is next and why a lease waited or was drained. The event log now survives restarts. It was tagged first as
`v0.6.0-rc.1`.

### Added

- `berth why ID` tells one lease's story in plain words: when it asked for the card, each reason it waited, the
Expand Down
16 changes: 15 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ claim. When another engine holds it, Berth:
The numbered markers on the timeline are those four steps. A process that holds VRAM without a lease
shows up as a stowaway: Berth reports its PID and memory and leaves it running.

> **Status: alpha, v0.5.0.** Runs daily on an RTX 4090 workstation beside llama-swap, NInfer,
> **Status: alpha, v0.6.0.** Runs daily on an RTX 4090 workstation beside llama-swap, NInfer,
> Strata, ComfyUI and games, and testers run it on Windows. The [docs](docs/README.md) cover what works and has tests; the
> [roadmap](docs/roadmap.md) lists the phases and what is still missing.

Expand Down Expand Up @@ -116,6 +116,16 @@ line goes away.
[Training runs](docs/leasing.md#training-runs).
- **`berth run --pinned`** for an app that must never be stopped mid-work but may share the card, such as Blender.

**Plans the card's hours**
- **A schedule per card.** `berth schedule book` gives an engine the card for set hours, changes its priority for
them, or books downtime, up to 14 days ahead. A booked run goes first and keeps the card against everything but
a hold. Hours nobody booked run by priority, then arrival. See [Book the card](docs/leasing.md#book-the-card).
- **Agents book their own runs** through `/v1/berth/schedule` on the gateway, and the harbor's SCHEDULE tab shows
the week to the minute. A paired phone books by clicking an empty hour.
- **`berth queue`** lists the waiters in grant order. `bump`, `prio` and `drop` change one by hand.
- **`learn_size = true`** sizes a lease from what the engine held last time, so engines that fit together share
the card without anyone typing `needs_mib`.

**One API for your engines** *(preview)*
- **`berth gateway`**: one OpenAI-compatible port. Name a model and Berth starts its engine,
unloads whatever holds the card, waits for the load and streams the answer.
Expand Down Expand Up @@ -161,6 +171,10 @@ line goes away.
leaderboard; 30 days of history on disk.
- **The harbor web UI** (`berth harbor`): a departures board of leases, a collisions-avoided
counter, charts and the event log. Read-only, loopback by default.
- **Explains itself.** `berth why ENGINE` tells that engine's last lease in plain words: each wait and its
reason, the grant, each drain and who it was for, and the restarts it lived through. `berth fit MODEL` says where
a request would run now and what the start costs, and `berth contract ENGINE` prints an engine's VRAM, RAM, turn
and switch times, each marked declared, measured or unknown. The event log is kept on disk across restarts.
- **Alerts** to the desktop or a webhook, `/metrics` for Prometheus, and `berth export` for
CSV or JSON.

Expand Down
6 changes: 3 additions & 3 deletions docs/prerelease.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Testing a pre-release

Work for the next release lands on the `next` branch before it reaches `main`. When it is ready for testers, it is
tagged as a pre-release (`v0.5.0-rc.1`, then `rc.2` and so on) on the
tagged as a pre-release (`v0.6.0-rc.1`, then `rc.2` and so on) on the
[releases page](https://github.com/T-Crypt/berth/releases), marked **Pre-release**.

Your normal install is not affected. The README's download link, `go install ...@latest` and `berth update` all stay
Expand All @@ -15,7 +15,7 @@ how it works. Back up `berth.toml` before you switch.
Pick the tag from the releases page, then on Linux:

```sh
TAG=v0.5.0-rc.1
TAG=v0.6.0-rc.1
cd /tmp
curl -fLO https://github.com/T-Crypt/berth/releases/download/$TAG/berth-linux-amd64
curl -fLO https://github.com/T-Crypt/berth/releases/download/$TAG/SHA256SUMS
Expand All @@ -31,7 +31,7 @@ it where your current `berth.exe` is, and restart Berth the way you started it.
Or build it with Go 1.27 or newer:

```sh
go install github.com/T-Crypt/berth/cmd/berth@v0.5.0-rc.1 # a tagged pre-release
go install github.com/T-Crypt/berth/cmd/berth@v0.6.0-rc.1 # a tagged pre-release
go install github.com/T-Crypt/berth/cmd/berth@next # the newest commit on next
```

Expand Down
41 changes: 27 additions & 14 deletions docs/roadmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -130,25 +130,38 @@ v0.5.0 was tagged first as `v0.5.0-rc.1`.
- **Restarts.** A run that started before berthd, or lost it, re-attaches when a daemon answers, and berthd
logs a refused re-attach with its reason.

## Next: v0.5.x, models across machines

In `next` for the next release candidate:

- **A yield for a ComfyUI job that calls an LLM** ([#299](https://github.com/T-Crypt/berth/issues/299)). The job
gives the card to the LLM it calls and takes it back, in place of a deadlock until the call times out.
- **`berth notify` on Windows**, a tray icon with native toasts ([#186](https://github.com/T-Crypt/berth/pull/186)).
`berth service install --notify` on Windows still needs its test on a real desktop.

Planned:

## Shipped: v0.6.0, a schedule per card (2026-11-14)

v0.6.0 was tagged first as `v0.6.0-rc.1`.

- **A schedule.** `berth schedule book` books an engine's run, a priority change or downtime on a card, up to 14
days ahead. Agents book their own runs through `/v1/berth/schedule`, and the harbor's SCHEDULE tab shows the
week. Hours nobody booked run by priority, then arrival.
- **Training runs.** `berth train` takes whole cards for a fine-tune, refuses every other request on them at once,
and with `--exclusive` locks the card in the driver.
- **Answers about the card.** `berth fit` ranks where a request would run, `berth contract` lists an engine's
terms, `berth queue` shows and changes the grant order, and `berth why` tells one lease's story. The gateway
picks through the same ranking as `berth fit`.
- **Learned sizes.** `learn_size = true` sizes a lease from the engine's measured peak.
- **A yield for ComfyUI jobs that call an LLM** ([#299](https://github.com/T-Crypt/berth/issues/299)), and
`berth notify` as a Windows tray icon ([#186](https://github.com/T-Crypt/berth/pull/186)).
- **Restarts.** The event log and lease numbers carry on across a berthd restart, a re-attached engine keeps the
turn it was in, and a drain no longer stops an engine that is still resuming
([#275](https://github.com/T-Crypt/berth/issues/275)).

## Next: v0.6.x

- **A warmth ladder.** An engine steps down from live to parked to stopped by idle time and the next booking, and
`berth why` names each step.
- **A booked run starts its engine** at the start of its hours, for engines the gateway can launch.
- **The soonest node.** When several nodes serve a model, send the request to the one where it is warm or the
card is free, by the same reach order a node uses for its own cards.
- **One board.** The harbor's SWITCH tab shows each peer's cards and engines beside this node's.
card is free.
- **Device names.** A key per device, so the queue and the schedule say "mac" or "pi-pocket", and a booking
belongs to the device that made it.

Still to decide, with data from multi-card users:

- Whether a cordon survives a berthd restart. Today it lives in berthd's memory, and a restart clears it.
- Whether measured switch costs rank the cards for a plain `/v1` request. Today the gateway ranks them by reach.

## Also queued

Expand Down
Loading