tabc 0.2.3__tar.gz → 0.2.5__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (42) hide show
  1. {tabc-0.2.3 → tabc-0.2.5}/CHANGELOG.md +108 -0
  2. {tabc-0.2.3 → tabc-0.2.5}/GUIDE.md +36 -1
  3. {tabc-0.2.3 → tabc-0.2.5}/MCP.md +62 -0
  4. {tabc-0.2.3/tabc.egg-info → tabc-0.2.5}/PKG-INFO +24 -82
  5. {tabc-0.2.3 → tabc-0.2.5}/PYPI.md +17 -79
  6. {tabc-0.2.3 → tabc-0.2.5}/pyproject.toml +2 -1
  7. {tabc-0.2.3 → tabc-0.2.5/tabc.egg-info}/PKG-INFO +24 -82
  8. {tabc-0.2.3 → tabc-0.2.5}/tabc.egg-info/SOURCES.txt +1 -0
  9. {tabc-0.2.3 → tabc-0.2.5}/tabus/bus.py +186 -31
  10. {tabc-0.2.3 → tabc-0.2.5}/tabus/cli.py +342 -3
  11. {tabc-0.2.3 → tabc-0.2.5}/tabus/daemon.py +153 -3
  12. {tabc-0.2.3 → tabc-0.2.5}/tabus/doorbell.py +58 -1
  13. {tabc-0.2.3 → tabc-0.2.5}/tabus/mcp_server.py +72 -10
  14. tabc-0.2.5/tabus/reply_link.py +287 -0
  15. {tabc-0.2.3 → tabc-0.2.5}/tabus/send_refusal.py +22 -4
  16. {tabc-0.2.3 → tabc-0.2.5}/LICENSE +0 -0
  17. {tabc-0.2.3 → tabc-0.2.5}/MANIFEST.in +0 -0
  18. {tabc-0.2.3 → tabc-0.2.5}/setup.cfg +0 -0
  19. {tabc-0.2.3 → tabc-0.2.5}/tabc.egg-info/dependency_links.txt +0 -0
  20. {tabc-0.2.3 → tabc-0.2.5}/tabc.egg-info/entry_points.txt +0 -0
  21. {tabc-0.2.3 → tabc-0.2.5}/tabc.egg-info/requires.txt +0 -0
  22. {tabc-0.2.3 → tabc-0.2.5}/tabc.egg-info/top_level.txt +0 -0
  23. {tabc-0.2.3 → tabc-0.2.5}/tabus/__init__.py +0 -0
  24. {tabc-0.2.3 → tabc-0.2.5}/tabus/admin.py +0 -0
  25. {tabc-0.2.3 → tabc-0.2.5}/tabus/codex_queue.py +0 -0
  26. {tabc-0.2.3 → tabc-0.2.5}/tabus/compat_bcn.py +0 -0
  27. {tabc-0.2.3 → tabc-0.2.5}/tabus/compat_busd.py +0 -0
  28. {tabc-0.2.3 → tabc-0.2.5}/tabus/doorbell_poll.py +0 -0
  29. {tabc-0.2.3 → tabc-0.2.5}/tabus/lang.py +0 -0
  30. {tabc-0.2.3 → tabc-0.2.5}/tabus/locales/en.json +0 -0
  31. {tabc-0.2.3 → tabc-0.2.5}/tabus/nodekey.py +0 -0
  32. {tabc-0.2.3 → tabc-0.2.5}/tabus/paths.py +0 -0
  33. {tabc-0.2.3 → tabc-0.2.5}/tabus/process_argv.py +0 -0
  34. {tabc-0.2.3 → tabc-0.2.5}/tabus/route_capture.py +0 -0
  35. {tabc-0.2.3 → tabc-0.2.5}/tabus/sent.py +0 -0
  36. {tabc-0.2.3 → tabc-0.2.5}/tabus/tac_identity.py +0 -0
  37. {tabc-0.2.3 → tabc-0.2.5}/tabus/tac_lookup.py +0 -0
  38. {tabc-0.2.3 → tabc-0.2.5}/tabus/tac_migration.py +0 -0
  39. {tabc-0.2.3 → tabc-0.2.5}/tabus/tac_refusal.py +0 -0
  40. {tabc-0.2.3 → tabc-0.2.5}/tabus/tac_search.py +0 -0
  41. {tabc-0.2.3 → tabc-0.2.5}/tabus/tac_store.py +0 -0
  42. {tabc-0.2.3 → tabc-0.2.5}/tabus/terminal_frontend.py +0 -0
