Connections, terminals and tasks
Install and start NimoteHost first, then use the same computer and SSH account to open sessions.
Choose Host and your SSH connection
- Choose Host from NimoteCode's mode entry or the mode menu in an existing workspace.
- On the setup screen, tap SSH connections.
- Pick the computer and account where you installed Host. Use New Remote Connection if you have not saved it yet.
- Verify the SSH host key on the first connection. Once connected, you should see the session list. An empty list is normal on a new Host.
Enlarge
EnlargeIf the app reports a missing, stopped, or incompatible Host, fix that condition and retry. Discovering a stopped Host does not automatically start it.
Open a terminal first
- Tap + and select Terminal in the new-session window.
- Enter the workspace directory or use the folder button. It must already exist on the remote computer and be accessible to your SSH account.
- Tap Start session and wait for a shell prompt.
- Run
pwd, thenecho Host connectedto check the directory and output. In Windows PowerShell, useGet-Locationfor the directory.
EnlargeThese 2.4.1 captures show the existing pocket-shop workspace. The terminal capture is a completed command session; the steps above illustrate how to create an interactive shell.
Returning to the list leaves the shell running. To end the demo shell, enter exit or use the session's stop button. Once stopped, opening its history shows retained output; it does not bring the process back.
Return to the same session
In Sessions, search by name or directory, choose All, Running, or History, and open the session. Its menu includes pinning, renaming, and other actions.
EnlargeAfter leaving the app or losing SSH, reconnect to the same Host. If Host and the managed process are still running, you can reattach without executing the original command again.
Sleep, logout, and a Host or OS restart are different. Host does not resurrect processes after a restart; unfinished sessions become interrupted. On Linux, logout behavior depends on user-service and lingering settings. macOS and Windows user services also depend on the login session.
If session creation times out, refresh the list before trying again. Check whether the first request created a session already.
Run a one-off task
Choose + → Task, select the directory, enter a command, and start it. Try echo Host connected first, then use your project's build or test command once the directory and output look right.
When it finishes, read the exit code and log. A task called “Tests” is only a name; check what actually ran and what it reported. Use Terminal for commands that need ongoing interaction.