Skip to content

ssh-commander v0.1.0

Choose a tag to compare

@lexuss1979 lexuss1979 released this 09 Sep 22:25
· 9 commits to main since this release

ssh-commander v0.1.0

Your personal AI DevOps: get your project running on a VPS, and get help when something breaks.

This first public release lets you describe a task and have an AI agent investigate and work on your actual Linux server over SSH. You don't need to carry commands and output between a separate chat and terminal. The agent asks for approval before making changes; terminal, files and Docker tools remain available when you want to take over.

The app is free and MIT-licensed, with no ssh-commander subscription. You pay for your servers and AI API usage with your own key. This is an interactive assistant, not an autonomous 24/7 on-call service; review proposed actions and keep backups.

Highlights

  • SSH terminal tabs, command history and sessions that survive page reloads.
  • SFTP file manager with editing, directory transfers, search and live log viewing.
  • Docker Explorer with Compose v2, container terminals and live logs.
  • PostgreSQL/MySQL consoles, systemd, Nginx, cron, package updates and SSH tunnels.
  • AI plan mode, per-server memory and cost tracking with your own API key.
  • English and Russian UI, dark and light themes, and settings without a restart.

Install

Requires Git and Docker with Compose v2.

git clone https://github.com/lexuss1979/ssh-commander.git
cd ssh-commander
git checkout v0.1.0
docker compose up -d --build

Open http://localhost:8080, set a password, add your AI API key and connect your server over SSH. No .env file is required. You can skip the key to use the manual tools and add it later in Settings. Run the app on your own computer; it does not rent a VPS for you.

Demos

Animated previews are available in the README.

Before You Run It

This is a single-user, localhost-only tool, not an internet-facing server panel.
SSH/DB passwords and the AI API key are stored in plain text in the local data
volume. AI prompts and tool results go to your configured provider, which can
also be self-hosted. SSH tunnels are accessible to other local processes.

MIT-licensed, published as-is, maintained on a best-effort basis with no SLA.
Please read the README's Security section before use.