@@ -1,5 +1,113 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.5 — 2026-11-20
4
+
5
+ ### Added
6
+
7
+ - `tabc send --check` sends nothing. It asks the daemon whether this send
8
+ would be refused now, and by which unread messages. It runs the same
9
+ refusals as a send and stops before the first write. Exit 0 not blocked,
10
+ 1 the check failed while running (a retry can work), 2 the daemon cannot
11
+ check (an older daemon, HTTP 400, 401 or 403), 3 the send would be
12
+ refused. A failed check is never reported as not blocked.
13
+ - `tabc status` prints this node's unread mail without changing anything:
14
+ counts of messages not opened and opened but not marked READ, by kind
15
+ (dm, tac, broadcast), the oldest message of each group, and which unread
16
+ mail blocks a send (DMs per sending node, tac messages per tac). It
17
+ writes nothing, not even the mailbox open time. Exit 0 read, 1 the query
18
+ failed, 2 the daemon cannot answer. A failed query is never shown as zero
19
+ unread.
20
+ - Reply links. `tabc send --re <id>` stores a reply to a message the sender
21
+ sent, received, or can read in a tac it belongs to now. `tabc read` and
22
+ `tabc open` print a `re` line with the parent's short id and subject.
23
+ - `tabc thread <id>` prints an outline of one thread: time, sender,
24
+ recipients, subject and id per message, with replies indented. It shows no
25
+ bodies and marks nothing READ. Times are in the local time zone of the
26
+ machine running it, with the zone name.
27
+ - `tabc thread --limit N --after ID` reads a long thread one page at a time
28
+ (`--limit` default 100, largest 500). A page that has more after it ends
29
+ with the command for the next page. A reply whose parent is on another page
30
+ is marked `(re: <id> on another page)`. A reply whose parent the node cannot
31
+ see is marked `(re: not visible)`.
32
+ - MCP: `reply_to` on `tabc_send` and `tabc_tac_send`, and a read-only
33
+ `tabc_thread` tool with the same paging. See [MCP.md](MCP.md#replies).
34
+
35
+ ### Changed
36
+
37
+ - `UNREAD_BLOCKED` details now also list the blocking messages (`id`,
38
+ `from`, `subject`, `accepted_at`; oldest first, at most 10) and `more`,
39
+ the count not listed. The older fields keep their values. A message that
40
+ was pulled but not opened is `CLAIMED`, still blocks, and is listed so it
41
+ can be opened.
42
+ - One notifier per state directory. `tabus.doorbell` takes an exclusive
43
+ lock on `<state dir>/lock-doorbell` before it reads, rings or records
44
+ anything. A second notifier on the same state directory exits 75 and
45
+ names the one holding the lock. An unknown `DOORBELL_MODE` exits 2.
46
+ - `tabd` binds its port before it prepares the ledger. A port that is
47
+ already taken exits 2 with one line and no traceback.
48
+ - MCP: a tool result with an error code other than `UNKNOWN` (a tabd refusal
49
+ such as `UNREAD_BLOCKED`, a bad argument, no node key, no server) now
50
+ returns with `isError` set, so a client sees the failure without reading
51
+ the result. The result is the same object as before. `UNKNOWN` (the write
52
+ may have been applied) is not marked as an error. See
53
+ [MCP.md](MCP.md#errors-and-retries).
54
+ - MCP: a partial `tabc_open` is not marked as an error. The body was
55
+ received, but recording `INJECTED` failed or its outcome is unknown. Check
56
+ `injected_recorded` and `ack_error`, not only `isError`.
57
+
58
+ ### Unchanged
59
+
60
+ - The ledger schema. Nodes, keys, messages, delivery states, TACs, routes and
61
+ Codex queue receipts are kept. No conversion or registration is required.
62
+ - Recipients are only the ones named. A reply does not reach the parent's
63
+ sender automatically, and it does not make the parent readable to a node
64
+ that could not read it before.
65
+ - `GET /thread` without `limit` uses the largest page size, 500.
66
+
67
+ ### Upgrade notes
68
+
69
+ - Restart `tabd` on 0.2.5 before using the new commands.
70
+ - `send --check`, `status` and `thread`: an older `tabd` has no such path.
71
+ The CLI exits 2 and says the daemon is older than the command needs.
72
+ Nothing is sent or changed.
73
+ - `send --re`: an older `tabd` does not check the reply target. It does not
74
+ resolve a short id, and it stores a full id without the 0.2.5 visibility
75
+ check. Upgrade `tabd` first.
76
+ - Stop the old `tabus.doorbell` before starting the new one. A notifier older
77
+ than 0.2.5 takes no lock, so the new one cannot see it.
78
+ - Restart any running MCP adapter from its host to load the new tools and the
79
+ `isError` change.
80
+ - See [Upgrading from 0.2.4 to 0.2.5](README.md#upgrading-from-024-to-025).
81
+
82
+ ### Known limits
83
+
84
+ - A reply target must be an id of 8 to 36 characters of 0-9, a-f and `-`.
85
+ A message stored with another id form, which a program could send before
86
+ this release, cannot be a reply target.
87
+ - The notifier lock does not cover two state directories (different
88
+ `TABC_HOME`) that share one ledger.
89
+
90
+ ## 0.2.4 — 2026-10-25
91
+
92
+ ### Added
93
+
94
+ - `tabc send --id <UUID>` sends with a caller-chosen message id, so a retry
95
+ after a lost response is not stored twice. A resend goes through the
96
+ usual send checks first, so unread mail can refuse it with
97
+ `UNREAD_BLOCKED`. After those checks, the same id with the same
98
+ envelope prints `stored id=<id>` and, below it,
99
+ `(identical envelope resent — not stored twice)`, and exits 0. With a
100
+ changed envelope it fails with `failed: conflict: …` and exits 1. The id
101
+ is checked before any request and written in canonical form. A value
102
+ that is not a UUID fails with
103
+ `failed: --id must be a full message UUID` and exits 1.
104
+
105
+ ### Unchanged
106
+
107
+ - Without `--id`, `send` uses a new random id as before. The daemon is
108
+ unchanged. The MCP `tabc_send` tool already took a caller-chosen id as
109
+ `message_id`; the CLI now offers the same.
110
+
3
111
  ## 0.2.3 — 2026-10-17
4
112
 
5
113
  ### Added
@@ -50,6 +50,12 @@ tells you which layer to look at.
50
50
  problem. Everyone missing them at once is the notifier, and no amount of
51
51
  re-registering will help.
52
52
 
53
+ From 0.2.5, one notifier runs per state directory. `tabus.doorbell` takes a lock
54
+ on `<state dir>/lock-doorbell`; a second one on the same state directory exits 75
55
+ and names the holder. A notifier older than 0.2.5 takes no lock, so stop it
56
+ before starting a new one. Two state directories (different `TABC_HOME`) that
57
+ share a ledger are not covered by the lock.
58
+
53
59
  For the single-node case, two queries answer it:
54
60
 
55
61
  ```bash
@@ -197,6 +203,31 @@ Two related traps:
197
203
  surprises you, run it under `set -x` and read the real `argv` before suspecting
198
204
  the tool.
199
205
 
206
+ ### Exit codes
207
+
208
+ `tabc` uses the same exit codes for every command:
209
+
210
+ | Exit | Meaning |
211
+ |---|---|
212
+ | 0 | done |
213
+ | 1 | the request failed or was refused: connection, server error, a refused send or ack. A retry can give a different result |
214
+ | 2 | refused to start: missing or invalid input or node identity, a usage error, a daemon older than the command needs, or HTTP 400, 401 or 403. Repeating gives the same result |
215
+ | 3 | `send --check` only: the send would be refused |
216
+
217
+ From 0.2.5, check a send before making it and read your own unread mail
218
+ without changing anything:
219
+
220
+ ```bash
221
+ tabc send --check --sender alice --to bob --subject s --body b # 0 not blocked, 3 would be refused
222
+ tabc status --node alice # counts, oldest unread, what blocks a send
223
+ ```
224
+
225
+ `send --check` runs the same refusals as a send and stores nothing. Its answer
226
+ is true at that moment only; the send itself can still be refused. A check that
227
+ could not run exits 1 or 2 and is never reported as not blocked. `status` writes
228
+ nothing, not even the mailbox open time; a failed query is never shown as zero
229
+ unread.
230
+
200
231
  ---
201
232
 
202
233
  ## Delivery states, and what each one settles
@@ -268,7 +299,11 @@ tabd returns a stable `code`, a plain `message`, structured `details`, and a
268
299
  | `REQUEST_TOO_LARGE` | HTTP request body exceeds 524,288 bytes |
269
300
  | `REQUEST_TIMEOUT` | the declared request body did not arrive within 30 seconds |
270
301
  | `REQUEST_INCOMPLETE` | the connection ended before the declared body length arrived |
271
- | `UNREAD_BLOCKED` | read-before-send is blocking this DM or TAC send |
302
+ | `UNREAD_BLOCKED` | read-before-send is blocking this DM or TAC send. From 0.2.5, `details.messages` lists the blocking messages (`id`, `from`, `subject`, `accepted_at`; oldest first, at most 10) and `details.more` counts the rest |
303
+ | `REPLY_TARGET_INVALID` | from 0.2.5: the reply target is not 8 to 36 characters of 0-9, a-f and `-` |
304
+ | `REPLY_TARGET_UNAVAILABLE` | from 0.2.5: the node cannot see the reply target, or it does not exist (the answer is the same) |
305
+ | `REPLY_TARGET_AMBIGUOUS` | from 0.2.5: the short id matches more than one visible message; the candidates are listed |
306
+ | `THREAD_PAGE_INVALID` | from 0.2.5: `after` is a UUID but not a row of this thread |
272
307
  | `TAC_ID_INVALID` | a TAC operation requires a canonical lowercase UUID; the server does not resolve names |
273
308
  | `TAC_NOT_FOUND` | no TAC matches the supplied identifier |
274
309
  | `TAC_NAME_TAKEN` | the folded name or a reserved legacy identifier is already used |
@@ -111,6 +111,61 @@ titles without that wait, including messages claimed by an earlier call. Use
111
111
  - `tabc_send`: send a DM to comma-separated recipients.
112
112
  - `tabc_tacs`, `tabc_tac_messages`: inspect TAC lists and member-only history.
113
113
  - `tabc_tac_send`: send to an existing TAC's members.
114
+ - `tabc_thread`: outline one thread, one page at a time. Read only.
115
+
116
+ ### Replies
117
+
118
+ `tabc_send` and `tabc_tac_send` take an optional `reply_to`: a full message id,
119
+ or at least its first 8 characters. This is the same as `tabc send --re` in the
120
+ CLI.
121
+
122
+ - The target must be a message the node sent, received, or can read in a TAC it
123
+ belongs to now.
124
+ - A target that is not 8 to 36 characters of 0-9, a-f and `-` is refused with
125
+ `REPLY_TARGET_INVALID` before any lookup. Upper-case hex is accepted and read
126
+ as lower case.
127
+ - tabd refuses any other target the node cannot see with
128
+ `REPLY_TARGET_UNAVAILABLE`. The answer is the same whether the id exists or
129
+ not. Nothing is stored.
130
+ - A prefix that matches more than one visible message is refused with
131
+ `REPLY_TARGET_AMBIGUOUS` and a list of candidates.
132
+ - The reply joins the parent's thread. tabd sets the thread; a client cannot.
133
+ - Recipients are only the ones named. A reply does not go to the parent's sender
134
+ unless that node is named.
135
+ - A recipient who cannot see the parent is shown its id only, not its subject or
136
+ body. A reply does not make the parent readable.
137
+ - The same `message_id` resent with a different `reply_to` is a conflict, as with
138
+ any other envelope field.
139
+
140
+ `tabc_thread(message_id, limit=50, after=None)` returns rows in the drawn order:
141
+ a message, then its replies, depth first.
142
+
143
+ - Each row has id, sender_id, to, subject, accepted_at (UTC, ISO 8601), reply_to
144
+ and depth. Bodies are not included; open one with `tabc_open`.
145
+ - `to` is `{"tac": <name>}` for TAC mail, `{"broadcast": true}` for an
146
+ announcement, and `{"nodes": [...]}` for a DM.
147
+ - The rows are only messages the node sent, received, or can read in a TAC it
148
+ belongs to now.
149
+ - `parent_hidden` means the parent exists but the node cannot see it.
150
+ - `parent_elsewhere` means the parent is visible but on another page.
151
+ - `total` is the number of rows the node can see. `more` and `next_after` give
152
+ the next page: call again with `after` set to `next_after`. `limit` is 1 to 500.
153
+ - Arguments are checked in two places. `limit` outside 1 to 500, or an `after`
154
+ that is not a UUID, is refused by the tool with an argument error, and tabd is
155
+ not called. An upper-case `after` is sent in lower case.
156
+ - An `after` that is a UUID but not a row of this thread is refused by tabd with
157
+ `THREAD_PAGE_INVALID`. A `message_id` of the wrong shape is refused by tabd
158
+ with `REPLY_TARGET_INVALID`; one the node cannot see, with
159
+ `REPLY_TARGET_UNAVAILABLE`.
160
+ - Pages follow the drawn order, not time. A reply that arrives between two page
161
+ reads and is drawn before `after` is not on a later page. Read the thread
162
+ again from the start to see it. `total` changes in that case.
163
+ - Messages accepted in the same second are ordered by id.
164
+ - `tabc_thread` changes no delivery state. It does not mark anything READ and does
165
+ not lift a send block.
166
+
167
+ The CLI equivalent is `tabc thread [--limit N] [--after ID] <id>`. The CLI shows
168
+ times in the local time zone of the machine running it.
114
169
 
115
170
  Use the CLI to create TACs and manage membership. Use the `tac_id` returned by
116
171
  `tabc_tacs`, not its display name. A TAC name can be renamed; its canonical UUID
@@ -133,6 +188,13 @@ section: the MCP adapter still does not wake an agent. See
133
188
  No request is automatically retried. A timeout, connection loss, server error or
134
189
  unusable response after a write returns `UNKNOWN`: the server may have applied it.
135
190
  Only a usable response with a top-level server `code` is a definite refusal.
191
+ A result with an `error` other than `UNKNOWN` is a definite failure and is
192
+ returned with `isError` set; the result object is the same. `UNKNOWN` is not
193
+ marked as an error, because the request may have been applied.
194
+ A partial `tabc_open` is not marked as an error either: the body was received,
195
+ but recording `INJECTED` failed or its outcome is unknown (`state: null`). Its
196
+ result has `ok: false`, `injected_recorded: false` and `ack_error`; check those
197
+ fields, not only `isError`.
136
198
  `retry=never` requires a changed request. `retry=after_condition` requires the
137
199
  reported condition to be cleared. `retry=as_is` permits the same request after
138
200
  stored state has been checked. The full server code, message, details, and retry
@@ -1,6 +1,6 @@
1
- Metadata-Version: 2.1
1
+ Metadata-Version: 2.4
2
2
  Name: tabc
3
- Version: 0.2.3
3
+ Version: 0.2.5
4
4
  Summary: A shared inbox for AI agents and programs on one machine
5
5
  License: MIT License
6
6
 
@@ -27,6 +27,7 @@ License: MIT License
27
27
  Project-URL: Homepage, https://tabc.sh
28
28
  Project-URL: Source, https://github.com/jultabc/tabc
29
29
  Project-URL: Documentation, https://github.com/jultabc/tabc/blob/main/GUIDE.md
30
+ Project-URL: Changelog, https://github.com/jultabc/tabc/blob/main/CHANGELOG.md
30
31
  Project-URL: Issues, https://github.com/jultabc/tabc/issues
31
32
  Keywords: agents,messaging,ipc,cli
32
33
  Classifier: Development Status :: 3 - Alpha
@@ -37,12 +38,15 @@ Classifier: Programming Language :: Python :: 3
37
38
  Classifier: Topic :: Communications
38
39
  Requires-Python: >=3.9
39
40
  Description-Content-Type: text/markdown
40
- Provides-Extra: mcp
41
41
  License-File: LICENSE
42
+ Requires-Dist: cryptography>=41
43
+ Provides-Extra: mcp
44
+ Requires-Dist: mcp<2,>=1.27.1; python_version >= "3.10" and extra == "mcp"
45
+ Dynamic: license-file
42
46
 
43
47
  # tabc
44
48
 
45
- ![tabc](https://raw.githubusercontent.com/jultabc/tabc/main/docs/logo-640.png)
49
+ <img src="https://raw.githubusercontent.com/jultabc/tabc/main/docs/logo-26-25-1.png" alt="tabc" width="320">
46
50
 
47
51
  A shared inbox for AI agents and programs on one machine.
48
52
  Messages are stored locally. Programs can send events; they do not receive replies.
@@ -51,6 +55,16 @@ This is an experimental package. It is not a security boundary between agents
51
55
  using the same operating-system account. Message delivery does not imply that
52
56
  an agent read, understood, or completed a request.
53
57
 
58
+ ## Updates
59
+
60
+ See the [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md)
61
+ for changes and compatibility notes, or
62
+ [GitHub releases](https://github.com/jultabc/tabc/releases) for published versions.
63
+
64
+ Before updating an existing installation, follow the
65
+ [installation and upgrade instructions](https://github.com/jultabc/tabc#readme).
66
+ Keep a backup and follow the stop, install, and restart sequence for your version.
67
+
54
68
  ## Install
55
69
 
56
70
  ```bash
@@ -63,7 +77,8 @@ Desktop agents can use the optional stdio MCP adapter (Python 3.10+):
63
77
  pip install 'tabc[mcp]'
64
78
  ```
65
79
 
66
- It provides DM and TAC messaging, inbox queries and explicit read acknowledgements.
80
+ It provides DM and TAC messaging, replies and threads, inbox queries and explicit read
81
+ acknowledgements. A definite failure comes back with `isError` set.
67
82
  Register a normal node, set `TABC_NODE`, and configure the client to run `tabc-mcp`.
68
83
  The adapter does not start tabd or wake agents on message arrival.
69
84
  See [MCP installation and client configuration](https://github.com/jultabc/tabc/blob/main/MCP.md).
@@ -105,83 +120,6 @@ from the `pull --mode full` detail block, or a unique prefix of it.
105
120
  Terminal notification is a separate process and does not start with the
106
121
  install; see the repository's guide before turning it on.
107
122
 
108
- ## Updating from 0.2.2
109
-
110
- The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
111
- TACs, routes, and Codex queue receipts are kept, and nodes do not register
112
- again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
113
- `tabus.doorbell` from the same installation:
114
-
115
- ```bash
116
- python -m pip install --upgrade "tabc==0.2.3"
117
- # Or, when the local desktop MCP adapter is required:
118
- python -m pip install --upgrade "tabc[mcp]==0.2.3"
119
- ```
120
-
121
- The CLI now accepts the exact name of an open tac and lists candidates instead
122
- of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
123
- is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
124
- unchanged. See the
125
- [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
126
-
127
- ## Updating from 0.2.1
128
-
129
- The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
130
- TACs, routes, and Codex queue receipts are kept. Stop `tabus.doorbell`, install,
131
- restart `tabd`, then start one `tabus.doorbell` from the same installation:
132
-
133
- ```bash
134
- python -m pip install --upgrade "tabc==0.2.2"
135
- # Or, when the local desktop MCP adapter is required:
136
- python -m pip install --upgrade "tabc[mcp]==0.2.2"
137
- ```
138
-
139
- `--kind` is now case-insensitive; `--kind Codex` selects the same Codex queue
140
- route as `--kind codex`. A detached command no longer needs a recognized agent
141
- product: its immediate session-boundary parent qualifies when it owns the
142
- terminal foreground and reads standard input from it. The check proves terminal
143
- ownership, not that the program is an agent. Register again from the intended
144
- terminal and confirm one notification arrives. Codex queue rules are otherwise
145
- unchanged. See the
146
- [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
147
-
148
- ## Updating from 0.2.0
149
-
150
- The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
151
- TACs, and routes are kept. Stop `tabus.doorbell`, install, restart `tabd`, then
152
- start one `tabus.doorbell` from the same installation:
153
-
154
- ```bash
155
- python -m pip install --upgrade "tabc==0.2.1"
156
- # Or, when the local desktop MCP adapter is required:
157
- python -m pip install --upgrade "tabc[mcp]==0.2.1"
158
- ```
159
-
160
- `register` now requires `--kind`. Update scripts that omit it. Codex agents
161
- register again from each conversation after the notifier is replaced. The
162
- notifier creates `codex_queue_receipts.db` in the tabc home directory on its
163
- first Codex queue submission. See the
164
- [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
165
-
166
- ## Updating from 0.1.6
167
-
168
- The upgrade preserves nodes, messages, delivery states, TAC membership, names,
169
- and labels. Stop `tabus.doorbell` and `tabd`. Confirm that the ledger's `-wal`
170
- file is absent or empty (0 bytes), then keep a backup before installing. A
171
- remaining empty WAL or SHM file is safe. Do not continue while the WAL is
172
- non-empty:
173
-
174
- ```bash
175
- python -m pip install --upgrade "tabc==0.2.0"
176
- # Or, when the local desktop MCP adapter is required:
177
- python -m pip install --upgrade "tabc[mcp]==0.2.0"
178
- ```
179
-
180
- Existing string TAC IDs are not converted during installation. Follow the
181
- repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
182
- to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
183
- Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
184
-
185
123
  ## Commands
186
124
 
187
125
  - `tabc register --node alice --kind codex`: register an agent.
@@ -190,6 +128,10 @@ Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.
190
128
  - `tabc read --node bob`: display messages and record them as read.
191
129
  - `tabc sent --node alice`: inspect outgoing delivery states.
192
130
  - `tabc tac search --node alice --query text`: search joined topics without changing read state.
131
+ - `tabc send --sender bob --to alice --re <id> --subject "re" --body "ok"`: reply to a message (0.2.5).
132
+ - `tabc thread <id> --node alice`: outline one thread without changing read state (0.2.5).
133
+ - `tabc send ... --check`: ask whether a send would be refused now, without sending (0.2.5).
134
+ - `tabc status --node alice`: your unread mail and what blocks a send, without changing anything (0.2.5).
193
135
 
194
136
  Register each recipient before sending. tac creators must also join their topic.
195
137
  Since 0.2.0, the server mints a UUID for each new tac. Use that UUID for membership,
@@ -1,6 +1,6 @@
1
1
  # tabc
2
2
 
3
- ![tabc](https://raw.githubusercontent.com/jultabc/tabc/main/docs/logo-640.png)
3
+ <img src="https://raw.githubusercontent.com/jultabc/tabc/main/docs/logo-26-25-1.png" alt="tabc" width="320">
4
4
 
5
5
  A shared inbox for AI agents and programs on one machine.
6
6
  Messages are stored locally. Programs can send events; they do not receive replies.
@@ -9,6 +9,16 @@ This is an experimental package. It is not a security boundary between agents
9
9
  using the same operating-system account. Message delivery does not imply that
10
10
  an agent read, understood, or completed a request.
11
11
 
12
+ ## Updates
13
+
14
+ See the [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md)
15
+ for changes and compatibility notes, or
16
+ [GitHub releases](https://github.com/jultabc/tabc/releases) for published versions.
17
+
18
+ Before updating an existing installation, follow the
19
+ [installation and upgrade instructions](https://github.com/jultabc/tabc#readme).
20
+ Keep a backup and follow the stop, install, and restart sequence for your version.
21
+
12
22
  ## Install
13
23
 
14
24
  ```bash
@@ -21,7 +31,8 @@ Desktop agents can use the optional stdio MCP adapter (Python 3.10+):
21
31
  pip install 'tabc[mcp]'
22
32
  ```
23
33
 
24
- It provides DM and TAC messaging, inbox queries and explicit read acknowledgements.
34
+ It provides DM and TAC messaging, replies and threads, inbox queries and explicit read
35
+ acknowledgements. A definite failure comes back with `isError` set.
25
36
  Register a normal node, set `TABC_NODE`, and configure the client to run `tabc-mcp`.
26
37
  The adapter does not start tabd or wake agents on message arrival.
27
38
  See [MCP installation and client configuration](https://github.com/jultabc/tabc/blob/main/MCP.md).
@@ -63,83 +74,6 @@ from the `pull --mode full` detail block, or a unique prefix of it.
63
74
  Terminal notification is a separate process and does not start with the
64
75
  install; see the repository's guide before turning it on.
65
76
 
66
- ## Updating from 0.2.2
67
-
68
- The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
69
- TACs, routes, and Codex queue receipts are kept, and nodes do not register
70
- again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
71
- `tabus.doorbell` from the same installation:
72
-
73
- ```bash
74
- python -m pip install --upgrade "tabc==0.2.3"
75
- # Or, when the local desktop MCP adapter is required:
76
- python -m pip install --upgrade "tabc[mcp]==0.2.3"
77
- ```
78
-
79
- The CLI now accepts the exact name of an open tac and lists candidates instead
80
- of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
81
- is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
82
- unchanged. See the
83
- [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
84
-
85
- ## Updating from 0.2.1
86
-
87
- The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
88
- TACs, routes, and Codex queue receipts are kept. Stop `tabus.doorbell`, install,
89
- restart `tabd`, then start one `tabus.doorbell` from the same installation:
90
-
91
- ```bash
92
- python -m pip install --upgrade "tabc==0.2.2"
93
- # Or, when the local desktop MCP adapter is required:
94
- python -m pip install --upgrade "tabc[mcp]==0.2.2"
95
- ```
96
-
97
- `--kind` is now case-insensitive; `--kind Codex` selects the same Codex queue
98
- route as `--kind codex`. A detached command no longer needs a recognized agent
99
- product: its immediate session-boundary parent qualifies when it owns the
100
- terminal foreground and reads standard input from it. The check proves terminal
101
- ownership, not that the program is an agent. Register again from the intended
102
- terminal and confirm one notification arrives. Codex queue rules are otherwise
103
- unchanged. See the
104
- [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
105
-
106
- ## Updating from 0.2.0
107
-
108
- The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
109
- TACs, and routes are kept. Stop `tabus.doorbell`, install, restart `tabd`, then
110
- start one `tabus.doorbell` from the same installation:
111
-
112
- ```bash
113
- python -m pip install --upgrade "tabc==0.2.1"
114
- # Or, when the local desktop MCP adapter is required:
115
- python -m pip install --upgrade "tabc[mcp]==0.2.1"
116
- ```
117
-
118
- `register` now requires `--kind`. Update scripts that omit it. Codex agents
119
- register again from each conversation after the notifier is replaced. The
120
- notifier creates `codex_queue_receipts.db` in the tabc home directory on its
121
- first Codex queue submission. See the
122
- [changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
123
-
124
- ## Updating from 0.1.6
125
-
126
- The upgrade preserves nodes, messages, delivery states, TAC membership, names,
127
- and labels. Stop `tabus.doorbell` and `tabd`. Confirm that the ledger's `-wal`
128
- file is absent or empty (0 bytes), then keep a backup before installing. A
129
- remaining empty WAL or SHM file is safe. Do not continue while the WAL is
130
- non-empty:
131
-
132
- ```bash
133
- python -m pip install --upgrade "tabc==0.2.0"
134
- # Or, when the local desktop MCP adapter is required:
135
- python -m pip install --upgrade "tabc[mcp]==0.2.0"
136
- ```
137
-
138
- Existing string TAC IDs are not converted during installation. Follow the
139
- repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
140
- to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
141
- Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
142
-
143
77
  ## Commands
144
78
 
145
79
  - `tabc register --node alice --kind codex`: register an agent.
@@ -148,6 +82,10 @@ Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.
148
82
  - `tabc read --node bob`: display messages and record them as read.
149
83
  - `tabc sent --node alice`: inspect outgoing delivery states.
150
84
  - `tabc tac search --node alice --query text`: search joined topics without changing read state.
85
+ - `tabc send --sender bob --to alice --re <id> --subject "re" --body "ok"`: reply to a message (0.2.5).
86
+ - `tabc thread <id> --node alice`: outline one thread without changing read state (0.2.5).
87
+ - `tabc send ... --check`: ask whether a send would be refused now, without sending (0.2.5).
88
+ - `tabc status --node alice`: your unread mail and what blocks a send, without changing anything (0.2.5).
151
89
 
152
90
  Register each recipient before sending. tac creators must also join their topic.
153
91
  Since 0.2.0, the server mints a UUID for each new tac. Use that UUID for membership,
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "tabc"
7
- version = "0.2.3"
7
+ version = "0.2.5"
8
8
  description = "A shared inbox for AI agents and programs on one machine"
9
9
  readme = "PYPI.md"
10
10
  requires-python = ">=3.9"
@@ -40,6 +40,7 @@ mcp = ["mcp>=1.27.1,<2; python_version >= '3.10'"]
40
40
  Homepage = "https://tabc.sh"
41
41
  Source = "https://github.com/jultabc/tabc"
42
42
  Documentation = "https://github.com/jultabc/tabc/blob/main/GUIDE.md"
43
+ Changelog = "https://github.com/jultabc/tabc/blob/main/CHANGELOG.md"
43
44
  Issues = "https://github.com/jultabc/tabc/issues"
44
45
 
45
46
  [project.scripts]