tabc 0.2.3__tar.gz → 0.2.4__tar.gz

{tabc-0.2.3 → tabc-0.2.4}/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## 0.2.4 — 2026-10-25
+
+### Added
+
+- `tabc send --id <UUID>` sends with a caller-chosen message id, so a retry
+  after a lost response is not stored twice. A resend goes through the
+  usual send checks first, so unread mail can refuse it with
+  `UNREAD_BLOCKED`. After those checks, the same id with the same
+  envelope prints `stored id=<id>` and, below it,
+  `identical envelope resent — not stored twice`, and exits 0. With a
+  changed envelope it fails with `failed: conflict: …` and exits 1. The id
+  is checked before any request and written in canonical form. A value
+  that is not a UUID fails with
+  `failed: --id must be a full message UUID` and exits 1.
+
+### Unchanged
+
+- Without `--id`, `send` uses a new random id as before. The daemon is
+  unchanged. The MCP `tabc_send` tool already took a caller-chosen id as
+  `message_id`; the CLI now offers the same.
+
 ## 0.2.3 — 2026-10-17
 
 ### Added

{tabc-0.2.3/tabc.egg-info → tabc-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: tabc
-Version: 0.2.3
+Version: 0.2.4
 Summary: A shared inbox for AI agents and programs on one machine
 License: MIT License
         
@@ -27,6 +27,7 @@ License: MIT License
 Project-URL: Homepage, https://tabc.sh
 Project-URL: Source, https://github.com/jultabc/tabc
 Project-URL: Documentation, https://github.com/jultabc/tabc/blob/main/GUIDE.md
+Project-URL: Changelog, https://github.com/jultabc/tabc/blob/main/CHANGELOG.md
 Project-URL: Issues, https://github.com/jultabc/tabc/issues
 Keywords: agents,messaging,ipc,cli
 Classifier: Development Status :: 3 - Alpha
@@ -51,6 +52,16 @@ This is an experimental package. It is not a security boundary between agents
 using the same operating-system account. Message delivery does not imply that
 an agent read, understood, or completed a request.
 
+## Updates
+
+See the [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md)
+for changes and compatibility notes, or
+[GitHub releases](https://github.com/jultabc/tabc/releases) for published versions.
+
+Before updating an existing installation, follow the
+[installation and upgrade instructions](https://github.com/jultabc/tabc#readme).
+Keep a backup and follow the stop, install, and restart sequence for your version.
+
 ## Install
 
 ```bash
@@ -105,83 +116,6 @@ from the `pull --mode full` detail block, or a unique prefix of it.
 Terminal notification is a separate process and does not start with the
 install; see the repository's guide before turning it on.
 
-## Updating from 0.2.2
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, routes, and Codex queue receipts are kept, and nodes do not register
-again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
-`tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.3"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.3"
-```
-
-The CLI now accepts the exact name of an open tac and lists candidates instead
-of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
-is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
-unchanged. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.2.1
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, routes, and Codex queue receipts are kept. Stop `tabus.doorbell`, install,
-restart `tabd`, then start one `tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.2"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.2"
-```
-
-`--kind` is now case-insensitive; `--kind Codex` selects the same Codex queue
-route as `--kind codex`. A detached command no longer needs a recognized agent
-product: its immediate session-boundary parent qualifies when it owns the
-terminal foreground and reads standard input from it. The check proves terminal
-ownership, not that the program is an agent. Register again from the intended
-terminal and confirm one notification arrives. Codex queue rules are otherwise
-unchanged. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.2.0
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, and routes are kept. Stop `tabus.doorbell`, install, restart `tabd`, then
-start one `tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.1"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.1"
-```
-
-`register` now requires `--kind`. Update scripts that omit it. Codex agents
-register again from each conversation after the notifier is replaced. The
-notifier creates `codex_queue_receipts.db` in the tabc home directory on its
-first Codex queue submission. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.1.6
-
-The upgrade preserves nodes, messages, delivery states, TAC membership, names,
-and labels. Stop `tabus.doorbell` and `tabd`. Confirm that the ledger's `-wal`
-file is absent or empty (0 bytes), then keep a backup before installing. A
-remaining empty WAL or SHM file is safe. Do not continue while the WAL is
-non-empty:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.0"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.0"
-```
-
-Existing string TAC IDs are not converted during installation. Follow the
-repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
-to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
-Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
-
 ## Commands
 
 - `tabc register --node alice --kind codex`: register an agent.

{tabc-0.2.3 → tabc-0.2.4}/PYPI.md

@@ -9,6 +9,16 @@ This is an experimental package. It is not a security boundary between agents
 using the same operating-system account. Message delivery does not imply that
 an agent read, understood, or completed a request.
 
+## Updates
+
+See the [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md)
+for changes and compatibility notes, or
+[GitHub releases](https://github.com/jultabc/tabc/releases) for published versions.
+
+Before updating an existing installation, follow the
+[installation and upgrade instructions](https://github.com/jultabc/tabc#readme).
+Keep a backup and follow the stop, install, and restart sequence for your version.
+
 ## Install
 
 ```bash
@@ -63,83 +73,6 @@ from the `pull --mode full` detail block, or a unique prefix of it.
 Terminal notification is a separate process and does not start with the
 install; see the repository's guide before turning it on.
 
-## Updating from 0.2.2
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, routes, and Codex queue receipts are kept, and nodes do not register
-again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
-`tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.3"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.3"
-```
-
-The CLI now accepts the exact name of an open tac and lists candidates instead
-of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
-is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
-unchanged. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.2.1
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, routes, and Codex queue receipts are kept. Stop `tabus.doorbell`, install,
-restart `tabd`, then start one `tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.2"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.2"
-```
-
-`--kind` is now case-insensitive; `--kind Codex` selects the same Codex queue
-route as `--kind codex`. A detached command no longer needs a recognized agent
-product: its immediate session-boundary parent qualifies when it owns the
-terminal foreground and reads standard input from it. The check proves terminal
-ownership, not that the program is an agent. Register again from the intended
-terminal and confirm one notification arrives. Codex queue rules are otherwise
-unchanged. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.2.0
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, and routes are kept. Stop `tabus.doorbell`, install, restart `tabd`, then
-start one `tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.1"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.1"
-```
-
-`register` now requires `--kind`. Update scripts that omit it. Codex agents
-register again from each conversation after the notifier is replaced. The
-notifier creates `codex_queue_receipts.db` in the tabc home directory on its
-first Codex queue submission. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.1.6
-
-The upgrade preserves nodes, messages, delivery states, TAC membership, names,
-and labels. Stop `tabus.doorbell` and `tabd`. Confirm that the ledger's `-wal`
-file is absent or empty (0 bytes), then keep a backup before installing. A
-remaining empty WAL or SHM file is safe. Do not continue while the WAL is
-non-empty:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.0"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.0"
-```
-
-Existing string TAC IDs are not converted during installation. Follow the
-repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
-to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
-Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
-
 ## Commands
 
 - `tabc register --node alice --kind codex`: register an agent.

{tabc-0.2.3 → tabc-0.2.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "tabc"
-version = "0.2.3"
+version = "0.2.4"
 description = "A shared inbox for AI agents and programs on one machine"
 readme = "PYPI.md"
 requires-python = ">=3.9"
@@ -40,6 +40,7 @@ mcp = ["mcp>=1.27.1,<2; python_version >= '3.10'"]
 Homepage = "https://tabc.sh"
 Source = "https://github.com/jultabc/tabc"
 Documentation = "https://github.com/jultabc/tabc/blob/main/GUIDE.md"
+Changelog = "https://github.com/jultabc/tabc/blob/main/CHANGELOG.md"
 Issues = "https://github.com/jultabc/tabc/issues"
 
 [project.scripts]

{tabc-0.2.3 → tabc-0.2.4/tabc.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: tabc
-Version: 0.2.3
+Version: 0.2.4
 Summary: A shared inbox for AI agents and programs on one machine
 License: MIT License
         
@@ -27,6 +27,7 @@ License: MIT License
 Project-URL: Homepage, https://tabc.sh
 Project-URL: Source, https://github.com/jultabc/tabc
 Project-URL: Documentation, https://github.com/jultabc/tabc/blob/main/GUIDE.md
+Project-URL: Changelog, https://github.com/jultabc/tabc/blob/main/CHANGELOG.md
 Project-URL: Issues, https://github.com/jultabc/tabc/issues
 Keywords: agents,messaging,ipc,cli
 Classifier: Development Status :: 3 - Alpha
@@ -51,6 +52,16 @@ This is an experimental package. It is not a security boundary between agents
 using the same operating-system account. Message delivery does not imply that
 an agent read, understood, or completed a request.
 
+## Updates
+
+See the [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md)
+for changes and compatibility notes, or
+[GitHub releases](https://github.com/jultabc/tabc/releases) for published versions.
+
+Before updating an existing installation, follow the
+[installation and upgrade instructions](https://github.com/jultabc/tabc#readme).
+Keep a backup and follow the stop, install, and restart sequence for your version.
+
 ## Install
 
 ```bash
@@ -105,83 +116,6 @@ from the `pull --mode full` detail block, or a unique prefix of it.
 Terminal notification is a separate process and does not start with the
 install; see the repository's guide before turning it on.
 
-## Updating from 0.2.2
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, routes, and Codex queue receipts are kept, and nodes do not register
-again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
-`tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.3"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.3"
-```
-
-The CLI now accepts the exact name of an open tac and lists candidates instead
-of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
-is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
-unchanged. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.2.1
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, routes, and Codex queue receipts are kept. Stop `tabus.doorbell`, install,
-restart `tabd`, then start one `tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.2"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.2"
-```
-
-`--kind` is now case-insensitive; `--kind Codex` selects the same Codex queue
-route as `--kind codex`. A detached command no longer needs a recognized agent
-product: its immediate session-boundary parent qualifies when it owns the
-terminal foreground and reads standard input from it. The check proves terminal
-ownership, not that the program is an agent. Register again from the intended
-terminal and confirm one notification arrives. Codex queue rules are otherwise
-unchanged. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.2.0
-
-The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
-TACs, and routes are kept. Stop `tabus.doorbell`, install, restart `tabd`, then
-start one `tabus.doorbell` from the same installation:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.1"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.1"
-```
-
-`register` now requires `--kind`. Update scripts that omit it. Codex agents
-register again from each conversation after the notifier is replaced. The
-notifier creates `codex_queue_receipts.db` in the tabc home directory on its
-first Codex queue submission. See the
-[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
-
-## Updating from 0.1.6
-
-The upgrade preserves nodes, messages, delivery states, TAC membership, names,
-and labels. Stop `tabus.doorbell` and `tabd`. Confirm that the ledger's `-wal`
-file is absent or empty (0 bytes), then keep a backup before installing. A
-remaining empty WAL or SHM file is safe. Do not continue while the WAL is
-non-empty:
-
-```bash
-python -m pip install --upgrade "tabc==0.2.0"
-# Or, when the local desktop MCP adapter is required:
-python -m pip install --upgrade "tabc[mcp]==0.2.0"
-```
-
-Existing string TAC IDs are not converted during installation. Follow the
-repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
-to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
-Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
-
 ## Commands
 
 - `tabc register --node alice --kind codex`: register an agent.

{tabc-0.2.3 → tabc-0.2.4}/tabus/bus.py

@@ -74,7 +74,7 @@ DB_PATH = os.environ.get(
 #    drifted once already — 0.1.0.post1 shipped while this said 0.1.0. Bump
 #    both together; tests/test_version_agreement.py fails the build otherwise.
 #    Do not copy the number into documentation.
-__version__ = "0.2.3"
+__version__ = "0.2.4"
 PROTOCOL_VERSION = "tabus.v1"
 
 # TTLs. Past these, a derived status counts as old.

{tabc-0.2.3 → tabc-0.2.4}/tabus/cli.py

@@ -437,6 +437,21 @@ def _refusal_line(r):
 
 
 def fn_send(a):
+    # 🔴 --id lets a caller retry without storing twice. The daemon treats the same id
+    #    with the same envelope as a resend and the same id with a changed envelope as
+    #    a conflict, so the caller keeps the id and the whole envelope from before the
+    #    first attempt. The daemon does not compare the sending mode itself (tac or
+    #    broadcast), only the resolved recipients, so the caller keeps that fixed too.
+    #    Full UUIDs only, written in canonical form, so that one id typed two ways
+    #    cannot become two messages. Checked first, before the tac lookup or any
+    #    other request.
+    mid = str(uuid.uuid4())
+    if getattr(a, "id", None) is not None:
+        try:
+            mid = str(uuid.UUID(a.id))
+        except ValueError:
+            print("failed: --id must be a full message UUID")
+            sys.exit(1)
     body = a.body
     if a.body_file:
         body = open(a.body_file, encoding="utf-8").read()
@@ -454,7 +469,6 @@ def fn_send(a):
     #    send is authenticated by the request signature (call() signs every request),
     #    and the daemon requires `from` to equal the acting node, so no message-level
     #    signature is sent — a forged sender cannot get past the request auth.
-    mid = str(uuid.uuid4())
     payload = {
         "from": a.sender,
         "to": requested,
@@ -1216,6 +1230,13 @@ COMMANDS = {
             (("--body",), dict()),
             (("--body-file",), dict()),
             (("--priority",), dict(default="next", choices=["now", "next", "batch"])),
+            (
+                ("--id",),
+                dict(
+                    default=None,
+                    help="message UUID for a retry-safe send. The same id with the same envelope is not stored twice; with a changed envelope it is refused as a conflict",
+                ),
+            ),
         ],
     ),
     "who": (fn_who, "who is present, and how much is pending", [(("--node",), dict(default=None, help="acting node; falls back to TABC_NODE"))]),