Skip to content
Klyro Docs

Limitations

These limits define the v0.1 product boundary, not promises about future versions.

Supported scope

Section titled “Supported scope”
  • Hermes is the supported runtime.
  • Hermes built-in memory and Mnemosyne are the supported memory choices.
  • Telegram and the Hermes WebUI are the supported interfaces.
  • OpenRouter is the supported model-configuration provider.
  • Docker Compose is the supported renderer and execution format.

Adding another runtime, interface, memory system, or renderer requires a catalog/profile contract, compatibility fixtures, generated-output review, and a documentation update.

Operational limits

Section titled “Operational limits”
  • validate, plan, and generate do not call model providers, require a Klyro account, or require Docker to be running. The first start of a stack selecting Mnemosyne can download its pinned packages, so it needs outbound network access.
  • Klyro does not manage live secrets or provide a vault. It emits environment-variable names; you supply values through your normal secret workflow (see Secrets handling).
  • The generated project is standard Compose: not a Klyro daemon, hosted control plane, Kubernetes operator, or cloud deployment API.
  • There is no klyro up command and no web configurator in v0.1.
  • Provider support is curated and versioned. Basic validation does not probe arbitrary upstream APIs and cannot guarantee compatibility for unlisted provider versions.

File and regeneration limits

Section titled “File and regeneration limits”

Generation never deletes unrelated files:

  • Managed artifacts carry a Klyro marker and can be refreshed with --overwrite-owned.
  • The canonical klyro.yaml source is intentionally user-owned; replacing a differing copy requires an explicit --force policy.
  • Exact byte matches are skipped.
  • Failed planning or rendering happens before any write, so a failed run leaves no partial project.

The overwrite policies are specified under Commands.

Non-goals

Section titled “Non-goals”

Klyro v0.x is deliberately not an agent runtime, scheduler, long-running daemon, container control plane, Docker dashboard, generic Compose editor, model gateway, secret vault, workflow engine, observability platform, Kubernetes operator, or a hosted dependency required by generated stacks.

Deferred beyond v0.1: a web configurator, an MCP interface, a plugin runtime for third-party executable code, remote catalog updates, standalone native executables, and automatic migration of arbitrary hand-edited Compose files. A useful rule of thumb: if Klyro must remain running after your stack starts, the feature is out of scope.