by akira-init1
Shared terminal sessions for humans and AI agents, starting with serial and hardware debugging.
# Add to your Claude Code skills
git clone https://github.com/akira-init1/ChannelTermGuides for using ai agents skills like ChannelTerm.
Last scanned: 11/17/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-11-17T12:48:23.697Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how ChannelTerm compares with popular alternatives.
ChannelTerm is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by akira-init1. Shared terminal sessions for humans and AI agents, starting with serial and hardware debugging. It has 184 GitHub stars.
Yes. ChannelTerm passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/akira-init1/ChannelTerm" and add it to your Claude Code skills directory (see the Installation section above).
ChannelTerm is primarily written in Go. It is open-source under akira-init1 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh ChannelTerm against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
English | Deutsch | Español | Français | 日本語 | 한국어 | Русский | 简体中文 | 繁體中文
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.
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.
channelterm attach can create the local shared Host automatically.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.
List detected serial devices, saved profiles, and Sessions from the default HTTP Host when it is available:
channelterm list
A running Host is optional. When it is unavailable, list reports MCP as offline and still shows
local devices and profiles.
See the CLI reference for the complete option contract.
If an AI client should join the Session, configure a supported client once before attaching:
channelterm init --mcp
Choose HTTP, or press Enter for the HTTP default. The configuration includes the local Bearer credential. Reload the AI client if it does not pick up configuration changes immediately.
Then run the command for the current platform:
# Windows
channelterm attach COM8 --baud 115200 --label board
# Linux
channelterm attach /dev/ttyUSB0 --baud 115200 --label board
# macOS
channelterm attach /dev/cu.usbserial-110 --baud 115200 --label board
That single attach command opens the serial device and attaches the current terminal. When no
compatible Host is already running at the default endpoint, it also starts a temporary local HTTP
MCP Session Host automatically. Typical startup output is:
Shared Session created: SER-1 (0123456789abcdef0123456789abcdef)
[ChannelTerm] Temporary Session Host started; it and all shared Sessions stop when this attachment exits. Run 'channelterm mcp --transport http' separately for a persistent Host.
No separate MCP-server terminal is required for this quick path. While the attachment remains open,
a configured HTTP MCP client can use http://127.0.0.1:37099/mcp and operate the same SER-1.
The temporary Host and every Session it owns stop when the creating attachment exits; use a
persistent Host only when Sessions must outlive that terminal.
--label board is an optional display name, not an identifier. Use SER-1 or the opaque Session ID
when another client needs to refer to the Session.
| Goal | Command |
|---|---|
| Open a shared serial Session and auto-start a temporary Host | channelterm attach COM8 --baud 115200 |
| Configure a supported AI client for the shared HTTP Host | channelterm init --mcp |
| Keep the Host and Sessions alive independently | channelterm mcp --transport http |
| List or join an existing Session | channelterm list --kind session then channelterm attach SER-1 |
| Open a private serial connection with no MCP sharing | channelterm attach COM8 --private --baud 115200 |
| Watch structured Session activity | channelterm events SER-1 |
| Open the guided file-transfer menu in the current shared attachment | Press Ctrl+], then press f |
| Send or receive through a shared Session | channelterm file send firmware.bin --session SER-1 or channelterm file receive /tmp/log.txt ./log.txt --session SER-1 |
A persistent Host is a separate long-running process. After it reports
MCP Streamable HTTP listening on http://127.0.0.1:37099/mcp, other shells and configured AI clients
can create or join Sessions. Silence after the readiness line is normal; stop the Host with
Ctrl+C when all of its Sessions should close.
During ordinary terminal use, outside a file transfer or debugger takeover:
Ctrl+C Send 0x03 to the remote terminal
Ctrl+] q Leave this CLI; an attachment-owned temporary Host also stops
Ctrl+] ? Show local escape help
See the CLI reference for all local controls and the MCP workflow for client setup and AI-created Sessions.
For reusable workflow guidance, install the bundled
cterm-serial-debug Agent Skill
in an Agent Skills-compatible client. channelterm init --mcp configures MCP clients but does not
install the Skill.
The HTTP server requires a per-user Bearer token and defaults to a loopback-only listener. Built-in
CLI clients use the local token automatically. It can also listen on a trusted
LAN; remote clients must use the Host's reachable
address and send the same token through the Authorization header. Do not expose the endpoint
without TLS and separate network access controls.
An attached CLI renders an Agent command as a local AI activity block. terminal_exec keeps that
command out of an idle Bash prompt's history; the lines after the block are still the device's raw
terminal output, and the human can type again when the short command lease is released:
root@board:~#
──────── AI ────────
[18:52:31] >> echo agent-check
────────────────────
agent-check
root@board:~# echo human-still-here
human-still-here
root@board:~#
The exact command output depends on the connected device. The AI block is local presentation
derived from structured Session events; it is not inserted into the device byte stream or stored
terminal output. Raw keys and interactive programs still use terminal_write and retain the
device's normal history behavior.
Connect using an authorized private key (encrypted keys prompt for a passphrase) or enter your
login password when prompted. Passwords and key passphrases are not saved. For an unknown server,
verify its displayed fingerprint and enter yes to save its public
key in ~/.ssh/known_hosts; changed keys are rejected. Prompts require an interactive terminal:
# Terminal 1: open the shell; then run uname -a at its prompt.
channelterm ssh user@192.168.1.50
# Terminal 2: observe and use the same shell.
channelterm attach SSH-1
Keep the first command running: exiting it closes this Host and its Sessions. The default local sharing port must be free; use --listen and the printed attach endpoint for a separate Host. See the SSH workflow for key paths, host verification, ports, and current limits.
Use SFTP for file transfer and remote file management, or legacy SCP for compatible POSIX servers: