zas-agent 0.8.0 → 0.10.0

package/CHANGELOG.md

@@ -7,6 +7,62 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.10.0] - 2026-09-28
+
+### Added
+
+- Transfer telemetry. File and note sends, item downloads, and Directo sends
+  and receives (live and reliable delivery) report `transfer.started`,
+  `transfer.stage_started`, `transfer.slow` (after 30 s),
+  `transfer.phase_timing` and `transfer.finished`. Each report carries the
+  item category, the transport, byte counts, a size bucket, stage durations and
+  the outcome (success, failure or cancellation), joined by a random
+  per-attempt ID. No file name, content, path or channel name. The same
+  opt-out as `agent.tool_call` covers it. The telemetry notice names the new
+  fields.
+
+- `plan_inactive`. A send, replace or Directo transfer in an organization
+  channel whose plan is inactive now says so, and names who can reactivate
+  it. It used to arrive as `upload_failed`, which told the agent to retry.
+
+### Changed
+
+- Reports never delay or fail a tool call. The `agent.tool_call` report is
+  sent after the answer, on a later tick. Transfer events are queued, at most
+  32 per batch, and sent in one request on a later tick. A report is one
+  request with a 2 s timeout and no retry. It is skipped when there is no
+  valid session, so it never starts or refreshes a sign-in.
+
+## [0.9.0] - 2026-09-09
+
+### Added
+
+- `zas_edit_item`. An agent changes an item it sent, under the same id: the
+  title of a file or a note, or a note's text, language and secret cover.
+  The owner's activity log records the edit, and the channel's devices are
+  woken. An item somebody else sent is refused as `not_yours`.
+- `zas_replace_file`. An agent swaps the bytes under a file it sent, keeping
+  the item id, its place in the channel and its pin. The old chunks are
+  released and the new ones charged in one server transaction; a chunk in
+  both versions is left alone. A note, an item with a public share, and an
+  item somebody else sent are refused. Agents only: no web or mobile client
+  gets a replace.
+- Five codes: `not_yours`, `stale` (the item changed while the agent was
+  working on it: read it again and retry), `not_a_note`, `not_a_file`,
+  `item_shared`.
+- Both tools drop the local send receipts for the item they changed, so
+  "send that again" after an edit makes a new item.
+
+### Fixed
+
+- A machine whose agent home could not be written crashed on the way into
+  serving, before the MCP initialize response, because recording that the
+  telemetry notice had been shown threw. The notice is printed and the
+  failure to record it is logged; the server starts either way. This is the
+  crash behind "connection closed: initialize response" from a Codex-style
+  host.
+
+
 ## [0.8.0] - 2026-09-06
 
 ### Added
@@ -303,7 +359,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   two separate identities that cannot read each other's keys.
 - Install snippets for Claude Code and Codex, printed by `zas-agent pair`.
 
-[Unreleased]: https://github.com/soke1556/zas-agent/compare/v0.8.0...HEAD
+[Unreleased]: https://github.com/soke1556/zas-agent/compare/v0.10.0...HEAD
+[0.10.0]: https://github.com/soke1556/zas-agent/compare/v0.9.0...v0.10.0
+[0.9.0]: https://github.com/soke1556/zas-agent/compare/v0.8.0...v0.9.0
 [0.8.0]: https://github.com/soke1556/zas-agent/compare/v0.7.0...v0.8.0
 [0.7.0]: https://github.com/soke1556/zas-agent/compare/v0.6.3...v0.7.0
 [0.6.3]: https://github.com/soke1556/zas-agent/compare/v0.6.2...v0.6.3

package/README.md

@@ -25,9 +25,10 @@ scope to the channels you choose, and that you can revoke.
 
 ## What it does
 
-Your coding agent gets eleven tools. It can send a file or a note into a channel
+Your coding agent gets thirteen tools. It can send a file or a note into a channel
 you picked, send or receive a file live through Directo, list what is in that
-channel, and pull one item back onto disk.
+channel, pull one item back onto disk, and change what it sent: an item's
+title or text, or the bytes under a file, keeping the item id.
 Everything it sends is encrypted on your machine before it leaves, lands in your
 account, and is marked in the channel as sent by that agent. The agent has an
 identity of its own and never holds your account key: pairing mints a key pair
@@ -158,14 +159,24 @@ The package refuses some of these on its own, before a request is made. The
 ones marked *(server-side)* are enforced by the Zas server.
 
 - **No channel you did not grant.** Not by name, not by id.
-- **No shared channel you merely joined, and no workspace channel.** Grants
-  exist only on channels your account owns and that no organization manages
+- **No shared channel you joined, unless its owner allows it.** You can grant
+  a channel you joined, but the grant stays `grant_pending` until that
+  channel's owner allows this agent in Zas. The plan also caps how many of
+  these channels one agent holds: 2 on Free *(server-side)*.
+- **No workspace channel, unless the organization allows agents.** A channel
+  an organization manages, or one you created inside its workspace, can be
+  granted only while the organization is active and an admin turned agents on
   *(server-side)*.
 - **No reading unless the grant says so.** `read` is a separate switch from
   `send`; without it, `zas_list_items` and `zas_get_item` are refused.
 - **No stored sending into a view-only channel, and none into a channel in
   Directo mode.** Both are refused before a byte is uploaded. A channel in
   Directo mode takes `zas_send_direct`, a live transfer that stores nothing.
