Skip to content

AgentTCDH v0.1.2

Choose a tag to compare

@github-actions github-actions released this 29 Oct 15:37
· 16 commits to main since this release
9ba05bf

AgentTCDH v0.1.2

Available on npm as agent-tcdh@0.1.2, with latest pointing to 0.1.2.

npm install --global agent-tcdh@0.1.2
agent-tcdh init
agent-tcdh serve

For a hub without global installation, use npx --yes agent-tcdh@0.1.2 serve. Requires Node.js 24 or newer.

What is included

  • init: interactive or automated local/remote setup with reusable defaults and credential variable references.
  • Quick registration: inspect remote MCP/A2A metadata or record a stdio command without executing it.
  • connect: Codex, OpenCode v1/v2, Claude Code, Gemini CLI, Cursor, and VS Code profiles with preview, explicit file merging, and backups.
  • registry import-config and preset: offline-first conversion/selection and explicit atomic registration.
  • doctor and doctor --all: hub access, consumer prerequisites, metadata drift, bounded concurrency, and per-target versions.
  • target edit, enable, and disable: file-free management with conditional writes and idempotent no-ops. target remove --dry-run reviews a registration before guarded deletion.
  • registry diff and import/preset --compare: read-only differences, retained registrations, and existing import-policy effects.

See guided setup, client connections, imports/presets, management, and comparison for examples.

Verified assets

GitHub and npm contain the same verified tarball bytes. Public registry integrity and a fresh-cache CLI installation were checked after publication.

  • Source commit: 9ba05bf61abcc00b1cf7a3bfcf48e70a74b1594d.
  • Package SHA-256: 149d1c40c2fc17abdd3291cdff8f6934d1b7ef5c8b456322c6f8d3d119207e05.
  • Assets: agent-tcdh-0.1.2.tgz, release.json, and SHA256SUMS.
  • Release workflow: all native-platform, container, and exact-artifact checks passed.

Compatibility and verification scope

The minimum Node.js version remains 24. SQLite schema version 2, portable snapshot format version 1, HTTP/MCP/A2A contracts, and existing registration data remain compatible. Original full-definition update and deletion commands retain their existing behavior. Invalid UTF-8 snapshot files are now rejected rather than silently replacing malformed bytes.

Native CI covers Linux x64, macOS ARM64/x64, and Windows x64 with regression and isolated production-package checks; independent container CI verifies the Linux runtime and persistence. Release preparation verifies the exact candidate tarball, its manifest/checksums, installed CLI, discovery protocols, management/comparison workflows, and restart persistence.

Client profiles are verified as generated configuration and actual bridge invocations through the MCP SDK. These checks do not establish new native model executions for every client. Earlier public-provider and real-agent evidence retains its original dates and scope; external calls and model runs remain opt-in.

The hub continues to supply metadata. Consumer-side protocol support, selection, credentials, permissions, and execution remain necessary. Registry comparisons are advisory paginated observations; actual imports retain their own conflict transaction and replacement semantics. Disabling a registration changes default discovery visibility and does not revoke provider permissions or cancel existing work.