PiNT TERMINAL / CONNECT & KEEP THE CONTEXT

Your connections.
Your workspace.

SSH and Telnet sessions, FTP and SFTP transfers, and recordings you can return to. A desktop terminal for macOS and Windows, with an encrypted local workspace.

0.2.0 · STABLE RELEASE

macOS APPLE SILICON · WINDOWS x64

PiNT TERMINALWORKSPACE ILLUSTRATION
One local workspace.

Groups · devices · recordings

SSH
Connect to a saved hostVerify its fingerprint. Open a session.
SFTP
Move a fileBrowse local and remote folders.
REC
Revisit the outputRead recordings after disconnecting.
GROUP DEVICESCONNECTKEEP THE RECORD
Illustrative workflow, not an app screenshot. Check the release notes for platform coverage and current limitations.

Connect. Transfer.
Pick up the context.

Keep connection details and received output together, with tools for the next visit.

01 / CONNECTIONS

Your hosts, organised.

Organise SSH, Telnet, FTP and SFTP devices inside groups. Share a group username, password and SSH key path, or set custom credentials per device. Create and rename groups, add or move devices, and search groups, names, addresses and tags.

02 / RECORDINGS

Keep the output.

Encrypted recordings remain readable after disconnecting or restarting. Scrollback is stored on disk, with available disk space as the practical limit. Export the original text stream when needed.

03 / FILE TRANSFERS

Local and remote, side by side.

Browse folders and upload or download one file at a time with FTP or SFTP. Follow progress or cancel a transfer. Downloads replace the destination only after success.

04 / RECONNECT

Control the next connection.

Use multiple terminal tabs, SSH keepalives and manual or automatic reconnect. Existing tabs retain their connection details through reconnects; open a new tab to use changed group defaults. Reconnecting opens a fresh session, without restoring a lost shell.

05 / WORKSPACES

Take your setup with you.

Export an encrypted workspace bundle with profiles, trusted host keys, settings and recordings. Import it on another device with the same passphrase. Live sessions do not migrate.

06 / TFTP

Serve a file when you need it.

Manually start a read-only TFTP host for a selected folder. It defaults to localhost on UDP 1069 and rejects symbolic links and files outside that folder. Uploads are not supported.

0.2.0 / RELEASED 25 OCTOBER 2026

Stable release · v0.2.0

Get connected.
Stay organised.

PiNT Terminal 0.2.0 is marked stable. Choose the self-contained Windows EXE or the Apple Silicon Mac DMG. Neither needs a separate Python installation.

Before upgrading a workspace

Finish active sessions and close the older app. Keep an exported backup and store the passphrase separately; there is no passphrase recovery. Version 0.2.0 upgrades the vault format. Upgraded vaults and exports cannot be opened by 0.1.1. Read the backup and rollback steps below.

macOS / ARM64

Apple Silicon

Open PiNT-Terminal-0.2.0-macOS-arm64.dmg, drag PiNT Terminal.app to Applications, then launch it there.

Ad hoc signature. Not Apple-notarised. An Intel macOS build is not included.

Download macOS DMG

WINDOWS / x64

Windows

Download and run PiNT-Terminal-0.2.0-Windows-x64.exe directly. Its runtime is included; no separate folder of libraries is required.

Unsigned. Tested using x64 emulation in a Windows 11 ARM64 VM. Conventional x64 hardware acceptance is pending; a native ARM64 build is not included.

Download Windows EXE

New in 0.2.0: groups containing devices, shared group credentials and complete per-device overrides. The details panel shows the credential source without exposing the password. Read the release and verification notes ↗

Third-party runtime licence notices are included in both packages. Download checksums are listed in SHA256SUMS.txt.

FIRST USE

Make a workspace.
Make it yours.

Start with a local encrypted vault. Your passphrase unlocks the saved connection details and recordings.

  1. Create your workspace.

    Choose a passphrase of at least 12 characters. There is no cloud service or recovery route if you forget it.

  2. Create a group and add devices.

    In Vault, choose New group and set its default credentials. Choose Add device to group, then enter the hostname/IP, protocol and port. New devices use group credentials; choose Custom credentials to override them. Verify the fingerprint on first SSH/SFTP use. Changed keys are blocked; Telnet login stays interactive.

  3. Connect, then revisit.

    Open your session and return to received output under Recordings. The readable view interprets line-editing controls; raw exports retain the original text stream.

  4. Back up and close.

    Export a .pintbundle for backup or import on another device. Use Lock & close to disconnect, save and close the app.

GROUPS & EXISTING WORKSPACES

Shared defaults.
Explicit overrides.

A device uses one complete credential set. Blank custom fields stay blank and never fall back to group values.

Choose the credential source. Each group holds a username, password and SSH key path. Custom credentials replace all three fields. The details panel identifies group or custom credentials without showing the password. SSH supports passwords, unencrypted private-key files and the SSH agent.

Apply changes to new sessions. Changed group defaults apply to new sessions and file operations. Existing terminal tabs retain their connection details, including through reconnects. Open a new tab to use the updated defaults. Move a device in Edit device; groups can be renamed, and empty groups can be deleted.

Upgrade with the original vault preserved. Existing device credentials become custom credentials. Before the first format upgrade, PiNT saves the original encrypted vault beside the workspace as name.v1-backup.pint, with a numbered suffix if needed. Upgraded vaults and exports require 0.2.0 or later; 0.1.1 cannot open them. Recordings keep their existing format.

Return to an older app. Close PiNT, preserve the upgraded files separately, then restore the backup under the original workspace filename beside its unchanged .sessions.sqlite recordings database. This restores the pre-upgrade device settings; later group and device edits remain in the upgraded vault.

THE PRACTICAL DETAILS

Before your
first session.

What is encrypted?

The local workspace encrypts groups, device profiles, passwords, trusted host keys, settings and recordings. Exported workspace bundles are encrypted too. Raw transcript exports are unencrypted, and any secret printed by a remote device can appear in its recording. Telnet, FTP and TFTP do not encrypt network traffic.

Can I move a workspace between macOS and Windows?

Export a .pintbundle and import it using the same passphrase. Groups, device profiles, credentials, trusted host keys, settings and recordings move with it. Upgraded exports require 0.2.0 or later. Private-key files are referenced by path and are not included, so re-select them on the new device or use its SSH agent. Live connections and remote shell processes do not move.

What is still in development?

Serial connections, SSH MFA and encrypted private-key prompts, jump hosts, forwarding, split panes, recursive transfers and a transfer queue are pending. Automatic vault locking, passphrase rotation, multi-instance editing protection and signed installers are also pending. See the current limitations before relying on a particular workflow.

Is a recording a full terminal replay?

No. The reader is a paged CLI transcript, without full-screen or timed replay. Whole-archive search, retention controls and recording deletion are not implemented. Terminal handling is based on pyte; full xterm, terminal graphics and complete Unicode/reflow compatibility are not claimed.

How has 0.2.0 been checked?

The release reports 133 tests and seven subtests passing on each of macOS Apple Silicon and Windows 11 ARM64 with x64 Python under emulation. Group/device forms, scaled layouts, standalone packages and a macOS → Windows → macOS workspace round trip were checked. GitHub verification passed on macOS and Windows with Python 3.12 for the release commit. Conventional x64 hardware, Intel macOS, native Windows ARM64 and further real-device acceptance remain unverified. Read the release verification notes.

How can I report a problem?

Open an issue in the PiNT Terminal repository with the app version, platform and steps to reproduce it, or email reece@pinetworktools.com. Remove credentials and sensitive network details before sharing recordings or logs.