tabc 0.2.4__tar.gz → 0.2.6__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.4 → tabc-0.2.6}/CHANGELOG.md +108 -1
  2. {tabc-0.2.4 → tabc-0.2.6}/GUIDE.md +37 -2
  3. {tabc-0.2.4 → tabc-0.2.6}/MCP.md +64 -1
  4. {tabc-0.2.4/tabc.egg-info → tabc-0.2.6}/PKG-INFO +14 -5
  5. {tabc-0.2.4 → tabc-0.2.6}/PYPI.md +8 -2
  6. {tabc-0.2.4 → tabc-0.2.6}/pyproject.toml +1 -1
  7. {tabc-0.2.4 → tabc-0.2.6/tabc.egg-info}/PKG-INFO +14 -5
  8. {tabc-0.2.4 → tabc-0.2.6}/tabc.egg-info/SOURCES.txt +1 -0
  9. {tabc-0.2.4 → tabc-0.2.6}/tabus/bus.py +220 -31
  10. {tabc-0.2.4 → tabc-0.2.6}/tabus/cli.py +333 -10
  11. {tabc-0.2.4 → tabc-0.2.6}/tabus/daemon.py +196 -6
  12. {tabc-0.2.4 → tabc-0.2.6}/tabus/doorbell.py +58 -1
  13. {tabc-0.2.4 → tabc-0.2.6}/tabus/mcp_server.py +72 -10
  14. tabc-0.2.6/tabus/reply_link.py +287 -0
  15. {tabc-0.2.4 → tabc-0.2.6}/tabus/send_refusal.py +22 -4
  16. {tabc-0.2.4 → tabc-0.2.6}/LICENSE +0 -0
  17. {tabc-0.2.4 → tabc-0.2.6}/MANIFEST.in +0 -0
  18. {tabc-0.2.4 → tabc-0.2.6}/setup.cfg +0 -0
  19. {tabc-0.2.4 → tabc-0.2.6}/tabc.egg-info/dependency_links.txt +0 -0
  20. {tabc-0.2.4 → tabc-0.2.6}/tabc.egg-info/entry_points.txt +0 -0
  21. {tabc-0.2.4 → tabc-0.2.6}/tabc.egg-info/requires.txt +0 -0
  22. {tabc-0.2.4 → tabc-0.2.6}/tabc.egg-info/top_level.txt +0 -0
  23. {tabc-0.2.4 → tabc-0.2.6}/tabus/__init__.py +0 -0
  24. {tabc-0.2.4 → tabc-0.2.6}/tabus/admin.py +0 -0
  25. {tabc-0.2.4 → tabc-0.2.6}/tabus/codex_queue.py +0 -0
  26. {tabc-0.2.4 → tabc-0.2.6}/tabus/compat_bcn.py +0 -0
  27. {tabc-0.2.4 → tabc-0.2.6}/tabus/compat_busd.py +0 -0
  28. {tabc-0.2.4 → tabc-0.2.6}/tabus/doorbell_poll.py +0 -0
  29. {tabc-0.2.4 → tabc-0.2.6}/tabus/lang.py +0 -0
  30. {tabc-0.2.4 → tabc-0.2.6}/tabus/locales/en.json +0 -0
  31. {tabc-0.2.4 → tabc-0.2.6}/tabus/nodekey.py +0 -0
  32. {tabc-0.2.4 → tabc-0.2.6}/tabus/paths.py +0 -0
  33. {tabc-0.2.4 → tabc-0.2.6}/tabus/process_argv.py +0 -0
  34. {tabc-0.2.4 → tabc-0.2.6}/tabus/route_capture.py +0 -0
  35. {tabc-0.2.4 → tabc-0.2.6}/tabus/sent.py +0 -0
  36. {tabc-0.2.4 → tabc-0.2.6}/tabus/tac_identity.py +0 -0
  37. {tabc-0.2.4 → tabc-0.2.6}/tabus/tac_lookup.py +0 -0
  38. {tabc-0.2.4 → tabc-0.2.6}/tabus/tac_migration.py +0 -0
  39. {tabc-0.2.4 → tabc-0.2.6}/tabus/tac_refusal.py +0 -0
  40. {tabc-0.2.4 → tabc-0.2.6}/tabus/tac_search.py +0 -0
  41. {tabc-0.2.4 → tabc-0.2.6}/tabus/tac_store.py +0 -0
  42. {tabc-0.2.4 → tabc-0.2.6}/tabus/terminal_frontend.py +0 -0
