latest beta  ·  windows 10 21h2+  ·  x64 + arm64

ssh, telnet and local terminals for windows

keep your hosts in folders and open terminals side by side. resesh can also keep every command you run, with its output, so you can find it and compare it weeks later.

free & open source no cloud, no account imports securecrt, putty, openssh
resesh — split view · syd-pe-01 · syd-bastion-01
Resesh in the Phthalo Green theme: an ISP session tree beside two split terminals, a router's BGP summary on the left and an Ansible run on a bastion host on the right
split view with fictional isp hosts and documentation addresses
01

saved sessions

hosts in folders, with icons, colour tags and one shared login per folder. filter the list and press enter to connect.

02

command history

search every command and its output across all hosts. compare two runs of the same command.

03

splits and workspaces

tabs and split panes with live status. save a layout and reopen it for the next job.

04

ssh, telnet, serial, local

remote hosts, console servers and cables, powershell, cmd, wsl and git bash in one list.

$ scroll for the tour
01 / command history

find the command you ran last tuesday

turn on command history and resesh keeps each finished command with its output, host, folder, time and exit result. search all of it from one place, then put the command back at a prompt or reopen the session it ran in.

  • · every word must match the command, host, folder or output
  • · narrow with host:syd-pe in:/etc exit:fail, or pick a day on the calendar
  • · off by default, local only, and left out of backups
ctrl shift h open command history
command history — "bgp" across every host
Command history search for bgp, grouped by day, with the selected show bgp summary run and its output
02 / compare runs

see what changed since yesterday

run the same check twice and resesh can put the two outputs side by side. counters and timestamps that always move can be ignored, so the change that matters is the only thing left: here, one bgp peer that dropped to active.

compare with previous — show bgp summary on syd-pe-01
word-level marks added and removed lines, with the changed words marked. addresses and paths count as one word.
ignore the noise timestamps are ignored by default. turn on ignore numbers to hide packet and uptime counters.
honest about gaps runs that went through a pager, were cut at 64 kb, or scrolled away are flagged. f7 steps between changes.
sessions — devices grouped by site
ISP session tree grouped by site and role, with vendor icons and colour tags
03 / sessions and workspaces

organise hosts, then keep the layout

group sessions in folders and give each one a name, icon and colour. open them in tabs or split panes, then save the tabs, pane sizes and positions as a named workspace for the next maintenance window.

  • · select several sessions and open them in new splits, one pane each
  • · terminal theme, highlighting and history settings per session
  • · remote shells survive a dropped connection, kept alive by the resesh agent or tmux
ctrl shift p open a workspace from the command palette
04 / shared logins new

one login for the whole folder

an identity is a username and one way to prove it: a saved password, a registered key, or a password resesh asks for once each time it runs. set it on a folder and every session inside uses it. a session can still keep its own login.

  • · change a password in one place when it rotates
  • · if a host rejects it, resesh offers to update the identity for every session that uses it
  • · import finds logins that repeat and suggests identities for them
  • · passwords and passphrases stay in windows credential manager
settings — identities & keys
Settings, Identities and Keys: three identities with the folders and number of sessions that use each one
claude code over ssh — syd-bastion-01
Claude Code working on syd-bastion-01 over SSH, with its icon on the tab, beside Codex waiting for permission on syd-bastion-02
05 / coding agents updated

run claude code over ssh

coding agents on a remote host behave the way they do in a local terminal. tabs show which agent is running and whether it is working, waiting for you, finished or failed. claude code, codex, gemini cli, github copilot, cursor, opencode and 21 more agents are recognised by name.

  • · programs that report their own status need nothing installed on the server
  • · any program can report, not only agents: a deploy script gets a done or failed badge too
  • · copy from a remote program straight to the windows clipboard, and shift enter adds a new line
  • · box drawing, powerline separators and nerd font icons draw without a patched font
06 / telnet

console servers, lab gear, and the odd bbs

telnet sessions share the session list, tabs, splits, highlighting, history and recordings with ssh. the window size follows the tab, and send break works through a console server.

  • · text encoding per session: automatic, utf-8 or cp437 for ansi art
  • · report 80 × 25 to bbs servers, or keep the terminal at 80 columns for ansi art
  • · type telnet host 2003 in quick connect to reach a console line
telnet — a live synchronet bbs, cp437 art at 80 × 25
Telnet session to the Vertrauen Synchronet BBS showing CP437 block art and a TERM line that reads 80x25
rewind — back to when the peer was still active
07 / rewind

scroll back in time, not just up

rewind shows the terminal as it was minutes ago while the session keeps running, then returns to live. turn on recording to keep an asciicast file for playback and a text log you can search.

$ ls ~/resesh/recordings/ core-sw-01_2026-08-27_0914.cast   core-sw-01_2026-08-27_0914.log edge-fw-04_2026-08-26_2231.cast   edge-fw-04_2026-08-26_2231.log
08 / and the rest

the small things you'd miss

$ every feature, with screenshots →
09 / under the hood

native windows, measured

winui 3 and .net 10 for the app, libghostty-vt and direct2d for the terminal, ssh.net for the transport. the numbers below were measured while building it.

~900 automated tests xunit for the core, the app logic and the terminal.
<90ms history search a common word across 30,000 commands with output, from a sqlite fts5 trigram index.
~7mb/s ssh throughput an 8 mb log flood over ssh, parsed off the ui thread and drawn at the display's refresh rate.
0 cloud services no account and no sync. secrets live in windows credential manager, never in resesh's files.
10 / migration

bring your sessions with you

import saved ssh and telnet sessions from securecrt, putty or openssh. review them in a folder tree, choose which to add, and accept the shared logins resesh suggests. passwords are not imported.

$ compare resesh with other clients →
securecrt ssh and telnet hosts and session folders
putty saved ssh and telnet sessions from the registry
openssh host aliases from ~/.ssh/config
resesh backup restore sessions from a .reseshbackup file
./resesh

download the beta

free and open source. no account required.

windows 10 21h2 or newer installers and portable zip on github

questions

anything missing, open an issue on github.

is it free? yes. the source code is available on github.
where is my session data stored? saved sessions and recordings are stored locally. resesh does not require a cloud account.
does command history keep passwords i type? output can contain secrets, so history is off until you turn it on, and each session can opt out. it stays on this pc, is left out of backups, and deleted entries are overwritten on disk. entries older than 90 days are removed by default.
where are credentials kept? in the windows credential store, encrypted per user. resesh never writes a password to its own config files.
which protocols are supported? ssh, telnet, serial consoles and local shells.
does it work with claude code, codex or gemini cli? yes, locally and over ssh, along with codex, gemini cli, github copilot, opencode and 22 more agents. tabs show when an agent is working or needs you, remote copies reach the windows clipboard, and shift enter inserts a new line.
how does it compare with securecrt, putty or wezterm? there is a feature by feature table. it includes what resesh does not do yet: ssh agent support is planned.
what are the keyboard shortcuts? press ctrl shift / in the app for the full list, or open the command palette with ctrl shift p. shortcuts never take plain ctrl and letter keys from the shell.
mac or linux? resesh currently runs on windows only.