Skip to content

AgentTCDH v0.1.5

Choose a tag to compare

@github-actions github-actions released this 04 Nov 08:34
· 1 commit to main since this release
7dd36d8

AgentTCDH v0.1.5

Version 0.1.5 bundles the complete local connection import and maintenance flow. Bring existing MCP/A2A declarations into the registry, select them interactively, save a reusable private profile, and maintain their metadata and source changes. The hub continues to return discovery metadata; consumers connect directly.

Preparation, GitHub publication, and npm publication are separate. A source version or verified candidate does not establish that either public destination has been published. Check the destination before installing.

Publication status — 2026-11-04

GitHub and npm v0.1.5 publication completed. Public npm version and latest both report 0.1.5. The public registry SHA-512 integrity and downloaded bytes match the verified GitHub tarball; an independent npm download using an empty cache matched as well. Fresh installed CLI version/help, local import preview, private profile creation/listing, and offline backup listing passed at 2026-11-04T08:42:32.843Z.

Source commit: 7dd36d8e2099d95146afd29be9e50818a08e71dc.

Tarball SHA-256: 5fcf262fee3b4f00209a64e100d696508c036eb9dcb827df69908893aaef00f1.

Validation: 270 local Linux regression tests passed with no failures/skips. All native Linux, macOS ARM64/x64, Windows, and container jobs passed in PR CI, main CI, and the release workflow. Installed-package verification and platform-specific lifecycle checks ran in their applicable native jobs. The downloaded public GitHub bundle separately passed exact-source/checksum/installed-workflow verification before npm publication.

npm install --global agent-tcdh@0.1.5
agent-tcdh registry import-local --interactive --save-profile work

Included workflow

  • Local discovery/import: locate bounded Codex, Claude Code, OpenCode, Gemini CLI, Cursor, and VS Code configuration sources. Preserve origins, show source-qualified keys, coalesce compatible declarations conservatively, and import a selected group atomically. Gemini remote A2A definitions support inline cards; URL-only cards require explicit metadata lookup.
  • Interactive selection: a terminal checkbox list supports arrows, space, select-all, acceptance, and cancellation. No connections are preselected. Automated usage retains explicit --select keys and JSON output.
  • Private import profiles: save pinned source locations, selectors, hub identity, optional credential environment names, and synchronization fingerprints. Reuse a named profile without copying source commands or credential values into the ledger. Offline list/show/removal commands manage the private store.
  • Source synchronization: preview additions, field changes, disappeared declarations, and conflicts. Preserve hub-only edits; conflicting edits to the same field block writes. Existing IDs survive representative-origin changes. Removal requires explicit --prune --apply and an unchanged managed definition.
  • Metadata follow-up: optionally refresh and diagnose imported/synchronized targets with one metadata observation each. Conditional writes preserve labels/state/auth references and no-op revisions. A failed optional phase does not undo successful registration, and acknowledged ownership is checkpointed before follow-up.
  • Registry duplicate cleanup: inspect compatible existing connections, show differing label/capability fields, and explicitly select a representative plus redundant IDs. Fresh versions guard independent removals; different credentials/enabled states are not conflated.
  • Opt-in stdio metadata: explicitly authorize consumer-side process startup to initialize and list tools, with bounded output, pagination, deadline, minimal environment, portable Windows shims, and owned-process teardown. This does not call tools/tasks or turn the hub into an executor.

See local import and import management for supported locations, commands, outputs, and boundaries.

Example flow

Requires Node.js 24 or newer:

agent-tcdh registry import-local --interactive --save-profile work --apply
agent-tcdh registry sync-local --profile work
agent-tcdh registry sync-local --profile work --apply --refresh --diagnose
agent-tcdh registry duplicates

Use --fetch-a2a-cards when selected definitions require a remote card lookup. To authorize local server startup for metadata follow-up, additionally pass --inspect-stdio; use --stdio-cwd when a different consumer working directory is required. These permissions are not saved in the profile.

Installation and publication checks

From the verified source checkout, prepare a new local bundle with the release commands. For directory release/v0.1.5:

npm install --global ./release/v0.1.5/agent-tcdh-0.1.5.tgz
agent-tcdh --version --json

The built CLI tarball, release.json, and SHA256SUMS bind the package bytes to an exact source commit. Preparation does not publish anything.

Check npm before installing from its registry:

npm view agent-tcdh@0.1.5 version

After npm reports 0.1.5, install with npm install --global agent-tcdh@0.1.5 or run npx --yes agent-tcdh@0.1.5 --help. Confirm the GitHub v0.1.5 release exists before downloading its installable assets. Verify its bundle from the tagged checkout, publish those exact tarball bytes to npm, then verify public integrity, latest, and a fresh installation. A committed OIDC workflow does not establish package-side Trusted Publisher authorization.

Compatibility and operational scope

Node.js 24+, SQLite schema version 2, snapshot format version 1, and HTTP/MCP/A2A discovery contracts remain unchanged. Existing registry data, source files, explicit-file import behavior, and default single-target refresh behavior can be reused. New private import-profile storage has its own format version 1 and is machine-local. YAML parsing is supplied by pinned yaml@2.9.1; existing cross-spawn@7.0.6 is now a production dependency for explicit stdio inspection. No provider allowlist, proxy, model planner, or hosted credential service is added.

Profiles use atomic private writes/backups and cooperating operation locks. Limits include 50 profiles and 1 MiB total profile storage, up to 1,000 managed registrations subject to that byte bound, and the existing local scan bounds. Hub and filesystem changes are not a distributed transaction. Initial imports and sync additions use atomic conflict-checked import requests; existing sync changes and duplicate removals have independent conditions/outcomes without automatic rollback or retry. Review state after an unacknowledged request, forced termination, or ledger-write failure. Managed missing IDs are not silently recreated or adopted. Removing a profile does not remove registry entries.

Default previews do not start target processes. Explicit stdio inspection starts executable code with that user's filesystem access and can have program-defined side effects; it is not an OS sandbox. Only initialization/tool listing is requested. Output and lifetime bounds and normal/error/deadline teardown do not guarantee cleanup after forced host termination or escape from the owned process tree. Remote metadata lookup/refresh is also an explicit outbound operation. executionVerified: false distinguishes metadata observation from successful tool/task execution.

Verification scope

Regression coverage exercises source/profile isolation, terminal selection/cancellation, three-way field comparison, conservative pruning, concurrent conditional writes, durable ownership before follow-up, duplicate cleanup, and bounded stdio lifecycle/environment/output behavior. Real PTY checks additionally cover choosing only one connection and cancelling without profile changes.

Installed-package verification uses production dependencies, isolated user/project/profile paths, and local protocol fixtures to run discovery/import, profile persistence, metadata inspection, source synchronization/pruning, duplicate cleanup, persistence/restart, and direct-call examples. Native CI covers Linux x64, macOS ARM64/x64, Windows x64, plus a Linux container. Windows shim inspection and POSIX graceful-interrupt checks are platform-specific; only completed native jobs establish their results. The exact public GitHub bundle is separately verified before npm publication.

Personal AI client settings are not modified by verification. Public providers and real models remain opt-in; this release does not refresh earlier live-provider/model evidence or establish new model executions for every client.