Termix-SSH / Termix-SSH/Support

[FEATURE] Optimize SFTP integration for a more streamlined SSH/SFTP workflow

Open
#521 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature file-manager platform-web ssh ui
Dominant language
No language data
Stars
28
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Title

Optimize SFTP integration for a more streamlined SSH/SFTP workflow

Platform

Web-app

Is it related to an issue?

Description:
Currently, Termixe opens the file manager (SFTP) in a separate tab, which requires frequent switching and breaks the workflow. I recommend optimizing the layout by referencing the design of Nexus-terminal (as shown in the comparison):

Auto-Sync Connection: When an SSH session is established, the SFTP client should automatically connect in the background/sidebar without requiring manual initiation.

Integrated Panel: Instead of a separate tab, support a split-screen or side-panel view for SFTP within the same SSH window. This allows users to manage files while keeping the terminal in sight.

Path History: Add a history feature for the current path in the SFTP panel to allow quick navigation to frequently used directories.

The Solution

Motivation / Problems Solved:

Fragmentation of Workflow: Currently, terminal and file management are decoupled. Switching between tabs to view files breaks the user's mental flow and concentration during command-line tasks.

Redundant Operations: Having to manually open an SFTP session after an SSH connection is established is repetitive and time-consuming, especially when managing multiple servers.

Path Disconnection: The terminal might be deep in a directory (e.g., /var/www/html/project), while the SFTP tab defaults to the home directory. An integrated panel ensures the file manager and terminal stay in sync.

Goal: Transform Termixe from a "set of tools" into a "unified environment" where files and commands are accessible in a single view.

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by mapping the existing SSH window, SFTP tab, connection flow, and current-path handling; the issue names no files or tests. Define the interaction and implementation boundaries with maintainers, then verify that an SSH connection can expose SFTP in an integrated panel, preserve terminal visibility, and support path history without requiring a separate tab.

Written by the indexing model from the issue text.

Assessment

Domain
backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.