## Summary **Batch B of Phase 3** of the H1 → front-matter migration (`DOCS-484`; parent `DOCS-477`), the editorial follow-up to Batch A (#28030). For the **124** hand-authored pages whose leading body H1 differed from the manifest nav label, this promotes the richer body H1 to the front-matter **page title** and drops the duplicate H1, while keeping the short manifest **label** as the sidebar entry. Policy agreed with the docs owner: - Short sidebar labels win. Duplicate sidebar labels are acceptable. - Identical **page titles** across two pages are not. On a collision, rename the non-generated page's title. ## Page-title collisions resolved Promoting the H1 created 4 page-title collisions; each is disambiguated by renaming the non-generated / secondary page (sidebar labels left unchanged): | page | sidebar label | body H1 | → page title | |------|---------------|---------|--------------| | `install/index.md` | Install | Installing Coder | **Install Coder in your infrastructure** | | `install/cli.md` | Coder CLI | Installing Coder | **Install the Coder CLI** | | `ai-gateway/clients/jetbrains.md` | JetBrains | JetBrains IDEs | **JetBrains** | | `workspace-access/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | Web IDEs *(kept — primary user guide)* | | `extending-templates/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | **Web IDEs in templates** | | `workspace-management.md` | Workspace Management | Workspaces | **Manage workspaces** *(vs generated `api/workspaces.md`)* | These titles are the only non-mechanical editorial calls in this PR. ## Deliberately excluded: generated pages `admin/security/audit-logs.md` and `admin/setup/configuration-reference.md` are `make gen` outputs (`auditdocgen` / `configdocgen`) that Phase 2 did **not** update, so a hand-added title would be reverted on the next generation. They're excluded here and need their generators taught to emit front matter first (Phase 2 pattern), tracked as `DOCS-631`. Batch A (#28030) had the same issue for three other generated pages; it has been corrected there too. ## Verification AI was the primary author of this PR (see disclosure below); per the [AI Contribution Guidelines](https://coder.com/docs/about/contributing/AI_CONTRIBUTING) here is the manual verification. - Promote = set front-matter `title` to the body H1 (or the disambiguated title above) and remove that one duplicate H1. No other body prose is reflowed. - Every added front-matter block parses as YAML; all files pass `pnpm check-docs` (markdownlint-cli2 + table formatter): `Summary: 0 error(s)`. - Removing the H1 orphaned one in-page fragment (`[MCP](#mcp)` in `ai-gateway/mcp.md`), now repointed. A cross-file fragment audit into the retitled pages found no real breakage. Anchor-change note Unlike Batch A (title unchanged, a rendered no-op), Batch B changes each page's effective title from the manifest label to the body H1, so the rendered H1 **anchor slug changes**. An audit of cross-file `.md#fragment` links into these pages surfaced no links that break as a result (the only hits were false positives against a still-present `## TLS & Reverse Proxy` heading). Same-file fragments are enforced by markdownlint MD051, which is green. ## Title casing (follow-up, DOCS-742) A follow-up commit puts the promoted titles into sentence case and removes leading gerunds (for example, `Managing workspace schedules` → `Manage workspace schedules`): 57 of the 120 titles changed, the other 63 were already compliant. Proper nouns and branded names (Coder Validated Architecture, JetBrains, File Browser, Dev Containers, Island), acronyms (API, CLI, IDE, MCP, OIDC, URL, UI, CI/CD), the Premium license tier, and maturity labels (Beta, Experimental) are preserved. The four `Nk-users` pages become `Reference architecture: up to N users` (lowercase, matching the CVA landing page's own usage); the CVA landing page keeps its branded title. `pnpm check-docs`: `Summary: 0 error(s)`. Linear: DOCS-484, DOCS-742 > This PR was created with AI assistance (Coder Agents).
11 KiB
title
| title |
|---|
| Generate and upload a support bundle to Coder Support |
When you engage with Coder support to diagnose an issue with your deployment, you may be asked to generate and upload a "Support Bundle" for offline analysis. This document explains the contents of a support bundle and the steps to submit a support bundle to Coder staff.
What is a Support Bundle?
A support bundle is an archive containing a snapshot of information about your Coder deployment.
It contains information about the workspace, the template it uses, running agents in the workspace, and other detailed information useful for troubleshooting.
It is primarily intended for troubleshooting connectivity issues to workspaces, but can be useful for diagnosing other issues as well.
While we attempt to redact sensitive information from support bundles, they may contain information deemed sensitive by your organization and should be treated as such.
A brief overview of all files contained in the bundle is provided below:
Note
Detailed descriptions of all the information available in the bundle is out of scope, as support bundles are primarily intended for internal use.
| Filename | Description |
|---|---|
agent/agent.json |
The agent used to connect to the workspace with environment variables stripped. |
agent/agent_magicsock.html |
The contents of the HTTP debug endpoint of the agent's Tailscale Wireguard connection. |
agent/client_magicsock.html |
The contents of the HTTP debug endpoint of the client's Tailscale Wireguard connection. |
agent/listening_ports.json |
The listening ports detected by the selected agent running in the workspace. |
agent/logs.txt |
Active agent log plus rotated agent logs modified in the last 24 hours, capped at 100 MiB. |
agent/workspace_files/collection_errors.txt |
Workspace file entries dropped while assembling the bundle, such as entries exceeding the size budget. Only present when entries were dropped. |
agent/workspace_files/files/ |
Files collected from inside the remote workspace with --workspace-file. Only present when workspace paths are requested. |
agent/workspace_files/manifest.json |
Describes the remote workspace file collection: requested patterns, collected files, per-path errors, truncation, and applied limits. Only present when workspace paths are requested. |
agent/manifest.json |
The manifest of the selected agent with environment variables stripped. |
agent/startup_logs.txt |
Startup logs of the workspace agent. |
agent/prometheus.txt |
The contents of the agent's Prometheus endpoint. |
cli_logs.txt |
Logs from running the coder support bundle command. |
deployment/buildinfo.json |
Coder version and build information. |
deployment/config.json |
Deployment configuration, with secret values removed. Requires Owner role. |
deployment/experiments.json |
Any experiments currently enabled for the deployment. |
deployment/health.json |
A snapshot of the health status of the deployment. Requires Owner role. |
logs.txt |
Logs from the codersdk.Client used to generate the bundle. |
network/connection_info.json |
Information used by workspace agents used to connect to Coder (DERP map etc.) |
network/coordinator_debug.html |
Peers currently connected to each Coder instance and the tunnels established between peers. Requires Owner role. |
network/netcheck.json |
Results of running coder netcheck locally. |
network/tailnet_debug.html |
Tailnet coordinators, their heartbeat ages, connected peers, and tunnels. Requires Owner role. |
workspace/build_logs.txt |
Build logs of the selected workspace. |
workspace/workspace.json |
Details of the selected workspace. |
workspace/parameters.json |
Build parameters of the selected workspace. |
workspace/template.json |
The template currently in use by the selected workspace. |
workspace/template_file.zip |
The source code of the template currently in use by the selected workspace. |
workspace/template_version.json |
The template version currently in use by the selected workspace. |
vscode-logs/ |
Only present when generated from the VS Code Coder Remote extension. Includes logs, redacted settings, and local telemetry files. |
How do I generate a Support Bundle?
-
Ensure your deployment is up and running. Generating a support bundle requires the Coder deployment to be available.
-
Ensure you have the Coder CLI installed on a local machine. See installation for steps on how to do this.
Note
It is recommended to generate a support bundle from a location experiencing workspace connectivity issues.
-
Ensure you are logged in to your Coder deployment. Any authenticated user can generate a support bundle. Users with the Owner role will get the most complete bundle; non-admin users will still get a useful bundle but some admin-only data will be omitted (see the note below).
-
Run
coder support bundle [owner/workspace], and respondyesto the prompt. The support bundle will be generated in the current directory with the filenamecoder-support-$TIMESTAMP.zip.If you use VS Code, you can also run Coder: Create Support Bundle from the Command Palette. The VS Code Coder Remote extension runs
coder support bundleand appends recent VS Code diagnostics to the generated archive. Bundles created with the CLI alone do not includevscode-logs/. Learn more about VS Code diagnostics.Note
While support bundles can be generated without a running workspace, it is recommended to specify one to maximize troubleshooting information.
To collect workspace-side files such as editor or service logs, add one
--workspace-fileflag for each path or glob. This is explicit opt-in. The CLI sends each value to the workspace agent, so quote globs to prevent your local shell from expanding them:coder support bundle my-workspace \ --workspace-file '$HOME/.vscode-server/data/logs/**/*.log' \ --workspace-file '$HOME/.local/share/code-server/coder-logs/**/*.log'Workspace paths and globs are evaluated by the workspace agent. Environment variables such as
$HOMEexpand in the workspace, and~/resolves against the agent user's home directory; any absolute path in the workspace can be requested. Symlinks are followed for directly requested paths, but not during glob traversal. Collection is limited to 10000 files and 100 MiB in total; files larger than 10 MiB are truncated to their last 10 MiB and marked as truncated in the manifest. Collected files are stored underagent/workspace_files/files/, and collection metadata is stored inagent/workspace_files/manifest.json.Warning
Workspace files can contain tokens, credentials, source code, or other sensitive data. Extract and review
agent/workspace_files/before sharing the bundle. -
(Recommended) Extract the support bundle and review its contents, redacting any information you deem necessary.
-
Coder staff will provide you a link where you can upload the bundle along with any other necessary supporting files.
Note
It is helpful to leave an informative message regarding the nature of supporting files.
Coder support will then review the information you provided and respond to you with next steps.