tabc 0.2.4

Changes

• Add tabc send --id <UUID> for retries using a caller-saved message ID. After normal send checks pass, an identical request is not stored twice. Changed content or recipients produce a conflict.
• Keep the existing behavior when --id is omitted: each send receives a new random ID. The local MCP adapter already supports message_id; this release adds the CLI option.
• Link the PyPI introduction to the GitHub changelog, published releases, and upgrade instructions.
• Make the process-argument test wait briefly for a newly started child process. Product validation remains unchanged.

Upgrade

See Upgrading from 0.2.3 to 0.2.4.

The new CLI option works with an existing 0.2.3 daemon. This feature does not require a ledger conversion or node re-registration. Follow the documented backup and stop/install/restart procedure when replacing the complete running installation.

Duplicate-storage prevention is not a read receipt or a guarantee that a task ran once. Preserve the ID and complete message inputs before the first attempt. Read-before-send and other normal send checks still apply.

tabc 0.2.3

The CLI can now resolve an exact open TAC name to its UUID. Canonical lowercase UUIDs still work without a lookup.

• Case-folded exact names resolve; partial, missing, or closed names do not run the requested operation. The CLI lists candidates and returns TAC_NAME_UNRESOLVED (exit 2).
• The server and MCP adapter still require UUIDs. No ledger conversion or node re-registration is needed.
• Upgrade both the CLI and tabd. Restart tabd for name lookup; before that, UUID operations continue to work. The notifier and MCP implementation are unchanged.

Upgrade: python -m pip install --upgrade "tabc==0.2.3" (or "tabc[mcp]==0.2.3" for the optional MCP adapter).

See CHANGELOG.md and the README upgrade section for the stop/install/restart sequence. Verified with clean wheel/sdist installations, multilingual name checks, old-server compatibility, and real MCP stdio calls.

tabc 0.2.2

Changes

• register --kind is case-insensitive and stores the kind in lowercase.
• A detached command can capture an iTerm2 or tmux route through its immediate session-boundary parent without a recognized agent product. The parent must have the same OS user, own the terminal foreground process group, and read standard input from that terminal. Process state, executable path, and standard input are rechecked.
• Codex queue rules are otherwise unchanged. --kind Codex --auto-enter on now selects the same queue route as lowercase codex, when its existing environment checks pass.

Upgrade from 0.2.1

The ledger schema is unchanged. Nodes, keys, messages, delivery states, TACs, routes, and queue receipts are kept. Stop the notifier, install 0.2.2, restart tabd, then start one matching notifier. Restart the local MCP process from its desktop client if used. Register again from the intended terminal and verify one notification.

python -m pip install --upgrade 'tabc==0.2.2'
# Optional local MCP adapter:
python -m pip install --upgrade 'tabc[mcp]==0.2.2'

The route check proves terminal ownership, not agent identity. Automatic Enter remains opt-in. No dedicated adapter for another agent product is added. MCP still does not wake an agent.

See CHANGELOG and terminal-routing notes.

Validated: independent three-reviewer approval, CI, isolated wheel/sdist CLI tests, real MCP stdio tests, and a reported macOS OpenCode/iTerm2 registration and notification check. Other terminal hosts were not validated as real integrations in this release.

PyPI: https://pypi.org/project/tabc/0.2.2/

tabc 0.2.1

Codex CLI queue notifications are available in 0.2.1.

• Registration now requires --kind.
• With --kind codex --auto-enter on, supported native Codex managed-daemon conversations can select queue notifications automatically. --codex-queue requires that route without terminal fallback.
• Notifications carry metadata, not message bodies. QUEUED is not READ or task completion. The local MCP adapter remains separate and does not wake desktop agents.
• Update the CLI and notifier together, keep one notifier, and register again from each intended Codex conversation. Existing messages and keys are preserved; the message schema is unchanged.
• The supported notification path was checked with codex-cli 0.162.1 on macOS. Other versions and desktop hosts are not covered by that check.

PyPI: https://pypi.org/project/tabc/0.2.1/
Full upgrade notes: https://github.com/jultabc/tabc/blob/v0.2.1/CHANGELOG.md