+- **No changing what it did not send.** `zas_edit_item` and `zas_replace_file`
+  act only on items carrying this agent's mark; anything else is `not_yours`,
+  and the server refuses it too *(server-side)*. A replace is for agents only:
+  no web or mobile client gets one. An item with a public share is not
+  replaced until the share is removed.
 - **No receiving unless the grant says read.** Receiving through Directo
   writes a file onto this machine, so `zas_receive_direct` takes the same
   `read` switch as listing. And it only ever runs inside a tool call: the
@@ -194,6 +205,7 @@ string ever reaches a terminal.
 | `agent_revoked` | The owner revoked this agent. |
 | `agent_forbidden` | Only the account owner can do that. |
 | `grant_missing` | This agent has no access to that channel. |
+| `grant_pending` | That channel belongs to somebody else, and its owner has not allowed this agent yet. |
 | `send_forbidden` | This agent cannot send to that channel. |
 | `read_forbidden` | This agent cannot read that channel. |
 | `direct_mode` | That channel is in Directo mode. |
@@ -209,14 +221,26 @@ string ever reaches a terminal.
 | `fallback_unavailable` | Reliable delivery is not available right now. |
 | `key_stale` | The channel key changed; the owner refreshes it by opening Zas. |
 | `quota_exceeded` | The account reached its storage limit. |
+| `plan_inactive` | The organization's plan is inactive, so sending to its channels is paused; the owner or a billing admin reactivates it. |
 | `rate_limited` | Too many sends in a row. |
 | `file_too_big` | The file is over the plan limit. |
 | `duplicate` | That item is already in the channel. |
 | `not_found` | That item is not in the channel. |
+| `not_yours` | That item was not sent by this agent; it can only change its own items. |
+| `stale` | That item changed while this agent was working on it; read it again and retry. |
+| `not_a_note` | That item is a file, not a note; only its title can change. |
+| `not_a_file` | That item is a note, not a file. |
+| `item_shared` | That item has a public share; the owner removes the share first. |
 | `invalid_cap` | That file is no longer available. |
 | `write_failed` | The download destination could not be written. |
 | `pairing_expired` | The pairing expired; pair again. |
 | `pairing_cancelled` | The owner cancelled the pairing. |
+| `claim_mismatch` | The code does not match. |
+| `pairing_not_approved` | Nobody has approved this pairing yet. |
+| `pairing_claimed` | This pairing was already claimed; pair again. |
+| `agent_limit` | The account cannot take another agent; the owner deletes one from Settings → Agents. |
+| `grant_limit` | The plan allows fewer channels per agent than this pairing grants. |
+| `foreign_limit` | The plan allows this agent fewer channels of other people than this pairing asks for. |
 | `feature_disabled` | Agents are not enabled for this account yet. |
 | `upload_failed` | The upload failed. |
 | `oprf_failed` | Zas did not answer correctly while preparing the file. |
@@ -243,11 +267,22 @@ stack trace.
 | `zas_receive_direct_fallback` | After a Directo receive failed in flight, downloads the encrypted copy the sender chose to store, and decrypts it to the same destination. |
 | `zas_list_items` | Lists the most recent items in one of the owner's channels. Needs a grant that includes reading. |
 | `zas_get_item` | Fetches one item. A note comes back as text; a file is written to disk. It never overwrites, so the path it answers with can differ from the one you asked for. |
+| `zas_edit_item` | Changes an item this agent sent, keeping its id: the title of a file or a note, or a note's text, language and secret cover. Needs a grant that includes reading and sending. The owner's activity log records it. |
+| `zas_replace_file` | Replaces the bytes of a file this agent sent with a file from this machine, keeping the item id, its place in the channel and its pin. Returns the item id, or a job id after a minute. Refuses notes, shared items, and items sent by anyone else. |
 | `zas_jobs` | Lists the sends and Directo transfers this server started, newest first, with the phase each one reached — and where a `job_id` from a long send is redeemed. |
 
 `channel` takes a channel name or a channel id. A name has to match exactly one
 of the channels you granted; with exactly one grant, `zas_send_file`,
-`zas_send_note`, `zas_send_direct` and `zas_receive_direct` can leave it out.
+`zas_send_note`, `zas_send_direct`, `zas_receive_direct`, `zas_edit_item` and
+`zas_replace_file` can leave it out.
+
+A replace runs the same pipeline as a send — hash, key derivation, encryption,
+then upload or proof per chunk — and posts the new set with the old one to
+release. The server moves both sets, the account's storage tally and the item
+in one transaction, so a failure leaves everything as it was; a chunk present
+in both versions is neither uploaded nor released. Both tools read the item
+first and write only over the version they read: an item that changed in
+between answers `stale`, and nothing is lost.
 
 Directo needs a native module, [node-datachannel](https://github.com/murat-dogan/node-datachannel),
 WebRTC for Node. npm installs a prebuilt binary for Windows, macOS and Linux;
@@ -284,14 +319,16 @@ covers every profile on the machine; pairing again does not reset it.
 
 What one report carries, and nothing else: the tool that ran, whether it
 worked, the closed error code when it did not, which of four duration buckets
-it fell in, and the package version. No file name, no file contents, no path,
+it fell in, and the package version. Item transfers also report item category,
+transport, byte counts, stage durations, and success/failure/cancellation, joined
+by a random per-attempt ID. No file name, no file contents, no path,
 no channel name, no error message, no stack.
 
 Where it goes: to Zas, never to an analytics service directly. This package
 holds no analytics token and opens no connection to a third party, so no
 address of yours reaches one. The report is attributed to the Zas account the
 agent is paired with, which the server reads from the session — the request
-carries no identifier of its own. Nothing is reported before pairing, because
+carries no account or content identifier. Nothing is reported before pairing, because
 until then there is no account it could belong to.
 
 A report is never allowed to matter: it is sent after the answer, waited on