> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/visdom-orchestrator/user-guide/known-limitations.md). # Known limitations This page is here so that nothing on it is a surprise. It is taken from the repository's own feature tour, which is explicit about what it does not cover, plus the caveats scattered through the runbooks. It reflects the repository as read on **4 September 2026** and will drift. ## Shipped but partial * **The flow editor is read-only.** The UI renders the graph with per-kind node colours and no Save. Flows are edited through the API or installed from a template. In a product whose core promise is declarative flows, this is the gap that shows fastest. * **Egress enforcement cannot be exercised without a cluster.** The resolver is unit-tested; the enforcement point is a real pod making a real call. On a laptop, egress policy is a screen rather than a behaviour you can observe. * **Classifiers only see what the runtime reports.** The PII detector runs over model output when the runtime hands it over. It is not network-level inspection of everything the agent did. ## Not built yet * **First-party adapters**: Slack, SMTP, GitHub, GitLab, Jira. The generic outbound webhook works; everything past it is integration work. * **Chat as a running thing**: the chat agent runtime image, the in-flow chat node and the output MCP are missing. Sessions and messages persist; nothing holds the conversation. * **The ask-user MCP server bundled with the runtime.** The questions layer exists on the platform side. * **Cost-cap notification and an explicit retry state machine**: the quota gate blocks, but the surrounding notification and retry transitions are unfinished. * **Async memory imports**, **catalog version deprecation**, **bulk catalog import and export**, and the **memory-injector image build pipeline**. * **Helm polish**: HPA and ingress refinements. ## What works end to end today A flow triggered manually or by webhook, agents running as pods with real output, an approval that stops the graph, a shared workspace passing artefacts between agents, a cost rollup, and a hash-chained audit log. ## Traps that look like bugs * A stopped and restarted local cluster breaks the registry wiring; every run then fails on image pull. * A run that already failed on an image pull stays failed after the fix. Trigger a new one. * The Memory tab is empty when the controller runs on a host rather than in the cluster: it is reading the wrong filesystem. * An agent blocked on an outbound call is almost never the workspace egress policy; it is the agent's own allow-list column, which the catalog manifest does not set. * A catalog that fails to load after a manifest edit needs re-signing, not debugging. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.visdom.virtuslab.com/visdom-orchestrator/user-guide/known-limitations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.