diff --git a/CHANGELOG.md b/CHANGELOG.md index a737be3..dd8d8a5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,6 +9,19 @@ remain historical snapshots. Beta does not mean error-free operation. ## [Unreleased] +## [0.20.0] — 2026-11-11 + +### Stable release + +- Promote the RC.3 runtime to stable 0.20.0 with the frozen operator contract, + unchanged permissions and unchanged dependency locks. This release adds no + runtime behavior beyond the version identifier. +- Carry forward safe Hermes/OpenClaw migration, Talos Connections, managed skills, + labelled scheduled results and the pypdf 6.21.4 security fix. +- Require the seven-day RC observation review and independent qualification of + the final signed archive, including RC.3-to-stable upgrade and rollback. +- Keep the next Telegram live-display update separate from this release. + ## [0.20.0-rc.3] — 2026-11-05 ### Added diff --git a/README.md b/README.md index 01e8674..d4e5764 100644 --- a/README.md +++ b/README.md @@ -39,7 +39,7 @@ Tools Default identities Python - Latest release, including prereleases + Latest stable release MIT

@@ -54,8 +54,8 @@ tools — but only after a deterministic permission kernel has ruled on the acti Choose **Allow once**, **Allow this task**, or an exact-action standing approval; you do not have to approve every step individually. Sandboxed shell execution and an append-only audit trail keep actions bounded and reviewable. Talos is MIT-licensed; -model-provider and hosting costs depend on your setup. It is now a **release candidate**: the -[operator contract](docs/beta-contract.md) is frozen; RC is not a claim of error-free +model-provider and hosting costs depend on your setup. The **0.20.0 stable** release retains the frozen +[operator contract](docs/beta-contract.md). Stable is not a claim of error-free operation or a substitute for reviewing permissions and keeping backups. [Install Talos](#install) · [Run local models with Ollama](https://talos-agent.ch/docs/#model) · @@ -70,12 +70,12 @@ a handover, save and read back a local note, and compare release notes without i missing facts. Already tried it? [Share your first-run result](https://github.com/talos-kernel/Talos/issues/new?template=first_run.yml), including installation blockers. No star or positive review required. -**Latest signed release — [0.20.0-rc.3](https://github.com/talos-kernel/Talos/releases/tag/v0.20.0-rc.3):** -this candidate adds safe agent migration, Talos Connections and labelled scheduled -results. It retains the pypdf 6.21.4 security fix and starts a fresh observation -window before stable 0.20.0. +**Latest signed release — [0.20.0](https://github.com/talos-kernel/Talos/releases/tag/v0.20.0):** +this stable release carries forward the qualified RC.3 runtime: safe agent migration, +Talos Connections and labelled scheduled results, including the pypdf 6.21.4 +security fix. The operator contract and permissions remain unchanged. -**New in RC.3:** migration from Hermes or +**Included in 0.20.0:** migration from Hermes or OpenClaw can now fingerprint and apply an exact redacted plan into inactive staging, archive that staging for recovery, and activate one validated imported skill at a time. [Talos Connections](docs/connections.md) adds secret-free disabled connector drafts and @@ -94,7 +94,7 @@ See the **Source versus release:** `main` can contain newer changes. Signed installers and package managers follow their pinned release; older archives remain immutable. -RC.3 includes the Beta.8 pip 26.2.2 hash lock and isolates pip from per-user +0.20.0 includes the Beta.8 pip 26.2.2 hash lock and isolates pip from per-user configuration. When upgrading from Beta.7 or older with custom pip settings, use `PIP_CONFIG_FILE=/dev/null talos update` once; those older updaters still inherit pip configuration. @@ -107,7 +107,7 @@ configuration. - **Inspect the evidence:** review tool outcomes and the audit trail; do not mistake a confident answer for a successful action. Start with the [model, cost and permission FAQ](https://talos-agent.ch/faq/). -Talos is not Talos Linux or Cisco Talos. It is a self-hosted AI agent, and it remains a prerelease. +Talos is not Talos Linux or Cisco Talos. It is a self-hosted AI agent, with a stable 0.20.0 release. If this approach is useful, **star the repository to bookmark it**, try a small task and [report a reproducible result](https://github.com/talos-kernel/Talos/issues). Want to improve it? [Fork Talos](https://github.com/talos-kernel/Talos/fork) and read @@ -423,7 +423,7 @@ come from `stdin` instead of `getUpdates`. ``` $ talos chat - ◉ Talos / 0.20.0-rc.3 + ◉ Talos / 0.20.0 Your terminal. Your rules. ────────────────────────────────────────────────────────────────────────── model claude-cli/claude-opus-4-1 @@ -987,10 +987,10 @@ The [beta release evidence](docs/beta-readiness.md) separates source tests, sign artifact checks and the seven-day operating observation. The frozen [beta contract](docs/beta-contract.md), [recovery runbook](docs/recovery.md) and local `python scripts/beta-gate.py --previous ` make these checks repeatable. -The [RC and stable qualification plan](docs/stable-readiness.md) tracks the next -transition from beta through `0.20.0-rc.3` to `0.20.0`; stable remains subject to the RC observation and final-artifact gates. The path to 1.0 -requires evidence from the beta line and a verified upgrade from a previous beta; -it is not a calendar promise. +The [stable qualification record and gates](docs/stable-readiness.md) cover the +transition from RC.3 to `0.20.0`, including seven days of deployed observation and +separate final-artifact checks. The path to 1.0 remains a separate compatibility +commitment supported by operating and upgrade evidence; it is not a calendar promise. 1. `openat2()` with `RESOLVE_BENEATH` instead of realpath checks. 2. **An adapter seam for tools.** Adding a channel is already just implementing a diff --git a/docs/stable-readiness.md b/docs/stable-readiness.md index 558bf60..5f9aa73 100644 --- a/docs/stable-readiness.md +++ b/docs/stable-readiness.md @@ -1,9 +1,10 @@ # From beta to a stable 0.20.0 -This tree identifies `0.20.0-rc.3`, followed by `0.20.0` only after the evidence -below passes. Publication is established by the signed release assets, not this -source label. The upgrade baseline is `0.20.0-rc.2`. RC.3 adds safe agent migration, Talos -Connections and labelled scheduled results; its deployed observation window starts afresh. +This tree identifies stable `0.20.0`, retaining the RC.3 runtime and frozen operator +contract. Publication is established by the signed release assets, not this source +label. The upgrade baseline is `0.20.0-rc.3`. Deployed RC.3 observation covers +5–11 November 2026; the final stable bytes still require every gate below. +The next Telegram live-display update is deliberately separate from this release. The historical `0.20.0-alpha.rc.*` artifacts qualified the earlier transition **into beta**. They are not candidates for this transition out of beta. `1.0.0` @@ -31,7 +32,7 @@ not silently included in a broad claim that everything passed. | Real model flow | Isolated real-model E2E: read, approval/refusal, exactly-once effect, restart/state restoration and the event chain. Record provider and results; do not send external test messages. | | User-visible flow | Telegram reply/approval/background completion behavior, including conversation isolation and no false completion while waiting. Injected transport tests and an actual service probe are distinct evidence. | | Exact artifact | Build from the qualified public commit; SHA-256, pinned Ed25519 verification, tamper rejection and archive hygiene. Source tests alone do not qualify an archive. | -| Installation/recovery | Clean install and RC.2→RC.3 signed upgrade on macOS and ARM64 Linux; check operator identity/configuration, selected model, history, schedules, file modes and rollback. Rehearse isolated service restart and retain the prior runtime. | +| Installation/recovery | Clean install and RC.3→0.20.0 signed upgrade on macOS and ARM64 Linux; check operator identity/configuration, selected model, history, schedules, file modes and rollback. Rehearse isolated service restart and retain the prior runtime. | | Delivery | Native Homebrew lifecycle, Pinokio clean/repeated install, and byte-for-byte HTTPS read-back of the release, website and installer definitions. Check main CI after each merge. | | Observation before stable | Seven consecutive calendar days on a deployed RC, with daily health/event-chain records, investigated errors, no unexplained restart and no unresolved security or data-loss regression. Preserve failed samples. A release-blocking runtime fix starts a new candidate/window. | | Stable promotion | Rebuild/sign the final version and requalify its exact bytes, including RC→stable upgrade and recovery. A version-only change is still a new artifact. | @@ -48,7 +49,7 @@ Start with the current published baseline in a prepared, hash-locked development environment: ```sh -python scripts/beta-gate.py --previous 0.20.0-rc.2 --current 0.20.0-rc.3 +python scripts/beta-gate.py --previous 0.20.0-rc.3 --current 0.20.0 python -m pytest macos/Tests -q python e2e.py ``` @@ -59,8 +60,8 @@ dependency locks, a disposable clean install, and signed upgrade/migration/rollb `--without-upgrade` is a partial source check and says so; it does not qualify a candidate. Tests and artifact downloads require their normal dependencies/network. -For an unpublished candidate, use `--current 0.20.0-rc.3`, `--previous -0.20.0-rc.2`, an explicit `--base` pointing to the candidate's `dist/` directory +For an unpublished candidate, use `--current 0.20.0`, `--previous +0.20.0-rc.3`, an explicit `--base` pointing to the candidate's `dist/` directory parent, and `--assets-dir` containing both versions' archive/checksum/signature. The checkout's installer must name the candidate. The existing scripts support `file://` for an isolated pre-publication install. Run against the actual signed @@ -92,6 +93,6 @@ installation or restart its service. |---|---|---| | `0.20.0-beta.9` | Published baseline | [Core main CI](https://github.com/talos-kernel/Talos/actions/runs/40661310306), [Homebrew](https://github.com/talos-kernel/homebrew-tap/actions/runs/40661911664), [Pinokio](https://github.com/talos-kernel/talos-pinokio/actions/runs/40663657826). These qualify beta.9 only. | | `0.20.0-rc.1` | Published, superseded candidate | Original signed assets remain available. Its observation days do not qualify RC.3. | -| `0.20.0-rc.2` | Published upgrade baseline | Original signed security release remains available; qualification now rehearses RC.2→RC.3. | -| `0.20.0-rc.3` | Candidate source | Requires matching signed assets and platform/install/recovery evidence; seven new observation days start after rollout. | -| `0.20.0` | Not qualified | Needs the RC observation window and final-artifact gates above. | +| `0.20.0-rc.2` | Published, superseded candidate | Original signed security release remains available. | +| `0.20.0-rc.3` | Published upgrade baseline | Signed candidate, with seven deployed daily records dated 5–11 November 2026. Transient channel/provider errors were reviewed; no unresolved security or data-loss regression was identified. | +| `0.20.0` | Stable source | Release publication requires the final-artifact gates above; matching signed assets and hosted CI establish delivery. No new runtime feature is included. | diff --git a/site/console.html b/site/console.html index 0bdd866..81066b5 100644 --- a/site/console.html +++ b/site/console.html @@ -284,7 +284,7 @@ .lg .k.c-deny{color:var(--deny)} .lg .k.c-allow{color:var(--allow)} -/* ── this release candidate, measured ── */ +/* ── this stable release, measured ── */ .stats{display:grid;grid-template-columns:repeat(auto-fit,minmax(160px,1fr));gap:1px;background:var(--line);border:1px solid var(--line);margin-top:44px} .stat{background:var(--bg);padding:28px 26px} .stat .n{font-family:var(--crt);font-size:clamp(30px,3.4vw,44px);color:var(--hot);line-height:1.05; @@ -365,7 +365,7 @@
-

talos 0.20.0-rc.3 · operator console · MIT

+

talos 0.20.0 · operator console · MIT

recorded · unfurled · no live wire

Witness one deed from door to ledger.

This hall unfurls one true session, recorded on the working machine @@ -553,12 +553,12 @@

Numbers this candidate must ship.

embedded below. Either way the digits come from a count, not from memory.

-
0.20.0-rc.3
release candidate
public installer v0.20.0-rc.3
+
0.20.0
stable release
public installer v0.20.0
3492
automated tests, collected by pytest
277
adversarial cases, all behaving
996
lines in policy.py, readable in one sitting
37
tools, every one through the gate
-
v0.20.0-rc.3
release tag
+
v0.20.0
release tag
@@ -724,7 +724,7 @@

Numbers this candidate must ship.

replayBtn.addEventListener('click', play); })(); -/* ─── this release candidate, measured: ./status.json with an embedded fallback ─── */ +/* ─── this stable release, measured: ./status.json with an embedded fallback ─── */ (() => { const src = document.getElementById('statusSrc'); const FIELDS = ['version', 'installer_version', 'tests', 'redteam_faelle', 'kernel_zeilen', 'werkzeuge', 'release_ref']; diff --git a/site/docs/index.html b/site/docs/index.html index c9070b2..e71a1ef 100644 --- a/site/docs/index.html +++ b/site/docs/index.html @@ -378,10 +378,10 @@

Section 03Give it a mind

-

RC.3Move from Hermes or OpenClaw

+

0.20.0Move from Hermes or OpenClaw

- Included in the signed 0.20.0-rc.3 installer -

Upgrade to RC.3 to use these commands. Preview the fingerprinted plan before + Included in the signed 0.20.0 installer +

Upgrade to 0.20.0 to use these commands. Preview the fingerprinted plan before applying it; staged content grants no permissions.

Preview first. Talos inventories only portable profile text, memory documents @@ -436,7 +436,7 @@

Section 04Run it

Section 05The terminal session

$ talos chat
-Talos 0.20.0-rc.3  ·  anthropic-api/claude-opus-4-8  ·  autonomy 3
+Talos 0.20.0  ·  anthropic-api/claude-opus-4-8  ·  autonomy 3
 speaking as cli:1000  ·  approvals possible  ·  you are at a terminal
 /help for commands, `exit` to leave
 
diff --git a/site/faq/index.html b/site/faq/index.html
index 2683c59..481ed11 100644
--- a/site/faq/index.html
+++ b/site/faq/index.html
@@ -47,8 +47,8 @@ 

Getting started

How do I install Talos on macOS or Linux?

Follow the installation guide: inspect the Bash installer, install the signed release, configure your identity and model, then start terminal chat. Talos requires Python 3.11 or newer. The installer verifies the release and runs its tests; it does not start the agent automatically. A separate Pinokio launcher is also available; check the release it currently pins.

Can Talos run on a Raspberry Pi or a VPS?

Yes. Talos runs on Linux, including Raspberry Pi, as well as macOS. The agent and the model are separate: a Pi can run Talos while a configured provider supplies inference. Running a large model locally needs enough memory and compute for that model. Self-hosting does not imply that every model fits on a Pi. See model setup.

Can I use Talos as a self-hosted Telegram AI agent?

Yes. Configure your own Telegram bot and explicitly allow your identity. Talos fetches messages by long polling; the Telegram channel does not need a public webhook. Follow the Telegram setup instructions. Keep one service polling each bot token to avoid competing consumers.

-
Can I migrate from Hermes or OpenClaw?

Talos RC.3 can preview a redacted, fingerprinted plan for portable profile text, memory documents and Agent Skills, then apply exactly that plan into inactive staging. It does not import passwords, permissions, schedules, plugins, sessions, databases or live connector access. This feature is included in RC.3; see the migration guide.

-
What are Talos Connections?

Talos Connections is the public source interface for the existing isolated-worker registry and secret-free disabled connector drafts. A draft is inert: the operator must separately install the server and opt in through both agent and worker allowlists. It contains no private Atlas service, bundled account, endpoint or credential. Connections is included in the signed RC.3 installer. See the guide and commands.

+
Can I migrate from Hermes or OpenClaw?

Talos 0.20.0 can preview a redacted, fingerprinted plan for portable profile text, memory documents and Agent Skills, then apply exactly that plan into inactive staging. It does not import passwords, permissions, schedules, plugins, sessions, databases or live connector access. This feature is included in 0.20.0; see the migration guide.

+
What are Talos Connections?

Talos Connections is the public source interface for the existing isolated-worker registry and secret-free disabled connector drafts. A draft is inert: the operator must separately install the server and opt in through both agent and worker allowlists. It contains no private Atlas service, bundled account, endpoint or credential. Connections is included in the signed 0.20.0 installer. See the guide and commands.

Your models. Your costs.

@@ -68,7 +68,7 @@

The terms of the grant

Judge the work

How should I compare Talos with IronClaw, OpenClaw or Hermes?

Compare the same task, model, host resources and permission scope. Measure completed outcomes, operator effort, latency and recovery, not just stars or test counts. Talos focuses on a readable deterministic capability kernel and scoped approvals; other projects may suit different integrations or workflows. We do not claim a universal winner. Read the documented comparison and check each project's current source for its own capabilities.

-
Is Talos production-ready?

Talos is a release candidate, not yet stable. Automated tests and signed releases are evidence for specific checks, not a guarantee of error-free operation. Review the frozen operator contract, validate your own workflows and keep a rollback path. Experimental Computer adapters have separate qualification requirements; a source implementation is not a ready-to-use VM.

+
Is Talos production-ready?

Talos 0.20.0 is stable under its documented operator contract. Automated tests and signed releases are evidence for specific checks, not a guarantee of error-free operation. Review the frozen operator contract, validate your own workflows and keep a rollback path. Experimental Computer adapters have separate qualification requirements; a source implementation is not a ready-to-use VM.

How can I star, fork or contribute to Talos?

Visit Talos on GitHub and star it if you want to keep track of the project. Fork the repository to experiment, follow the contribution guide, or open a reproducible issue. Helpful contributions include installation reports, clearer documentation and regression tests. Share only sanitised examples, never tokens, private logs or personal configuration.

These answers describe Talos, not a hosted service. Check the release notes for the version you install. A GitHub star is a bookmark and a signal of interest, not a security certificate.

diff --git a/site/index.html b/site/index.html index 541f2d9..d299320 100644 --- a/site/index.html +++ b/site/index.html @@ -536,9 +536,9 @@

Give it work worthy of a sworn hand.

-

new in RC.3

+

new in 0.20.0

Move the work. Leave authority behind.

-

The 0.20.0-rc.3 installer can prepare a bounded move from Hermes or OpenClaw and can record +

The 0.20.0 installer can prepare a bounded move from Hermes or OpenClaw and can record disabled connector drafts. It never inherits an old agent's passwords, grants, schedules or live connections.

@@ -557,7 +557,7 @@

Move the work. Leave authority behind.

current recordings in the GitHub README. Their provenance states which parts are real and which transport is simulated.

-

Included in RC.3. Review the migration fingerprint before applying; imported +

Included in 0.20.0. Review the migration fingerprint before applying; imported content stays inactive until you explicitly activate a validated skill.

@@ -686,7 +686,7 @@

The bounds are named.

Measured, with the path stated

None of this asks for belief. The installer runs the unit and adversarial suites in front of you; the real-model cases are a separate opt-in E2E run.

-

Release-candidate source and signed release. Counts describe the source test suite, not speed or real-world success rates; signed release contents follow their tag.

+

Stable source and signed release. Counts describe the source test suite, not speed or real-world success rates; signed release contents follow their tag.

0
automated tests collected from the source tree
0
adversarial cases trying to pass the kernel
0
opt-in end-to-end cases against a real model
@@ -812,7 +812,7 @@

Talos AI agent: your questions

raise the keep

The command remains yours

-

Release candidate 0.20.0-rc.3. Tested on Python 3.11 · 3.13, Linux and macOS, including Raspberry Pi. +

Stable 0.20.0. Tested on Python 3.11 · 3.13, Linux and macOS, including Raspberry Pi. Bring your own model: a supported CLI, configured API provider or local Ollama. The installer runs the unit and adversarial suites in front of you, then starts nothing.

diff --git a/site/install.sh b/site/install.sh index d6fecfb..327e86f 100755 --- a/site/install.sh +++ b/site/install.sh @@ -15,7 +15,7 @@ set -euo pipefail -VERSION="0.20.0-rc.3" +VERSION="0.20.0" BASE="${TALOS_BASE:-https://talos-agent.ch}" TARBALL="${BASE}/dist/talos-${VERSION}.tar.gz" PREFIX="${TALOS_PREFIX:-$HOME/talos}" diff --git a/site/llms.txt b/site/llms.txt index a05af23..bc53143 100644 --- a/site/llms.txt +++ b/site/llms.txt @@ -10,9 +10,9 @@ - MCP servers run only inside a UID-separated worker, from an operator-owned registry — no marketplace, no third-party code in the agent process - Channels: Telegram, mail (IMAP pull), CLI, WhatsApp via an operator-controlled broker — every channel fetches; no inbound port, no webhook - Updates: signed tarballs, verified before anything is unpacked; dependencies pinned and hashed, installed with --require-hashes -- Latest signed release: 0.20.0-rc.3. Includes safe migration, Talos Connections and labelled scheduled-result notifications. -- Migration in RC.3: fingerprinted redacted preview, inactive staging apply, recovery archive and one-at-a-time validated skill activation; no inherited secrets or authority -- Talos Connections in RC.3: isolated-worker inventory plus disabled secret-free drafts; no bundled account, endpoint or private service +- Latest signed release: 0.20.0. Includes safe migration, Talos Connections and labelled scheduled-result notifications. +- Migration in 0.20.0: fingerprinted redacted preview, inactive staging apply, recovery archive and one-at-a-time validated skill activation; no inherited secrets or authority +- Talos Connections in 0.20.0: isolated-worker inventory plus disabled secret-free drafts; no bundled account, endpoint or private service - Scheduled runs on current source stay quiet while working and deliver one labelled final result; interactive work trails show bounded skill and executable names without arguments or contents - License: MIT diff --git a/site/redteam/index.html b/site/redteam/index.html index 56f9906..44e3913 100644 --- a/site/redteam/index.html +++ b/site/redteam/index.html @@ -394,7 +394,7 @@

Section 06Attack it yourself

Roll of Arms Weigh the Orders Source - MIT · REV 0.20.0-RC.3 + MIT · REV 0.20.0
diff --git a/site/status.json b/site/status.json index bac3d1f..bc60ae1 100644 --- a/site/status.json +++ b/site/status.json @@ -1,11 +1,11 @@ { - "version": "0.20.0-rc.3", + "version": "0.20.0", "release_state": "released", "source_state": "release", - "installer_version": "0.20.0-rc.3", + "installer_version": "0.20.0", "tests": 3492, "redteam_faelle": 277, "kernel_zeilen": 996, "werkzeuge": 37, - "release_ref": "v0.20.0-rc.3" + "release_ref": "v0.20.0" } diff --git a/talos/__init__.py b/talos/__init__.py index a1d1003..c577c71 100644 --- a/talos/__init__.py +++ b/talos/__init__.py @@ -8,4 +8,4 @@ advertised and a released package is never left behind. """ -__version__ = "0.20.0-rc.3" +__version__ = "0.20.0"