tabc 0.2.1__tar.gz → 0.2.2__tar.gz

{tabc-0.2.1 → tabc-0.2.2}/CHANGELOG.md

@@ -1,5 +1,50 @@
 # Changelog
 
+## 0.2.2 — 2026-10-17
+
+### Changed
+
+- `register` treats `--kind` case-insensitively and stores it in lowercase.
+  `--kind OpenCode` registers `opencode`.
+- Terminal route capture at a detached session boundary no longer requires a
+  recognized Codex or Claude CLI. The immediate session-boundary parent
+  qualifies when it belongs to the same OS user, leads the target terminal's
+  foreground process group, and reads standard input from that terminal.
+  Process state, executable path, and standard input are checked again before
+  the route is accepted. Product names and install directories are not an
+  admission list.
+- Codex queue selection under `--kind codex --auto-enter on` and its fallback
+  rules are unchanged. Because the kind is case-folded, `--kind Codex` now
+  selects the same queue route.
+
+### Notes
+
+- The check verifies terminal ownership, not whether the program is an agent.
+  A foreground program that reads the terminal can qualify even if it is not
+  an agent. Automatic Enter remains a separate opt-in.
+- No dedicated adapter for another agent product is added. The MCP adapter
+  still does not wake an agent.
+
+### Upgrade notes (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 0.2.2, restart `tabd`, then start one
+  `tabus.doorbell` from the same installation:
+
+```bash
+python -m pip install --upgrade "tabc==0.2.2"
+# Or, for desktop MCP support:
+python -m pip install --upgrade "tabc[mcp]==0.2.2"
+```
+
+- Stored routes are not migrated. A failed capture does not replace an
+  existing route. Register again from the intended terminal, then confirm one
+  notification arrives.
+- If a desktop client runs `tabc-mcp`, restart that MCP process from the client
+  after the upgrade so it loads the new installation.
+- After restart, `tabc --version` and `tabd --version` report 0.2.2.
+
 ## 0.2.1 — 2026-10-15
 
 ### Added

