Repository navigation
AgentTCDH v0.1.3
AgentTCDH v0.1.3
GitHub and npm publication are complete. Install with npm install --global agent-tcdh@0.1.3 or run npx --yes agent-tcdh@0.1.3 --help.
Release source: 92d04d121e19c4f4fb3d4d4ec863fe6bf03d9811. Tarball SHA-256: 26e57f98547251049a7c3624703c405e07a07cbacd64c90b1065f67f0cb85c3d.
Publication verification checked npm version/latest, SHA-512 integrity, exact downloaded bytes against the GitHub tarball, execution from a fresh npm cache, and the installed backup-listing command. Native Linux, macOS ARM64/x64, Windows x64, and container CI passed; the Linux regression suite has 217 passing tests.
Version 0.1.3 adds local client connection checks, disconnection, backup discovery, and whole-file recovery. The commands work with the seven existing client profiles and preserve the discovery/direct-execution architecture.
Release preparation is separate from publication. Source metadata and candidate verification do not establish that npm or GitHub publication has completed. Confirm the requested destination before installing from it.
Included changes
connect CLIENT --check FILE: compare a saved named entry with this installation's generated profile. Report missing or differing settings without writes, network calls, or source values in output. Matches exit 0; missing/mismatched profiles exit 1.disconnect CLIENT --file FILE: preview named-entry removal. Explicit--applysaves an exact backup before replacement. Missing files/entries are successful no-ops. Codex managed blocks preserve surrounding text; other TOML layouts require an explicit--normalizechoice.config backups --file FILE: list matching sibling backup metadata by modification time, with a bounded scan, per-entry status, and installation-specific restore preview commands. Backup contents are not opened or validated during listing.config restore BACKUP_FILE --file FILE: preview whole-file recovery. Explicit--applyrestores the selected text and backs up an existing destination. Identical content is a no-op; a missing destination is created only on apply.
See connection checks, disconnection, backup discovery, and restoration for options, result codes, and scope.
Install a prepared candidate
Requires Node.js 24 or newer. From the verified release source checkout, prepare and verify a new local bundle as described in the release process. For output directory release/v0.1.3:
npm install --global ./release/v0.1.3/agent-tcdh-0.1.3.tgz
agent-tcdh --helpThe bundle contains the built CLI tarball, release.json, and SHA256SUMS, bound to the exact source commit. Preparation does not create a tag, publish a GitHub release, or publish to npm.
Published artifacts
Check npm availability before using the new version:
npm view agent-tcdh@0.1.3 versionAfter npm reports 0.1.3, install with npm install --global agent-tcdh@0.1.3 or run npx --yes agent-tcdh@0.1.3 --help. Existing hub configuration and registry storage can be reused.
Confirm that the GitHub v0.1.3 release exists before downloading its built tarball, manifest, and checksums. Verify the exact release bundle from the tagged source checkout. GitHub and npm publication are separate; publish the same verified tarball and verify its public registry integrity and latest tag afterwards. A configured workflow does not establish package-side npm trusted-publisher authorization.
Compatibility and verification scope
The minimum Node.js version remains 24, SQLite schema remains version 2, and portable snapshots remain format version 1. HTTP/MCP/A2A contracts and existing registrations are unchanged. No dependency changes or database migration are needed.
A connection check verifies generated settings, not client loading or successful authentication/execution. Disconnection selects the complete named entry, including custom settings, without inferring ownership. Restoration replaces the entire selected UTF-8 file, including unrelated settings, and does not validate backup provenance or client-specific syntax. Backup discovery uses names and filesystem metadata, not validated content or immutable creation history. Reload clients after applying configuration changes.
Local and native CI use isolated configuration files and local protocol fixtures. The matrix covers Linux x64, macOS ARM64/x64, Windows x64, and an independent Linux container. Package verification exercises configuration checks, disconnection, backup discovery, whole-file restoration, direct-call examples, and restart persistence. The exact release bundle is separately verified before publication.
Earlier live provider and model evidence retains its original dates and scope. This release does not establish new model-driven executions for each supported client. External calls and real model runs remain opt-in. The hub continues to return connection metadata; consumers own target selection, credentials, protocol support, permissions, and execution.