AICHE +

V

Vscode Insiders Integration

The short answer: open VS Code Insiders, position cursor in a comment block or README file, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak your documentation, and AICHE inserts formatted text. It works identically to stable VS Code - your voice workflow stays consistent even as the editor changes daily.

If you run VS Code Insiders, you are the kind of developer who installs nightly builds to test features before they ship. You are already comfortable with experimental tooling and willing to deal with the occasional rough edge for early access. AICHE fits right into that mindset. It is another tool that gives you an advantage, and unlike Insiders features, it does not break overnight.

The specific friction for Insiders users: you test new features constantly, find bugs, have opinions about preview APIs, and need to communicate all of that. Filing good Insiders bug reports, documenting preview feature behavior, and writing feedback takes real effort. Voice makes that effort smaller.

1. Open VS Code Insiders (the green icon, not the blue one).
2. Position cursor in a comment block, markdown file, issue template, or the Source Control commit message field.
3. Press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux) to start recording.
4. Speak your documentation, observation, or explanation naturally.
5. Press the hotkey again. AICHE transcribes and inserts the text.
6. Review, adjust technical specifics, and continue working.
7. For longer content like bug reports or feature feedback, speak in sections of 30-60 seconds each.

Heads-up: VS Code Insiders updates daily. AICHE is a separate desktop app, not an extension, so Insiders updates never affect your voice input workflow. No re-installation, no compatibility checks, no waiting for extension updates to catch up with API changes.

Testing New Features with Voice Documentation

Capturing Observations While Testing

When a new Insiders build ships a preview feature (new debugger UI, updated terminal renderer, experimental Copilot integration), you often want to note what works, what does not, and what feels different. Rather than switching to a separate notes app, open a markdown file in your project or workspace, press ⌃+⌥+R, and speak your observations while the feature is in front of you.

This produces better feedback than writing notes after the fact. You describe exactly what you see, in the moment, while your reaction is fresh. If you spot a bug in a new inline diff view, dictate the reproduction steps immediately instead of hoping you will remember them later.

AI Feature Testing Notes

Insiders gets new Copilot and AI features before stable. These features often behave differently depending on context, language, and project size. When you are evaluating how well a new AI feature works, dictate your findings: what prompts produced good results, what failed, and where the feature felt slow or inaccurate. These notes become useful reference material when the feature eventually reaches stable and your team asks whether to adopt it.

Filing Insiders Bug Reports

Good bug reports need reproduction steps, expected behavior, actual behavior, environment details, and context. That is a lot of typing. Most developers file sparse reports because the effort does not feel worth it.

With AICHE, click into the GitHub issue template (VS Code's built-in "Report Issue" or the vscode repo issue form), press your hotkey, and speak through the entire report: what you were doing, what went wrong, what you expected, what build version you are on, and whether you can reproduce it consistently. Enable Content Organization in AICHE settings, and your spoken walkthrough gets structured into clear paragraphs.

A bug report that takes 10 minutes to type becomes 3 minutes of speaking. You file more reports, with better detail, and the VS Code team gets the information they need to fix things faster.

Working Alongside Experimental Extensions

Extension Compatibility

Insiders users often run pre-release extensions alongside pre-release editor features. AICHE does not interact with the VS Code extension system at all. It runs as a standalone desktop app that inserts text wherever your cursor is. This means zero conflicts with experimental extensions, pre-release language servers, or proposed API features.

Copilot and Voice Together

When Insiders ships a new Copilot feature (inline chat, multi-file editing, new model options), you are still writing the prompts, comments, and documentation that surround AI-generated code. AICHE handles the human-written text. Copilot handles the code suggestions. They occupy different parts of the workflow and do not overlap.

Insiders-Specific Tips

• Separate settings sync. VS Code Insiders uses its own settings profile. AICHE does not depend on VS Code settings at all, so your voice workflow is identical across both Insiders and stable installs.
• Daily builds, stable voice. When an Insiders update changes keyboard shortcuts or breaks an extension, AICHE's hotkey still works because it registers at the OS level, not through VS Code.
• Side-by-side with stable. Many developers run both Insiders and stable. AICHE works in whichever window has focus. No configuration changes needed when switching between them.

The pro-tip: Keep a TESTING.md file in your workspace. Each time you open Insiders, dictate a quick entry: the date, the build number, what you tested, and what you found. Over weeks, this becomes a personal changelog of your Insiders experience that is genuinely useful when previewed features hit stable.

Result: Better bug reports, more thorough feature testing notes, and documentation that stays current even when you are focused on evaluating bleeding-edge features. The friction between "I noticed something" and "I wrote it down" drops to nearly nothing.

Do this now: Open VS Code Insiders, create a TESTING.md file, press ⌃+⌥+R, and dictate your observations about whatever new feature shipped in today's build.