{tabc-0.2.1/tabc.egg-info → tabc-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.1
 Name: tabc
-Version: 0.2.1
+Version: 0.2.2
 Summary: A shared inbox for AI agents and programs on one machine
 License: MIT License
         
@@ -37,11 +37,8 @@ Classifier: Programming Language :: Python :: 3
 Classifier: Topic :: Communications
 Requires-Python: >=3.9
 Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: cryptography>=41
 Provides-Extra: mcp
-Requires-Dist: mcp<2,>=1.27.1; python_version >= "3.10" and extra == "mcp"
-Dynamic: license-file
+License-File: LICENSE
 
 # tabc
 
@@ -108,6 +105,27 @@ 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.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,
@@ -143,7 +161,7 @@ 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".
+Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
 
 ## Commands
 

{tabc-0.2.1 → tabc-0.2.2}/PYPI.md

@@ -63,6 +63,27 @@ 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.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,
@@ -98,7 +119,7 @@ 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".
+Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
 
 ## Commands
 

{tabc-0.2.1 → tabc-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "tabc"
-version = "0.2.1"
+version = "0.2.2"
 description = "A shared inbox for AI agents and programs on one machine"
 readme = "PYPI.md"
 requires-python = ">=3.9"

{tabc-0.2.1 → tabc-0.2.2/tabc.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.1
 Name: tabc
-Version: 0.2.1
+Version: 0.2.2
 Summary: A shared inbox for AI agents and programs on one machine
 License: MIT License
         
@@ -37,11 +37,8 @@ Classifier: Programming Language :: Python :: 3
 Classifier: Topic :: Communications
 Requires-Python: >=3.9
 Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: cryptography>=41
 Provides-Extra: mcp
-Requires-Dist: mcp<2,>=1.27.1; python_version >= "3.10" and extra == "mcp"
-Dynamic: license-file
+License-File: LICENSE
 
 # tabc
 
@@ -108,6 +105,27 @@ 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.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,
@@ -143,7 +161,7 @@ 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".
+Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
 
 ## Commands
 

{tabc-0.2.1 → tabc-0.2.2}/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.1"
+__version__ = "0.2.2"
 PROTOCOL_VERSION = "tabus.v1"
 
 # TTLs. Past these, a derived status counts as old.

{tabc-0.2.1 → tabc-0.2.2}/tabus/cli.py

@@ -251,6 +251,7 @@ def fn_config(a):
 
 def fn_register(a):
     node = _require_acting_node(a.node)
+    a.kind = a.kind.casefold()
     payload = {"node": node, "kind": a.kind}
     take_route = bool(getattr(a, "take_route", False))
     setting = getattr(a, "auto_enter", None)

{tabc-0.2.1 → tabc-0.2.2}/tabus/route_capture.py

@@ -6,8 +6,8 @@ that terminal.  A detached shared runner can therefore carry one tab's route,
 allocate a fresh PTY, and still register the stale tab.  Route capture accepts
 the inherited key only when its resolved TTY equals the controlling TTY of this
 process or a same-session ancestor. A detached command may also use its immediate
-session-boundary parent when that parent is a recognized native interactive CLI
-and the foreground process-group leader of the target terminal.
+session-boundary parent when that parent owns the target terminal foreground
+process group and its standard input is that same terminal, regardless of kind.
 """
 
 import os
@@ -99,7 +99,7 @@ def terminal_tty(
 
     ``ps`` is used instead of ``/proc`` so this works on both macOS and Linux.
     Any lookup failure is a negative result. The cross-session fallback is
-    restricted to a checked native foreground CLI, not arbitrary ancestors.
+    restricted to a checked foreground terminal owner, not arbitrary ancestors.
     """
     inspect = process_row or _process_row
     inspect_session = process_session or _session_id

{tabc-0.2.1 → tabc-0.2.2}/tabus/terminal_frontend.py

@@ -1,7 +1,7 @@
-"""Recognize a foreground native agent CLI, never a generic terminal ancestor.
+"""Verify a foreground terminal owner without a product-name allowlist.
 
 This is local routing evidence, not an isolation boundary against a malicious
-process running as the same OS user. Unknown launch modes fail closed.
+process running as the same OS user. Missing terminal evidence fails closed.
 """
 
 import ctypes
@@ -57,7 +57,7 @@ def executable_kind(executable, user_home):
 
 
 def interactive_arguments(kind, argv):
-    """Allow inspected interactive modes only; no arbitrary prompt/subcommand."""
+    """Legacy argument classifier; not used by generic route registration."""
     if not argv or os.path.basename(argv[0]) != kind:
         return False
     flags = {
@@ -120,11 +120,27 @@ def process_info(pid):
             fields[4], args)
 
 
+def input_terminal(pid):
+    """Resolve fd 0, not inherited environment variables or a process name."""
+    if sys.platform.startswith("linux"):
+        return os.path.realpath(os.readlink(f"/proc/{int(pid)}/fd/0"))
+    if sys.platform == "darwin":
+        result = subprocess.run(
+            ["/usr/sbin/lsof", "-a", "-p", str(int(pid)), "-d", "0", "-Fn"],
+            capture_output=True, text=True, timeout=1, check=False,
+        )
+        names = [line[1:] for line in result.stdout.splitlines() if line.startswith("n")]
+        if result.returncode == 0 and len(names) == 1:
+            return names[0]
+    return None
+
+
 def foreground_frontend_tty(pid, expected_tty, inspect=None, executable=None,
-                            uid=None, user_home=None):
+                            uid=None, user_home=None, stdin_terminal=None):
     """Only the boundary parent itself may qualify; never walk past a server."""
     inspect = inspect or process_info
     executable = executable or native_executable
+    stdin_terminal = stdin_terminal or input_terminal
     uid = os.getuid() if uid is None else uid
     try:
         user_home = pwd.getpwuid(uid).pw_dir if user_home is None else user_home
@@ -135,11 +151,15 @@ def foreground_frontend_tty(pid, expected_tty, inspect=None, executable=None,
         if owner != uid or not (pid == group == foreground) or tty != expected_tty:
             return None
         path = executable(pid)
-        kind = executable_kind(path, user_home) if path else None
-        if kind is None or not interactive_arguments(kind, argv):
+        # Generic terminal routing is independent of kind and installation path.
+        # The immediate boundary parent must own the foreground group AND read
+        # from that terminal. A pipe-backed server is not a terminal recipient.
+        input_path = "/dev/" + expected_tty.removeprefix("/dev/")
+        if not path or stdin_terminal(pid) != input_path:
             return None
         # Recheck mutable process state around executable and command inspection.
-        if inspect(pid) != before or executable(pid) != path:
+        if (inspect(pid) != before or executable(pid) != path
+                or stdin_terminal(pid) != input_path):
             return None
         return tty
     except (OSError, ValueError, TypeError, KeyError, ctypes.ArgumentError,