Current capabilities, practical examples and the gaps that could shape future improvements. Available features and unshipped ideas are labeled throughout.
Product notes reviewed
These capabilities are present in the current application. Access to remote services still depends on the host, account permissions and any required setup.
Distinguish rejected credentials, key problems, DNS failures, refused connections, timeouts and shell access restrictions. Keep the original failure visible and edit the connection from the error screen.
An account authenticates but cannot open a terminal: review shell/PTY permissions rather than replacing its password.
Start follow mode in the remote editor to read appended bytes while keeping the displayed tail bounded. Editing is disabled while following; stop following to return to file editing.
Watch fresh application messages after a release without repeatedly downloading the whole log.
Keep server-specific favorite directories, choose whether the file browser follows the terminal, and search into subfolders when needed.
Keep /var/log and your application folder close at hand without mixing favorites from staging and production.
Inspect visitor sessions, page paths, referrers and available browser/device context. Optional tracking adds interaction timelines and replay-style inspection when the required data is collected.
Compare a traffic spike with the routes visitors reach, then inspect an individual visitor timeline.
Browse table rows in pages of 50. Long cells use compact previews; table previews bound large text values before transfer. Run supported read-only queries and export the current result to CSV, JSON or SQL text.
Locate a record by its ID and status, then inspect its returned JSON preview without stretching every row.
Review local-to-remote folder differences, inspect file changes and choose individual or batch transfer actions. Deletions are separate actions to review deliberately.
Compare a staging configuration with your local copy before deciding which version should replace the other.
Review system vitals, cleanup candidates, security observations and failed services. Export a text report with findings and available execution logs, and inspect the proposed scheduled-care command before installing it.
Keep a record of disk pressure and the cleanup selections that justified a maintenance action.
Adjust interface scale from 90% to 150%, keep terminal appearance settings separate, and choose English or Turkish interface options.
Increase interface controls on a high-density display while retaining your preferred terminal font settings.
These are current product boundaries and setup requirements. They help explain what a tool can establish and where a separate workflow is still needed.
The current connection form covers a host, port, user and password or private key. A dedicated jump-host, tunnel and interactive MFA manager is not part of this workflow yet.
Open local and remote terminal tabs and switch between them. A saved split-terminal layout and automatic session restoration are not currently offered as dedicated features.
A compact cell is not a full database backup. Table previews can truncate large values, and exports contain the returned rows and values rather than an automatic export of the entire database.
Live resource views and System Care reports support the active investigation. They are not a durable cross-server metrics history, alerting service or team audit system.
Nginx insights depend on readable logs, their format and retention. Rich interaction views require explicit tracking setup and server changes. Review the collected event fields, access and retention before enabling them; missing records cannot be reconstructed.
English and Turkish options exist, but some tool-specific labels and notices remain inconsistent. Language completeness is an improvement area rather than a claim that every interface string is already translated.
Every item below is an idea for future development. These features are not shipped, and no availability date or implementation order is promised.
Make server identity and multi-step authentication understandable before a session is trusted.
A fingerprint review flow, saved trust decisions, changed-key warnings and dedicated prompts for challenge-based authentication.
A rebuilt server presents a new host key; the user can inspect and verify the change before deciding to continue.
Reach private infrastructure without rebuilding the route in a separate terminal.
Bastion profiles, explicit connection chains and named local port forwards with visible ownership and lifecycle controls.
Reach an internal database through an approved bastion and see which local port belongs to that connection.
Return to a working arrangement without reconstructing every tab and panel.
Named layouts, opt-in session restoration and horizontal or vertical terminal splits with a persistent host label.
Open a staging layout containing application logs, a local project shell and a remote inspection terminal.
Recover a large transfer after a dropped connection without losing track of progress.
Queued jobs, pause/resume where supported, explicit cancellation and integrity checks with a clear completed/failed state.
Resume an interrupted archive upload, then verify its integrity before using it for a release.
Understand what changed while you were away from the live host view.
Configurable local history, comparable snapshots, retention controls and opt-in alerts for resource thresholds.
Compare disk growth across a week and get an alert before the application filesystem fills.
Move a carefully organized workspace to another Mac without recreating every profile.
Reviewed OpenSSH configuration import and encrypted export/import with an explicit choice about including credentials.
Import approved host aliases, review unsupported settings and restore a backup on a replacement device.
Make repeated maintenance steps understandable and their outcomes reviewable.
Named multi-step runbooks, target-host previews, deliberate approval of changes and a local history that redacts secrets.
Review the destination and planned checks before a release, then retain the individual results alongside the runbook.
Know which version is installed, what changed and whether the selected language covers the active tools.
A release-notes view, a verified update flow and a systematic translation review of tool-specific screens.
Read the changes before installing a release and keep error messages and tool labels in the chosen language.
Read all capabilities, then follow the setup guide.
