FAQ

Using Marshal

Which agents can I use?

Any agent your admin installs from the marketplace. The catalog includes Claude Code, OpenAI Codex CLI, GitHub Copilot CLI, Cursor CLI, Gemini CLI, Grok, Hermes and opencode. Each one runs in its own space with the tools and credentials its manifest gives it. See the package catalog.

Can the agent see my credentials?

No. You save a credential once, and nobody can read its value after that, including owners and admins. When a tool in your space needs a credential, Marshal injects it into that tool’s process, outside the agent’s reach. For API keys sent over HTTP, the agent sees only a placeholder. Marshal swaps in the real value on the way out, and only for the hosts the package declared. See Credentials and connections.

Does my code leave my cloud?

Marshal runs on your own Kubernetes cluster, so your spaces, your code and your saved credentials stay in your infrastructure. Outbound traffic from a space goes only where your network policy allows, such as your Git host and the model provider your agent uses. Every call that policy allows or blocks is recorded in the audit log.

Running Marshal

What does “the chart version is the product version” mean?

Marshal is made up of several components (api, gateway, web dashboard, marketplace service, and the images used inside each space), and each one has its own version number. On their own, those numbers do not tell you what a Marshal release contains.

The Helm chart acts as a Bill of Materials: its values.yaml pins the exact, tested image for every component in a release. When you install a chart version, you install one specific, known-good combination of every component. One number tells you exactly what is installed, which makes upgrades, rollbacks and support conversations simple.

Can I run multiple instances (for example prod and staging) on one cluster?

Yes. Each instance is its own Helm release in its own namespace, for example marshal-prod and marshal-staging on the same cluster. Each release gets its own space namespace, its own configuration and secrets, and its own resources, so the two instances are fully isolated. Teams use this to rehearse an upgrade in staging before they promote the same chart version to production.

Is Marshal exposed to the internet?

No. By default Marshal is reached over your own private network (VPN, bastion, or equivalent). Your cluster needs no inbound access from the internet. Webhooks from GitHub, Slack and your own systems go to a webhook relay, and your install pulls them from there over an outbound connection.

What outbound access does the cluster need?

Outbound HTTPS to a small set of Marshal endpoints: the image registry (through a pull-through cache that you run in your own environment), license verification, the hourly usage report of counts, and the marketplace catalog. The webhook relay is added only when an admin turns on webhooks in Settings > Platform. Spaces reach other hosts only as your network policy allows. The full list is in Networking and egress.

How do I get support, renew my license, or contact Marshal?

Reach out to your Marshal contact. They handle support, license renewal, onboarding new credentials, and the latest chart version. Keep your onboarding details (deployment ID, license token, registry pull token) at hand, since most support requests start there.