cloud.abridge.services

FAQ

Updated 2026-08-29

Quick answers to the "but what about…" questions. The authoritative technical references live in the holodeck repo (AGENTS.md, service/README.md, docs/design/applicationset-current-design.md) and the holodeck-api-client / holodeck-mcp skills.

How do I open the SOAP dashboard in my slot?

Each slot serves its own SOAP dashboard from its per-service URLs (or the Reservations tab). If it prompts for an access code, use HLDECK42.

Do I have to learn the API?

No. Use the web console (paste a PR, hit Deploy) or point your agent at the holodeck-api-client skill — it handles reserve → deploy → poll → release for you. The raw HTTP API is there when you want scripting or CI control.

Can I deploy through MCP?

Not yet — the MCP path is read-only today (list slots, status, jobs, registry). To deploy or release, use the clone-the-repo + skill path or the web console. Write tools over MCP are tracked in PLA-4263.

My PR deploy failed immediately — why?

Almost always because the PR's container images aren't built yet. Images come from the repo's own CI (pr-<n>-<sha>). Wait for CI to finish, then deploy or change-version to that commit.

Why can't I deploy a single service?

Because of the temporal cohort label: services that share Temporal namespaces must deploy together. Naming one temporal member alone returns a 400 listing the missing members. Use a footprint other than none (or the temporal label), and run plan-preview first if unsure.

How long does a slot live?

Until you release it or its TTL expires. If you don't set a TTL, reservations default to 24 hours. You can extend an active reservation.

What's the difference between footprint and baseline?

Footprint = which services deploy (default notegen, or same-repo). Baseline = where the fill-in services come from (main, stage, or prod). See Footprint & baseline for the mental model.

How do I wire Holodeck into my editor?

Log in to Teleport (tsh login --proxy=abridge.teleport.sh:443), confirm tsh mcp ls lists dev-holo-mcp-teleport, then add one MCP entry that runs tsh mcp connect dev-holo-mcp-teleport. Don't configure the internal HTTP URL or the legacy dev-holo-mcp app.