clay

The archive

Releases

Verified Clay builds with bundled Python 3.11 for macOS and Linux. Choose core for the command line and daemon, or UI for the Qt desktop.

0.1.2 stable

# 2026-08-15 — 0.1.2

## Configuration

- `clay configure` (and its `clay config` alias) now also prompts for a
default response token limit, saved as `maxTokens` in
`~/.clay/config.json` alongside the provider URL and model profiles. New
configs default to `4096`. The `scramda2` action uses this value whenever an
action does not set its own `max_tokens`; an action-level value still wins.
- Curl-based release installs run the installed version's config migration on
upgrade. It adds `maxTokens` to older configs without touching existing
settings, and never overwrites an existing `maxTokens` value. A read-only
config file still works — Clay falls back to the built-in default in memory.
- Every `clay` invocation (other than `configure` itself) now runs a
configuration check before the command executes: missing config file, a
malformed or unreachable server URL, or a model profile the server doesn't
actually serve. For local llama.cpp Hugging Face cache paths, the check
decodes the real `owner/repository` from the cache path instead of guessing
from the GGUF filename. Connection and malformed-config problems are
advisory; an actual loaded-model mismatch stops before the command runs and
asks for confirmation.

## `system/editor` — structured, checklist-driven task completion

The editor workflow now drives multi-file builds from a written `PLAN.md`
checklist instead of trying to hold the whole task in one pass:

- Each turn, the workflow picks the next unfinished file off the plan, writes
it, verifies it, and reviews the result — then updates the plan's `[x]`
checkboxes only when the write succeeded, the saved content actually
contains the file, and verification passed. A file is never marked done on
the model's say-so alone.
- `outputKey` lets an action overwrite the plan document in place as each file
completes, so the checklist on disk always reflects real, verified progress
rather than a running commentary beside it.

## Improved workflows

- **`system/clay`** — a chat-workflow addition for answering
questions about Clay's own workflow syntax and capabilities.

- **`system/coding`** - a coding agent loop that creates structured
tasks and completes them

- **`aws`** - some templates for workflows that will create terraform projects
from user input

## Also in this release

- Workflow token-usage linting and a new CLI reference document.
- `outputKey` documentation and lint fixes across the action registry and
workflow schema docs.

Source archiveSource signature

0.1.0 stable

# 2026-08-08 0.1.0 launch

Clay 0.1.0 is the first release published to the public repository,
[dpayne9000/clay](https://github.com/dpayne9000/clay). Everything in this
document, and everything else under `docs/release-notes/`, ships there via
the allowlisted mirror in `scripts/git_release/` — this is the first entry
written specifically for that audience rather than for internal tracking.

Clay runs JSON-defined AI and automation workflows from the command line, a
background daemon, or an optional Qt desktop application. Workflow actions
pass structured context to later actions, can call local
OpenAI-compatible model servers, and can operate on approved project
directories under explicit safety guards.

## Install

```bash
curl --proto '=https' --proto-redir '=https' -fsSL \
https://get.clay.dev/install.sh | sh
```

The installer selects the correct macOS/Linux ARM64 or x86-64 release,
verifies its SHA-256 value against the signed release manifest, and installs
Clay with its bundled CPython runtime and offline dependency wheelhouse. The
Qt desktop edition installs the same way with `-- --ui` appended. See
[README.md](../../README.md#installation) for the downloaded-archive path
and WSL2 notes.

## License

Clay is source-available for private, internal, non-commercial use under the
Clay Private Use Source License 1.0 (see [LICENSE](../../LICENSE)).
Commercial use requires a separate written license from the copyright
holder. This is explicitly not an open-source license as defined by the
Open Source Initiative — the source is visible and modifiable for personal
use, but redistribution, hosting as a service, and commercial use are not
granted by default.

Clay is distributed from the Clay HTTPS release site; it is not published to
PyPI or another public package registry.

Source archiveSource signature