@@ -1,5 +1,112 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.6 — 2026-11-22
4
+
5
+ ### Fixed
6
+
7
+ - `tabc open` on a message already marked READ or PROCESSED answered
8
+ `no such delivery`, which reads as a wrong id. It now shows the body again
9
+ and changes nothing (no state move, no row written), and prints
10
+ `(already read — state unchanged)`. A DEAD or QUARANTINED delivery, or a
11
+ body that no longer matches its hash, answers 409 with the state named.
12
+ An id that matches nothing still answers 404.
13
+ - `tabc read` skips a listed message that was marked read elsewhere before it
14
+ was opened, instead of printing it and reporting that the READ mark failed.
15
+ - Opening a message whose body fails its envelope check closed the
16
+ connection with no answer the first time, because the quarantined row was
17
+ read as a body. It now answers 409 with state `QUARANTINED` and the reason,
18
+ the first time and after. `tabc open` prints the reason and exits 1.
19
+ - A message another reader claimed in the same instant answers 409
20
+ `being opened by another reader — try again` instead of naming its state as
21
+ if it could not be opened.
22
+
23
+ ## 0.2.5 — 2026-11-20
24
+
25
+ ### Added
26
+
27
+ - `tabc send --check` sends nothing. It asks the daemon whether this send
28
+ would be refused now, and by which unread messages. It runs the same
29
+ refusals as a send and stops before the first write. Exit 0 not blocked,
30
+ 1 the check failed while running (a retry can work), 2 the daemon cannot
31
+ check (an older daemon, HTTP 400, 401 or 403), 3 the send would be
32
+ refused. A failed check is never reported as not blocked.
33
+ - `tabc status` prints this node's unread mail without changing anything:
34
+ counts of messages not opened and opened but not marked READ, by kind
35
+ (dm, tac, broadcast), the oldest message of each group, and which unread
36
+ mail blocks a send (DMs per sending node, tac messages per tac). It
37
+ writes nothing, not even the mailbox open time. Exit 0 read, 1 the query
38
+ failed, 2 the daemon cannot answer. A failed query is never shown as zero
39
+ unread.
40
+ - Reply links. `tabc send --re <id>` stores a reply to a message the sender
41
+ sent, received, or can read in a tac it belongs to now. `tabc read` and
42
+ `tabc open` print a `re` line with the parent's short id and subject.
43
+ - `tabc thread <id>` prints an outline of one thread: time, sender,
44
+ recipients, subject and id per message, with replies indented. It shows no
45
+ bodies and marks nothing READ. Times are in the local time zone of the
46
+ machine running it, with the zone name.
47
+ - `tabc thread --limit N --after ID` reads a long thread one page at a time
48
+ (`--limit` default 100, largest 500). A page that has more after it ends
49
+ with the command for the next page. A reply whose parent is on another page
50
+ is marked `(re: <id> on another page)`. A reply whose parent the node cannot
51
+ see is marked `(re: not visible)`.
52
+ - MCP: `reply_to` on `tabc_send` and `tabc_tac_send`, and a read-only
53
+ `tabc_thread` tool with the same paging. See [MCP.md](MCP.md#replies).
54
+
55
+ ### Changed
56
+
57
+ - `UNREAD_BLOCKED` details now also list the blocking messages (`id`,
58
+ `from`, `subject`, `accepted_at`; oldest first, at most 10) and `more`,
59
+ the count not listed. The older fields keep their values. A message that
60
+ was pulled but not opened is `CLAIMED`, still blocks, and is listed so it
61
+ can be opened.
62
+ - One notifier per state directory. `tabus.doorbell` takes an exclusive
63
+ lock on `<state dir>/lock-doorbell` before it reads, rings or records
64
+ anything. A second notifier on the same state directory exits 75 and
65
+ names the one holding the lock. An unknown `DOORBELL_MODE` exits 2.
66
+ - `tabd` binds its port before it prepares the ledger. A port that is
67
+ already taken exits 2 with one line and no traceback.
68
+ - MCP: a tool result with an error code other than `UNKNOWN` (a tabd refusal
69
+ such as `UNREAD_BLOCKED`, a bad argument, no node key, no server) now
70
+ returns with `isError` set, so a client sees the failure without reading
71
+ the result. The result is the same object as before. `UNKNOWN` (the write
72
+ may have been applied) is not marked as an error. See
73
+ [MCP.md](MCP.md#errors-and-retries).
74
+ - MCP: a partial `tabc_open` is not marked as an error. The body was
75
+ received, but recording `INJECTED` failed or its outcome is unknown. Check
76
+ `injected_recorded` and `ack_error`, not only `isError`.
77
+
78
+ ### Unchanged
79
+
80
+ - The ledger schema. Nodes, keys, messages, delivery states, TACs, routes and
81
+ Codex queue receipts are kept. No conversion or registration is required.
82
+ - Recipients are only the ones named. A reply does not reach the parent's
83
+ sender automatically, and it does not make the parent readable to a node
84
+ that could not read it before.
85
+ - `GET /thread` without `limit` uses the largest page size, 500.
86
+
87
+ ### Upgrade notes
88
+
89
+ - Restart `tabd` on 0.2.5 before using the new commands.
90
+ - `send --check`, `status` and `thread`: an older `tabd` has no such path.
91
+ The CLI exits 2 and says the daemon is older than the command needs.
92
+ Nothing is sent or changed.
93
+ - `send --re`: an older `tabd` does not check the reply target. It does not
94
+ resolve a short id, and it stores a full id without the 0.2.5 visibility
95
+ check. Upgrade `tabd` first.
96
+ - Stop the old `tabus.doorbell` before starting the new one. A notifier older
97
+ than 0.2.5 takes no lock, so the new one cannot see it.
98
+ - Restart any running MCP adapter from its host to load the new tools and the
99
+ `isError` change.
100
+ - See [Upgrading from 0.2.4 to 0.2.5](README.md#upgrading-from-024-to-025).
101
+
102
+ ### Known limits
103
+
104
+ - A reply target must be an id of 8 to 36 characters of 0-9, a-f and `-`.
105
+ A message stored with another id form, which a program could send before
106
+ this release, cannot be a reply target.
107
+ - The notifier lock does not cover two state directories (different
108
+ `TABC_HOME`) that share one ledger.
109
+
3
110
  ## 0.2.4 — 2026-10-25
4
111
 
5
112
  ### Added
@@ -9,7 +116,7 @@
9
116
  usual send checks first, so unread mail can refuse it with
10
117
  `UNREAD_BLOCKED`. After those checks, the same id with the same
11
118
  envelope prints `stored id=<id>` and, below it,
12
- `identical envelope resent — not stored twice`, and exits 0. With a
119
+ `(identical envelope resent — not stored twice)`, and exits 0. With a
13
120
  changed envelope it fails with `failed: conflict: …` and exits 1. The id
14
121
  is checked before any request and written in canonical form. A value
15
122
  that is not a UUID fails with
@@ -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 |
@@ -348,7 +383,7 @@ tabc send --sender alice --to bob --subject "hello" --body "first"
348
383
 
349
384
  # shell 2
350
385
  tabc dm --node bob # the subject appears, state unchanged
351
- tabc open --node bob --id <full-uuid> # body prints, state becomes INJECTED
386
+ tabc open --node bob --id <full-uuid> # body prints, state becomes INJECTED (an already READ or PROCESSED message prints, unchanged)
352
387
  tabc ack --node bob --id <full-uuid> --state READ
353
388
 
354
389
  # shell 1
@@ -94,7 +94,8 @@ the stored message; it does not confirm that the recipient has read it.
94
94
  On the receiving agent:
95
95
 
96
96
  1. Call `tabc_pull`. It claims new deliveries and returns bodies.
97
- 2. Call `tabc_open` with the full message UUID. It records `INJECTED`.
97
+ 2. Call `tabc_open` with the full message UUID. It records `INJECTED`. A message
98
+ already `READ` or `PROCESSED` is shown again and keeps its state.
98
99
  3. Call `tabc_ack` with state `READ` after reviewing the message.
99
100
  4. Record `PROCESSED` only after processing it. This records an outcome, not its correctness.
100
101
 
@@ -111,6 +112,61 @@ titles without that wait, including messages claimed by an earlier call. Use
111
112
  - `tabc_send`: send a DM to comma-separated recipients.
112
113
  - `tabc_tacs`, `tabc_tac_messages`: inspect TAC lists and member-only history.
113
114
  - `tabc_tac_send`: send to an existing TAC's members.
115
+ - `tabc_thread`: outline one thread, one page at a time. Read only.
116
+
117
+ ### Replies
118
+
119
+ `tabc_send` and `tabc_tac_send` take an optional `reply_to`: a full message id,
120
+ or at least its first 8 characters. This is the same as `tabc send --re` in the
121
+ CLI.
122
+
123
+ - The target must be a message the node sent, received, or can read in a TAC it
124
+ belongs to now.
125
+ - A target that is not 8 to 36 characters of 0-9, a-f and `-` is refused with
126
+ `REPLY_TARGET_INVALID` before any lookup. Upper-case hex is accepted and read
127
+ as lower case.
128
+ - tabd refuses any other target the node cannot see with
129
+ `REPLY_TARGET_UNAVAILABLE`. The answer is the same whether the id exists or
130
+ not. Nothing is stored.
131
+ - A prefix that matches more than one visible message is refused with
132
+ `REPLY_TARGET_AMBIGUOUS` and a list of candidates.
133
+ - The reply joins the parent's thread. tabd sets the thread; a client cannot.
134
+ - Recipients are only the ones named. A reply does not go to the parent's sender
135
+ unless that node is named.
136
+ - A recipient who cannot see the parent is shown its id only, not its subject or
137
+ body. A reply does not make the parent readable.
138
+ - The same `message_id` resent with a different `reply_to` is a conflict, as with
139
+ any other envelope field.
140
+
141
+ `tabc_thread(message_id, limit=50, after=None)` returns rows in the drawn order:
142
+ a message, then its replies, depth first.
143
+
144
+ - Each row has id, sender_id, to, subject, accepted_at (UTC, ISO 8601), reply_to
145
+ and depth. Bodies are not included; open one with `tabc_open`.
146
+ - `to` is `{"tac": <name>}` for TAC mail, `{"broadcast": true}` for an
147
+ announcement, and `{"nodes": [...]}` for a DM.
148
+ - The rows are only messages the node sent, received, or can read in a TAC it
149
+ belongs to now.
150
+ - `parent_hidden` means the parent exists but the node cannot see it.
151
+ - `parent_elsewhere` means the parent is visible but on another page.
152
+ - `total` is the number of rows the node can see. `more` and `next_after` give
153
+ the next page: call again with `after` set to `next_after`. `limit` is 1 to 500.
154
+ - Arguments are checked in two places. `limit` outside 1 to 500, or an `after`
155
+ that is not a UUID, is refused by the tool with an argument error, and tabd is
156
+ not called. An upper-case `after` is sent in lower case.
157
+ - An `after` that is a UUID but not a row of this thread is refused by tabd with
158
+ `THREAD_PAGE_INVALID`. A `message_id` of the wrong shape is refused by tabd
159
+ with `REPLY_TARGET_INVALID`; one the node cannot see, with
160
+ `REPLY_TARGET_UNAVAILABLE`.
161
+ - Pages follow the drawn order, not time. A reply that arrives between two page
162
+ reads and is drawn before `after` is not on a later page. Read the thread
163
+ again from the start to see it. `total` changes in that case.
164
+ - Messages accepted in the same second are ordered by id.
165
+ - `tabc_thread` changes no delivery state. It does not mark anything READ and does
166
+ not lift a send block.
167
+
168
+ The CLI equivalent is `tabc thread [--limit N] [--after ID] <id>`. The CLI shows
169
+ times in the local time zone of the machine running it.
114
170
 
115
171
  Use the CLI to create TACs and manage membership. Use the `tac_id` returned by
116
172
  `tabc_tacs`, not its display name. A TAC name can be renamed; its canonical UUID
@@ -133,6 +189,13 @@ section: the MCP adapter still does not wake an agent. See
133
189
  No request is automatically retried. A timeout, connection loss, server error or
134
190
  unusable response after a write returns `UNKNOWN`: the server may have applied it.
135
191
  Only a usable response with a top-level server `code` is a definite refusal.
192
+ A result with an `error` other than `UNKNOWN` is a definite failure and is
193
+ returned with `isError` set; the result object is the same. `UNKNOWN` is not
194
+ marked as an error, because the request may have been applied.
195
+ A partial `tabc_open` is not marked as an error either: the body was received,
196
+ but recording `INJECTED` failed or its outcome is unknown (`state: null`). Its
197
+ result has `ok: false`, `injected_recorded: false` and `ack_error`; check those
198
+ fields, not only `isError`.
136
199
  `retry=never` requires a changed request. `retry=after_condition` requires the
137
200
  reported condition to be cleared. `retry=as_is` permits the same request after
138
201
  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.4
3
+ Version: 0.2.6
4
4
  Summary: A shared inbox for AI agents and programs on one machine
5
5
  License: MIT License
6
6
 
@@ -38,12 +38,15 @@ Classifier: Programming Language :: Python :: 3
38
38
  Classifier: Topic :: Communications
39
39
  Requires-Python: >=3.9
40
40
  Description-Content-Type: text/markdown
41
- Provides-Extra: mcp
42
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
43
46
 
44
47
  # tabc
45
48
 
46
- ![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">
47
50
 
48
51
  A shared inbox for AI agents and programs on one machine.
49
52
  Messages are stored locally. Programs can send events; they do not receive replies.
@@ -74,7 +77,8 @@ Desktop agents can use the optional stdio MCP adapter (Python 3.10+):
74
77
  pip install 'tabc[mcp]'
75
78
  ```
76
79
 
77
- 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.
78
82
  Register a normal node, set `TABC_NODE`, and configure the client to run `tabc-mcp`.
79
83
  The adapter does not start tabd or wake agents on message arrival.
80
84
  See [MCP installation and client configuration](https://github.com/jultabc/tabc/blob/main/MCP.md).
@@ -122,8 +126,13 @@ install; see the repository's guide before turning it on.
122
126
  - `tabc send --sender alice --to bob --subject "Hello" --body "Ready to collaborate."`: send a dm.
123
127
  - `tabc dm --node bob`: list unread messages.
124
128
  - `tabc read --node bob`: display messages and record them as read.
129
+ - `tabc open --node bob --id <id>`: open one message; one already read shows again, unchanged (0.2.6).
125
130
  - `tabc sent --node alice`: inspect outgoing delivery states.
126
131
  - `tabc tac search --node alice --query text`: search joined topics without changing read state.
132
+ - `tabc send --sender bob --to alice --re <id> --subject "re" --body "ok"`: reply to a message (0.2.5).
133
+ - `tabc thread <id> --node alice`: outline one thread without changing read state (0.2.5).
134
+ - `tabc send ... --check`: ask whether a send would be refused now, without sending (0.2.5).
135
+ - `tabc status --node alice`: your unread mail and what blocks a send, without changing anything (0.2.5).
127
136
 
128
137
  Register each recipient before sending. tac creators must also join their topic.
129
138
  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.
@@ -31,7 +31,8 @@ Desktop agents can use the optional stdio MCP adapter (Python 3.10+):
31
31
  pip install 'tabc[mcp]'
32
32
  ```
33
33
 
34
- 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.
35
36
  Register a normal node, set `TABC_NODE`, and configure the client to run `tabc-mcp`.
36
37
  The adapter does not start tabd or wake agents on message arrival.
37
38
  See [MCP installation and client configuration](https://github.com/jultabc/tabc/blob/main/MCP.md).
@@ -79,8 +80,13 @@ install; see the repository's guide before turning it on.
79
80
  - `tabc send --sender alice --to bob --subject "Hello" --body "Ready to collaborate."`: send a dm.
80
81
  - `tabc dm --node bob`: list unread messages.
81
82
  - `tabc read --node bob`: display messages and record them as read.
83
+ - `tabc open --node bob --id <id>`: open one message; one already read shows again, unchanged (0.2.6).
82
84
  - `tabc sent --node alice`: inspect outgoing delivery states.
83
85
  - `tabc tac search --node alice --query text`: search joined topics without changing read state.
86
+ - `tabc send --sender bob --to alice --re <id> --subject "re" --body "ok"`: reply to a message (0.2.5).
87
+ - `tabc thread <id> --node alice`: outline one thread without changing read state (0.2.5).
88
+ - `tabc send ... --check`: ask whether a send would be refused now, without sending (0.2.5).
89
+ - `tabc status --node alice`: your unread mail and what blocks a send, without changing anything (0.2.5).
84
90
 
85
91
  Register each recipient before sending. tac creators must also join their topic.
86
92
  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.4"
7
+ version = "0.2.6"
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"
@@ -1,6 +1,6 @@
1
- Metadata-Version: 2.1
1
+ Metadata-Version: 2.4
2
2
  Name: tabc
3
- Version: 0.2.4
3
+ Version: 0.2.6
4
4
  Summary: A shared inbox for AI agents and programs on one machine
5
5
  License: MIT License
6
6
 
@@ -38,12 +38,15 @@ Classifier: Programming Language :: Python :: 3
38
38
  Classifier: Topic :: Communications
39
39
  Requires-Python: >=3.9
40
40
  Description-Content-Type: text/markdown
41
- Provides-Extra: mcp
42
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
43
46
 
44
47
  # tabc
45
48
 
46
- ![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">
47
50
 
48
51
  A shared inbox for AI agents and programs on one machine.
49
52
  Messages are stored locally. Programs can send events; they do not receive replies.
@@ -74,7 +77,8 @@ Desktop agents can use the optional stdio MCP adapter (Python 3.10+):
74
77
  pip install 'tabc[mcp]'
75
78
  ```
76
79
 
77
- 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.
78
82
  Register a normal node, set `TABC_NODE`, and configure the client to run `tabc-mcp`.
79
83
  The adapter does not start tabd or wake agents on message arrival.
80
84
  See [MCP installation and client configuration](https://github.com/jultabc/tabc/blob/main/MCP.md).
@@ -122,8 +126,13 @@ install; see the repository's guide before turning it on.
122
126
  - `tabc send --sender alice --to bob --subject "Hello" --body "Ready to collaborate."`: send a dm.
123
127
  - `tabc dm --node bob`: list unread messages.
124
128
  - `tabc read --node bob`: display messages and record them as read.
129
+ - `tabc open --node bob --id <id>`: open one message; one already read shows again, unchanged (0.2.6).
125
130
  - `tabc sent --node alice`: inspect outgoing delivery states.
126
131
  - `tabc tac search --node alice --query text`: search joined topics without changing read state.
132
+ - `tabc send --sender bob --to alice --re <id> --subject "re" --body "ok"`: reply to a message (0.2.5).
133
+ - `tabc thread <id> --node alice`: outline one thread without changing read state (0.2.5).
134
+ - `tabc send ... --check`: ask whether a send would be refused now, without sending (0.2.5).
135
+ - `tabc status --node alice`: your unread mail and what blocks a send, without changing anything (0.2.5).
127
136
 
128
137
  Register each recipient before sending. tac creators must also join their topic.
129
138
  Since 0.2.0, the server mints a UUID for each new tac. Use that UUID for membership,
@@ -26,6 +26,7 @@ tabus/mcp_server.py
26
26
  tabus/nodekey.py
27
27
  tabus/paths.py
28
28
  tabus/process_argv.py
29
+ tabus/reply_link.py
29
30
  tabus/route_capture.py
30
31
  tabus/send_refusal.py
31
32
  tabus/sent.py