molthostctl

CLI delivery now rides the same Vercel app as the product.

The CLI is not implemented yet, but the public distribution surface is now fixed in place on https://molt.host. That means the install URL, release manifest, and agent guidance pack no longer depend on a second app or ad-hoc hosting.

What is live now

Release manifest

Machine-readable release status, installer URL, and agent-guidance links.

https://molt.host/.well-known/molthostctl.json

Installer script

Stable shell entrypoint. It fails closed until the first CLI binary is published.

https://molt.host/install/molthostctl.sh

Agent skill

Agent-facing workflow invariants that will ship beside the CLI.

https://molt.host/molthostctl/SKILL.md

Agent context

Shared context for humans and agents consuming the hosted CLI surface.

https://molt.host/molthostctl/CONTEXT.md

Current behavior

The installer fails closed with a clear “not published yet” message.
The manifest is machine-readable and already points at the stable URLs.
The guidance pack ships from the same deployment, so future agent automation does not need a second docs host.

Next step

When molthostctl exists, publish the first release by swapping the manifest from status=planned to a versioned release payload and updating the installer to fetch the real artifact. The URL contract stays unchanged.