1 - Get Started with AI in Visual Studio Code
For some technical writers, using AI means opening a standalone chat window, copying content into it, asking for suggestions, and then pasting the results back into their documentation source files. While that workflow is useful, it only scratches the surface of what is possible.
Instead of treating AI as a separate application, you can make it part of your documentation workflow. This post is intended for technical writers who use Git to manage HTML, DITA, or Markdown documentation, especially those working in Visual Studio Code (VS Code) as their integrated development environment (IDE). These concepts may also apply to other IDEs.
AI assistants such as Claude Code, GitHub Copilot, and OpenAI Codex integrate directly into VS Code and other IDEs, allowing you to work alongside AI without leaving your editor. You can use these tools to build shared automations that improve documentation quality, consistency, and efficiency. GitHub Copilot integrates most naturally with VS Code’s built-in capabilities, but the other AI assistants are also worth exploring within VS Code.
Documentation engineering
The role of the technical writer is shifting. We are no longer just creating documentation; we are building solutions that generate content automatically. Technical writers are increasingly combining traditional writing skills with lightweight automation, prompt design, scripting, and AI workflows to improve content quality and consistency.
If you’re not using AI assistants, you’re missing an opportunity. The good news is that you can get up to speed quickly. You do not need to become a software engineer to benefit from them. A basic understanding of Visual Studio Code and AI assistant extensions can improve your productivity by helping you automate repetitive tasks, focus on broader content strategy, and add your own voice to the content.
Configure Visual Studio Code for AI
To get started, install one or more AI assistant extensions in Visual Studio Code. Your company may already have a preferred AI vendor, but if not, GitHub Copilot may be the easiest place to start because it integrates seamlessly with Visual Studio Code. You can also experiment with the Claude Code or OpenAI Codex extensions within VS Code.
GitHub Copilot is available as a free extension from the Visual Studio Code Marketplace. If your GitHub account includes free or paid Copilot access, you can start experimenting immediately. After installing the extension, open the chat panel by selecting the speech bubble icon at the top of the Visual Studio Code window. GitHub Copilot allows you to choose your large language model (LLM). The paid plan gives you access to more models.
If you have a Claude or OpenAI account, even on the free tier, you can install the corresponding Visual Studio Code extensions at no additional cost. After installation, sign in with your account. You can then open the AI assistant panel by selecting the Claude Code or Codex icon in the upper-right corner of the Visual Studio Code window.
Regardless of which AI assistant you choose, it appears as a sidebar alongside your editor, allowing you to interact with it while working on your documentation. You can enter prompts, ask for suggestions, allow the AI assistant to edit files directly, and accept or reject edits without leaving Visual Studio Code. Each AI assistant provides options near the chat box that control whether it can edit files directly, as follows:
- In GitHub Copilot Chat, the Agents menu lets you choose between Agent, Ask, or Plan modes. Agent mode gives GitHub Copilot permission to edit your files directly. A separate permissions menu lets you choose whether to approve each attempt to run scripts or bypass approvals.
- In Claude Code, the Modes menu below the chat box includes options ranging from Manual to Auto. Each option is described in the menu itself.
- In Codex, the Approvals menu below the chat box includes options ranging from Ask for approval to Full access.
After you configure how your AI assistant can interact with your files, the next step is to teach it how your documentation should be written. You can do this by giving the assistant access to your style guide and creating reusable workflows that improve quality, consistency, and efficiency.
See the next post in this series, editing with AI in Visual Studio Code, for more information on how to give your AI assistant instructions and reusable workflows.