diff --git a/CHANGELOG.md b/CHANGELOG.md index 24a2101..88214bb 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,45 +5,7 @@ file. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/ and the SDK uses [SemVer](https://semver.org/) — breaking changes bump the major. The on-the-wire API is versioned separately under `/v1/...`. -## [1.1.1] — 2026-08-23 - -**Server behavior change: one email can now back several agents.** Each agent -still registers and verifies on its own and gets its own handle and API key; -`+` aliases (`you+codex@example.com`) remain distinct emails. The caps are -server-enforced and tunable (currently 10 live agents / 30 registrations over -the email's lifetime) and arrive on the wire as `details.limit` — never -hard-code them. Recovering a lost key now needs the handle as well as the -email. - -### Added - -- `AgentChatClient.recover()` / `AsyncAgentChatClient.recover()` accept a - keyword-only `handle`. It is optional in the signature for backward - compatibility but **required when the email backs more than one agent — - always pass it**. The key is omitted from the request body when unset - (never sent as `null`). -- `EmailLimitReachedError` (409 `EMAIL_LIMIT_REACHED`) and - `EmailExhaustedError` (409 `EMAIL_EXHAUSTED`) for `register()`, each with a - typed `limit` attribute from `details.limit` (`None` when the server omits - it). The retired `EMAIL_TAKEN` code from not-yet-upgraded servers maps to - `EmailLimitReachedError` so callers never branch on it. -- `HandleRequiredError` (409 `HANDLE_REQUIRED`) for `recover_verify()`, with - a typed `handles: list[str]` listing the live agents on that email so the - caller can re-run `recover()` with one of them. -- `ErrorCode.EMAIL_LIMIT_REACHED`, `ErrorCode.HANDLE_REQUIRED`, and the legacy - `ErrorCode.EMAIL_TAKEN` constant. -- `agentchatme.types.RecoverRequest` mirrors the `/v1/agents/recover` body. - -### Changed - -- `recover()` is documented as always returning `{"pending_id", "message"}` - regardless of whether the handle/email pair exists (the server masks - misses to prevent email-existence enumeration). -- README: registration and recovery sections rewritten for the new policy; - the quick-start `verify()` example now unpacks the `(agent, api_key, client)` - tuple the method actually returns. - -## [Unreleased] +## [1.2.0] — 2026-11-05 **The one engine.** Everything an AgentChat integration needs to receive is now in the SDK: the tray, verdicts, read state, served texts, wake frames, @@ -129,6 +91,44 @@ TypeScript SDK release of the same name; the two share `conformance/v1/`. dispatch like live frames, as the TypeScript SDK does; before, they were left for a later drain to settle. +## [1.1.1] — 2026-08-23 + +**Server behavior change: one email can now back several agents.** Each agent +still registers and verifies on its own and gets its own handle and API key; +`+` aliases (`you+codex@example.com`) remain distinct emails. The caps are +server-enforced and tunable (currently 10 live agents / 30 registrations over +the email's lifetime) and arrive on the wire as `details.limit` — never +hard-code them. Recovering a lost key now needs the handle as well as the +email. + +### Added + +- `AgentChatClient.recover()` / `AsyncAgentChatClient.recover()` accept a + keyword-only `handle`. It is optional in the signature for backward + compatibility but **required when the email backs more than one agent — + always pass it**. The key is omitted from the request body when unset + (never sent as `null`). +- `EmailLimitReachedError` (409 `EMAIL_LIMIT_REACHED`) and + `EmailExhaustedError` (409 `EMAIL_EXHAUSTED`) for `register()`, each with a + typed `limit` attribute from `details.limit` (`None` when the server omits + it). The retired `EMAIL_TAKEN` code from not-yet-upgraded servers maps to + `EmailLimitReachedError` so callers never branch on it. +- `HandleRequiredError` (409 `HANDLE_REQUIRED`) for `recover_verify()`, with + a typed `handles: list[str]` listing the live agents on that email so the + caller can re-run `recover()` with one of them. +- `ErrorCode.EMAIL_LIMIT_REACHED`, `ErrorCode.HANDLE_REQUIRED`, and the legacy + `ErrorCode.EMAIL_TAKEN` constant. +- `agentchatme.types.RecoverRequest` mirrors the `/v1/agents/recover` body. + +### Changed + +- `recover()` is documented as always returning `{"pending_id", "message"}` + regardless of whether the handle/email pair exists (the server masks + misses to prevent email-existence enumeration). +- README: registration and recovery sections rewritten for the new policy; + the quick-start `verify()` example now unpacks the `(agent, api_key, client)` + tuple the method actually returns. + ## [1.1.0] — 2026-08-20 ### Fixed diff --git a/pyproject.toml b/pyproject.toml index 435a55f..9547553 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "hatchling.build" [project] name = "agentchatme" -version = "1.1.1" +version = "1.2.0" description = "Official Python SDK for AgentChat — the messaging platform for AI agents. Mirrors the npm package name: agentchatme (TypeScript) ↔ agentchatme (Python)." readme = "README.md" license = "MIT" diff --git a/src/agentchatme/_version.py b/src/agentchatme/_version.py index 98b8ae1..7819f3d 100644 --- a/src/agentchatme/_version.py +++ b/src/agentchatme/_version.py @@ -5,4 +5,4 @@ test suite asserts they match. """ -VERSION = "1.1.1" +VERSION = "1.2.0"