IDE Mode
IDE Mode lets you browse and edit remote files inside the OxideTerm workspace. The editor, file tree, tabs, search panels, and dialogs are native GPUI views written in Rust.
Choose SFTP or SSH file access when opening the IDE. SSH offers Pure Shell commands or an agent installed, updated, or reused on demand. Basic editing does not require an agent.
Choose the Remote Environment
Section titled “Choose the Remote Environment”SFTP uses the connection’s file-transfer service. Pure Shell access uses Linux tools in the selected SSH environment, including GNU file and search utilities, without installing software. Its searches have execution and result limits. The agent adds file watching and symbol services on supported x86_64 and aarch64 Linux hosts.
To work inside a container or under a user selected with su, use Convert to IDE from the current idle terminal. It preserves that terminal’s user, environment, and directory instead of opening a separate login environment. Input pauses during conversion; use the return action to go back to the original terminal.
Native Editor
Section titled “Native Editor”The GPUI editor supports the workflows needed for focused remote changes:
- Syntax highlighting through OxideTerm’s Rust syntax layer
- Line numbers, indentation guides, folding, and bracket-aware editing
- Find and replace with case sensitivity, regular expressions, capture-group replacement, and replace all
- Multiline query/replacement paste and explicit newline insertion
- Multiple cursors and selections
- Undo and redo history
- Dirty-state tracking and save shortcuts
- Theme and font settings shared with the native application
The editor keeps text, selections, highlights, folds, and viewport state in Rust. It does not embed a browser editor component.
IDE and SFTP editors share the same search bar. Use its newline action to insert a line break; Enter and Shift+Enter navigate matches. Query and replacement inputs retain independent editing history. Dragging a selection past the editor’s upper or lower edge scrolls the document.
Language Support
Section titled “Language Support”Common shell and configuration languages are built in, including Bash, Zsh, Fish, PowerShell, Python, JSON, YAML, TOML, SQL, and Markdown. Other languages, such as Rust, Go, C/C++, JavaScript, and TypeScript, use language plugins.
Open Plugin Manager → Marketplace, find the language you need, and install and enable its plugin on this device. A text file can still be opened and edited without its language plugin; syntax highlighting and grammar-based features such as folding require the matching grammar. Installing the remote agent does not install local language plugins.
Remote File Tree
Section titled “Remote File Tree”The IDE sidebar provides a remote project tree with:
- Lazy directory expansion
- File and folder creation, rename, delete, and copy operations
- File-type icons and selected-file state
- Folder switching with an unsaved-change guard
- Git status when the active backend provides it
- Project-wide search results grouped by file
Selecting a file opens it in an editor tab. Multiple files can remain open, and unsaved buffers are protected from automatic tab eviction.
Save and Conflict Handling
Section titled “Save and Conflict Handling”Remote reads include content metadata such as size, modification time, and content hash where the backend supports it. When a save detects that the remote file changed after it was opened, OxideTerm presents a conflict instead of silently overwriting the newer version.
Agent-backed writes use staged atomic replacement and hash expectations. SFTP and pure Shell access retain save/conflict checks according to their backend capabilities. Saves to the same file are serialized, and remote temporary files use restricted permissions.
Use Ctrl+S or ⌘S to save the active file.
Optional Remote Agent
Section titled “Optional Remote Agent”After choosing SSH → Use agent, OxideTerm can install or reuse a lightweight Rust agent at ~/.oxideterm/oxideterm-agent in the selected environment. Installation shows progress. Bundled builds target x86_64 and aarch64 Linux.
The agent adds:
- Recursive file-tree operations
- Project text search
- Git status
- File watching notifications
- Symbol indexing, completion, and definition lookup
- Atomic writes with hash-based conflict detection
The desktop app starts the agent through an SSH exec channel. Requests and notifications are line-delimited messages carried inside the existing authenticated SSH connection; the agent does not listen on a network port.
Agent Lifecycle
Section titled “Agent Lifecycle”OxideTerm checks the remote agent version and compatibility level before use. A missing compatible agent can be installed from the IDE surface, while an incompatible build is reported instead of being used silently.
The remote binary remains on the selected host for later sessions and can be removed from the agent controls. Agent diagnostics are redacted before logging.
SFTP Access
Section titled “SFTP Access”IDE mode remains available without the agent:
- Directory and file operations use the managed SFTP session
- Files open and save through the same node identity
- The native editor and conflict UI remain available
- Agent-only capabilities such as live file watching and symbol indexing are unavailable
For ordinary configuration and script edits, SFTP mode is often sufficient.
Reconnect Behavior
Section titled “Reconnect Behavior”IDE consumers share node identity with terminal, SFTP, and forwarding surfaces. When SSH reconnect replaces the underlying connection, the IDE can reacquire its remote filesystem session without changing the visible node or project path.
Open buffers and dirty state remain in the native workspace. Remote I/O is gated while the node is unavailable and resumes only after a valid remote filesystem session is restored.
File Size, Encoding, and Line Endings
Section titled “File Size, Encoding, and Line Endings”IDE editing has its own 100 MiB file limit, independent of the SFTP preview limit. It applies to both agent-backed and SFTP-backed editing.
Opening a file detects its encoding, byte-order mark (BOM), and line endings. The editor uses LF internally, including pasted text, and restores the selected encoding, BOM, and LF/CRLF/CR format when saving. The existing status bar exposes encoding and line-ending controls: inspect the detected format, reopen with a chosen encoding, or change the format used for the next save.
Reopening replaces the buffer from disk; handle unsaved edits before choosing that action.