SupaKeeper Plain comparisons of AI coding tools

How to save diagnostic command snippets for technical support specialists in 2026

Learn how technical support specialists can save diagnostic command snippets, what to prepare first, and which tools can store and reuse them.

By SupaKeeper ยท

SupaKeeper is published by LunarWerx, the makers of AgentHydra, Copilot AI Productivity Suite, Codex Forecast and Model Odds, which are compared here alongside other tools.

To save diagnostic command snippets, first list the commands you run most often, write each one with a short clear name, and then pick a place where your whole support team can find and insert them during a call. Checking how that place handles sharing and updates matters as much as the saving itself.

OptionWhat it doesWhat to check
Copilot AI Productivity SuiteInserts a saved snippet into Copilot Chat with a short command. [1]Check that your editor is VS Code 1.116.0 or newer. [1]
A shared notes or wiki pageKeeps commands on a page your team can open and edit.Check whether you can add a note for normal results and mark commands that change settings.
A plain text file in a shared folderKeeps commands as text that anyone with folder access can copy.Check who can change the file and how updates are tracked.

What you need before you start

Before you save anything, gather the diagnostic commands you run most often and write each one exactly as you type it, including any flags or file paths. Note which operating system, device type or customer setup each command is meant for, so that a saved command is not run on the wrong machine during a call.

Decide who needs access. A snippet that only you can open is different from one your support team shares, and that choice affects how you name and organize the commands. Think about whether the commands will be used inside an editor, in a chat window or in a plain text file, because that decides which tools will fit your day.

Have a short naming plan ready. Names such as check disk space on Windows are easier to find under pressure than names such as cmd 3. Keep a clear mark on any command that changes a setting or restarts a service, since those need to be easy to spot before they are saved.

Check your tools too. Confirm which editor or support software you use daily, whether your machine allows installed extensions, and whether your team has rules about storing commands. Those rules often decide the choice more than any feature does.

Step by step

  1. Collect the commands you use most often for diagnosis, such as checks for network, disk, memory or service status, and write each one exactly as it runs.
  2. Give every command a plain name that says what it checks and when to use it.
  3. Add a short note under each command describing what a normal result looks like and what a problem result looks like.
  4. Mark any command that changes a setting or restarts a service, so that nobody runs it by accident.
  5. Group related commands together, for example all network checks in one place, so the list stays easy to scan.
  6. Save each group in the place your team can open, and run each command on a machine you control before using it on a live call.
  7. Set a simple habit for updates. When a command changes, edit the saved version the same day and tell the team what changed.
  8. Review the list regularly, and remove any command that no longer matches the systems you support.

Tools that can do it

Copilot AI Productivity Suite is made by the team that publishes this site.

It is a VS Code extension that needs VS Code 1.116.0 or newer, and it is also on Open VSX for Cursor, Windsurf and VSCodium. [1] You install it from the VS Code Marketplace. [1]

Typing #copilotsuite /snippet_id inserts the exact saved snippet template into the conversation. [1] Placeholders like ${name} or ${name:default} in a snippet ask you for a value when the snippet is inserted. [1] Snippets can sit in folders inside folders, and you can bundle several into a group that is referenced all at once. [1]

You can pin up to five favorite snippets to the VS Code status bar. [1] You can select several snippets and move them, delete them or insert all their references at once. [1] You can export snippets as JSON or make a share link, and teammates can import it. [1]

A bundled local helper, called an MCP server, makes your snippets available to Claude Code, Codex CLI and other tools that connect to it. [1] If you turn on slash command export, each snippet is written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as you edit. [1]

Other approaches include a shared notes page, a team wiki, or a plain text file kept with your support documents. Each can hold commands, but check whether it lets you insert a command in one step, whether it keeps names and notes together, and who can edit it. Compare each option against the exact job of saving diagnostic commands for a support call.

Common mistakes to avoid

Avoid saving commands without a note on what a normal result looks like. A saved command is only part of a diagnostic step, and a short note makes it useful to the next specialist who opens it.

Avoid vague names. A list is harder to use when a name does not say what the command checks.

Avoid storing passwords, keys or customer details inside a snippet. Commands are easy to share, so anything secret in the text can spread further than intended.

Avoid storing commands that change settings without a clear mark. These should be easy to spot before anyone runs them.

Avoid assuming that every tool handles sharing and updates the same way. Check who can see and change the saved commands before the team relies on them.

Frequently asked questions

How do technical support specialists save diagnostic command snippets?

Start by listing the commands you run most often, writing each one exactly as it runs, and giving it a plain name and a short note about normal results. Then choose a place your team can open, such as an editor extension, a shared page or a text file, and check that it keeps names, notes and sharing together. Review the list regularly so it matches the systems you support.

Can Copilot AI Productivity Suite insert saved commands into Copilot Chat?

Typing #copilotsuite /snippet_id inserts the exact saved snippet template into the conversation. [1] Placeholders such as ${name} ask you for a value when the snippet is inserted. [1] Before a live call, check that the command you need is saved in the form you expect, so the inserted text matches what you meant to run.

Does Copilot AI Productivity Suite keep snippets in sync across machines?

If you sign in with an account, which uses an emailed one-time code, your snippets, groups and settings sync across your machines. [1] Before you rely on sync for shared work, check how your team wants to handle who sees each snippet. You can also export snippets as JSON or make a share link, and teammates can import it. [1]

Does Copilot AI Productivity Suite send usage data?

While VS Code telemetry is on, it sends anonymous usage statistics, but never snippet content. [1] Whether usage statistics are sent therefore depends on whether VS Code telemetry is on for each machine. The commands you save are not part of what is sent, so you can decide on telemetry separately from your snippet library.

Is Copilot AI Productivity Suite free to use?

There is a Free plan at $0 that allows 20 Copilot insertions a week. [1] Premium costs $6.99 a month and has unlimited Copilot insertions. [1] Choose the plan that matches how often your team inserts snippets in a typical week, and check the current prices on the extension listing before you sign up.

There is a Free plan at $0 that allows 20 Copilot insertions a week. [1]

Try Copilot AI Productivity Suite

Sources

  1. Copilot AI Productivity Suite's own description of itself (the product of this site's publisher)

Related comparisons