AICHE +Vscode Integration

The short answer: open VS Code, position your cursor in a comment block or README file, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak your documentation or explanation for 30-45 seconds, and AICHE transcribes and inserts the formatted text.

VS Code is where most developers spend their entire workday. Writing code is the fast part. The slow part is everything around the code: the comment explaining why you chose this approach, the docstring documenting parameters and edge cases, the README that onboards new contributors, the commit message in the integrated terminal. These text-heavy tasks get skipped or rushed because switching from code-thinking to prose-typing breaks your flow.

1. Open VS Code with your project.
2. Position cursor where you want text - comment block, markdown file, inline comment, or the Source Control commit message field.
3. Press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux) to start recording.
4. Speak your explanation naturally (example: "this function validates user input by checking email format, verifying domain existence, and rejecting disposable addresses").
5. Press the hotkey again. AICHE transcribes, applies Message Ready formatting, and inserts the text at your cursor.
6. Review for technical accuracy, adjust any specifics, and continue coding.
7. For longer documentation like README sections, speak for 60-90 seconds per section and build the file incrementally.

Heads-up: AICHE transcribes your spoken words into text. If you say "create a function that adds two numbers," it inserts that sentence as text. It does not generate code syntax. Use AICHE for explaining code to humans, not writing code itself.

Inline Comments and Docstrings

Comment Blocks Above Functions

The most common use in VS Code is documenting functions you just wrote. Position your cursor on the line above a function, type your comment prefix (// or /** or #), then press ⌃+⌥+R and explain what the function does.

Speak as if you are explaining the function to a colleague sitting next to you. Describe what it accepts, what it returns, why it exists, and any edge cases. This conversational explanation produces better documentation than the terse notes most developers type, because speaking naturally forces you to include context you would otherwise skip.

After AICHE inserts the text, add language-specific formatting. For JSDoc, wrap with /** and add @param and @returns tags. For Python docstrings, wrap with triple quotes. The content is already there - you are just adding syntax markers.

Inline Explanations for Complex Logic

When you write a tricky algorithm or a workaround for a library bug, add a comment immediately. Position cursor above the line, press the hotkey, and say "this uses a binary search instead of linear scan because the dataset exceeds 10,000 items and response time needs to stay under 50ms." That comment takes 8 seconds to speak and 45 seconds to type. Over a full day of coding, the difference adds up.

README and Markdown Authoring

VS Code's built-in markdown preview (Ctrl+Shift+V or Cmd+Shift+V) pairs well with voice input. Open your README.md, split the editor so the preview is visible on the right, then dictate section by section.

For each section, speak the content naturally: what the project does, how to install it, how to configure it, common pitfalls. Enable Content Organization in AICHE settings to have your spoken explanation automatically structured into clear paragraphs. After dictating, add markdown headers (##), code fences, and links manually.

A README that takes 25 minutes to type from scratch becomes 8 minutes of dictation plus 3 minutes of formatting. More importantly, you actually write it instead of pushing it to next sprint.

Git Commit Messages in the Integrated Terminal

VS Code's integrated terminal (Ctrl+ or Cmd+) is where most VS Code users run git commands. When you type git commit and your editor opens for the message, press ⌃+⌥+R and dictate the full context: what changed, why it changed, and what to watch for during review.

You can also use VS Code's Source Control panel. Click into the commit message field at the top of the Source Control sidebar, press the hotkey, and speak your message. AICHE inserts directly into that field.

Detailed commit messages make git blame useful months later. The reason developers write "fixed bug" is not laziness - it is that typing a proper explanation feels slow when you want to move on. Speaking it takes 15 seconds.

VS Code-Specific Tips

• Extensions stay out of the way. AICHE runs as a separate desktop app, not a VS Code extension. There are no conflicts with Copilot, ESLint, Prettier, or any other extension. Your extension setup stays exactly as it is.
• Multi-cursor still works. If you have multiple cursors active, AICHE inserts text at the primary cursor position. Place your cursor deliberately before recording.
• Remote SSH and WSL. AICHE inserts text into whatever VS Code window has focus, including Remote-SSH and WSL sessions. No server-side installation needed.
• Snippet-friendly. Dictate a comment, then use VS Code snippets to add boilerplate around it. The combination of voice content and snippet structure is fast.

The pro-tip: When documenting complex functions, speak while looking at the code on screen. This produces more accurate descriptions than trying to remember implementation details from memory. Your eyes scan the parameters and return types while your mouth explains the logic.

Result: A comprehensive README that takes 18 minutes to type becomes 5 minutes of dictation. Function docstrings get written immediately instead of being postponed to a cleanup sprint that never happens.

Do this now: Open any code file with an undocumented function, add a comment block above it, press your hotkey, and dictate what the function does and why it exists.