electerm
Cross-platform terminal, SSH, SFTP and serial port client
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
◆Recent moves
- 9d ago
3.15.186 adds a dedicated SFTP channel and terminal write coalescing
Separates file transfer onto its own SFTP channel with managed lifecycle, adds write coalescing and buffer management to terminal output, and adds side-by-side code compare for two selected files. The transfer and rendering work here is the substantive half; the rest is mobile UI polish.
View source ↗ - 9d ago
3.15.171 adds AI guardrails, a disclaimer and Hungarian support
Adds optional mandatory guardrails and a disclaimer to the AI chat, alongside a new logo, Hungarian localisation and several WebGL and window-restore fixes. The guardrail and disclaimer work is what a project adds once it is hosting the AI backend itself rather than passing through a user's key.
View source ↗ - 19d ago
3.15.159 adds Android support and fixes the MCP server
Android joins the platform list and the MCP server gets a fix, extending electerm's reach in two directions at once — new devices and agent tooling. The release note is thin on what Android support actually covers, but it lands alongside the sustained mobile UI work in surrounding releases.
View source ↗ - 25d ago
3.15.138 gives AI chat memory, sessions and compression
Adds persistent chat memory and sessions plus conversation compression, turning the assistant from a one-shot prompt box into something with continuity. Also fixes connection hopping failing in some configurations, which matters more to daily SSH use than the AI work does.
View source ↗ - 27d ago
electerm ships AI presets backed by its own free service
⚡ SPARKThe release that makes AI a default capability rather than a bring-your-own-key option, by shipping config presets pointed at a free hosted endpoint the project runs. Everything in the AI thread since — memory, sessions, guardrails, disclaimer — follows from that decision.
View source ↗ - 29d ago
3.15.120 fixes unsafe filename handling across transfer paths
Four security fixes for unsafe filename parsing — custom editor, FTP/SFTP transfer, folder size checks and RDP file transfer — plus file comparison from the context menu and persisted split-view state. The clustering of these fixes shows how much surface a client covering this many transfer protocols has to sanitise.
View source ↗