Skip to content
| Marketplace
Sign in
Visual Studio Code>AI>Serial Log ToolsNew to Visual Studio Code? Get it now.
Serial Log Tools

Serial Log Tools

Preview

ponyhuang

|
33 installs
| (0) | Free
Serial port tools for Copilot Chat agent mode without requiring an MCP server
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Serial Log Tools

Serial Log Tools is a VS Code extension that adds serial debugging tools to Copilot Chat agent mode without using an MCP server.

This extension is self-contained. Users do not need a separate serial-log-mcp directory path configuration.

It is designed for device-side validation workflows such as:

  • sending AT commands to a modem or module
  • capturing boot logs over UART
  • waiting for a known serial pattern such as READY or BOOT OK
  • saving TX/RX logs to .txt files for validation records

Features

  • List available serial ports
  • Capture serial logs from a selected port
  • Wait for a serial pattern with timeout support
  • Send command data before capture or waiting
  • Save logs to .txt files with timestamp, device name, TX, and RX sections
  • For multiple ports, run all ports concurrently by default
  • Use the tools directly from Copilot Chat in Agent mode

Requirements

  • VS Code 1.100 or later
  • GitHub Copilot Chat with Agent mode enabled
  • Node.js installed on the machine
  • Access permission for local serial ports

Setup

  1. Install the extension .vsix or from the Visual Studio Marketplace.
  2. Open Copilot Chat and switch to Agent mode.
  3. Enable the serial tools in the tool picker.

How To Use

  1. Open Copilot Chat
  2. Switch to Agent mode
  3. Enable the serial tools in the tool picker
  4. Ask using natural language

Example prompts:

List available serial ports and tell me which one looks like the device.
Send AT*READVER\r\n to COM30 at 115200 baud, wait 300ms, capture 3 seconds of logs, and tell me the firmware version.
Wait on COM30 for READY with a 20 second timeout and save the captured log to a text file.
Simultaneously capture COM29 and COM30, save both logs, and compare whether they return the same boot message.
Wait on COM29 and COM30 for BOOT OK at the same time, then tell me which ports matched.

Saved Log Format

Saved logs include metadata and formatted TX/RX sections, for example:

---------- TX (Sent Command) ----------
TX [19:13:36.237] | AT*READVER\r\n

---------- RX (Received Data) ---------
RX [19:13:36.276] | *READVER:
RX [19:13:36.288] | OK

Settings

No mandatory extension settings are required for basic usage.

Optional:

  • serialLogTools.defaultOutputDir: default folder for saved logs.
    • If tool input includes outputDir, that value is used first.
    • If not set, extension falls back to VS Code global storage logs folder.

Packaging

cd D:\tools\serial-log-mcp\vscode-extension
npm install
npm run build
npm run package

Notes Before Marketplace Publishing

  • Replace the publisher value in package.json with your actual Marketplace publisher ID
  • Add your repository URL if you want Marketplace source links
  • Add a real license file before public publishing
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft