ChannelTerm
Shared terminal sessions for humans and AI agents, starting with serial and hardware debugging.
English | Deutsch | Español | Français | 日本語 | 한국어 | Русский | 简体中文 | 繁體中文
ChannelTerm
Debug your board with AI. Stay in the same terminal.
ChannelTerm lets you and your AI client share a live serial or SSH terminal. Read the same device output, follow AI terminal commands, and take turns operating the board. It runs on Windows, Linux, and macOS and connects external AI clients through MCP.
Use GDB to let AI set breakpoints, step through Linux programs, and inspect variables. Connect the serial port on Windows and run GDB in WSL2, or keep the shared console open while GDB uses the board's Ethernet connection. Choose a debugging setup.
For short boot windows, let the Host interrupt U-Boot and verify the prompt. Export a diagnostic ZIP with optional raw bytes when investigating failures. U-Boot and diagnostic workflow.
Why ChannelTerm?
Keep your terminal open while the AI works with the same device connection:
+---- Human terminal
|
Serial device ---- Session
|
+---- AI / MCP client
Each client reads independently, so an AI reader does not consume the output you are watching. ChannelTerm displays AI terminal writes in your attachment; external debugger output has its own visibility rules.
What It Enables
- Share the console: human CLI and AI/MCP clients use one serial or SSH Session.
- Follow the work: see AI terminal commands alongside the device's output.
- Debug Linux programs: use managed GDB, a serial bridge, or GDB over the network.
- Move files: transfer over a shared serial Session with SHA-256 checks, or use dedicated SFTP/SCP connections.
- Start with one attachment:
channelterm attachcan create the local shared Host automatically.
Installation
Download the archive for your operating system and architecture from
Releases and verify it against that release's
SHA256SUMS. Extract it, then run .\channelterm.exe install on Windows or ./channelterm install
on Linux/macOS from the extracted directory. Prebuilt binaries do not require Go.
Building from source requires Go 1.26 or newer. Use a currently supported patched Go toolchain, then build the native executable from the repository root:
git clone https://github.com/akira-init1/ChannelTerm.git
cd ChannelTerm
go build ./cmd/channelterm
./channelterm install
install copies the running binary into the current user's standard program location, creates the
channelterm and cterm commands, adds that location to the user PATH only when necessary, and
initializes a missing minimal configuration. Open a new terminal when it reports a PATH change.
channelterm uninstall removes the installer-owned commands and PATH change while preserving user
data; channelterm uninstall --purge requires explicit confirmation before deleting configuration,
device state, and the local HTTP credential.
Supported desktop targets are Windows, Linux, and macOS on amd64/arm64. See Build and install from source, the exact
install / uninstall contract, and
configuration locations. Repository checks and cross-build
scripts are covered by Building and testing.
Quick Start: One Command, One Terminal
List detected serial devices, saved profiles, and Sessions from the default HTTP Host when it is available:
channelterm list
From the project's README.