It's a VIM-like text editor that edits local files, remote files, and remote files from inside the remote session itself. It provides a familiar VIM interface with NORMAL and INSERT modes, character operations, and real-time remote synchronization.
π‘ Included : Another function, Edit-RemoteFile is providing another way to remotely open/editing file with VSCode (or notepad) using WinRM.
>_ Windows Terminal
| π No dependency |
π Secure |
β¨οΈ Keyboard only |
π Vim like |
π«§ Lightweight |
- Require PowerShell 7
To install the module from the PowerShell Gallery, you can use the following command:
Install-PSResource -Name PSBITE
Import-Module -Name PSBITEπ‘ Feel free to create an alias in your profile vim, bite, psb, teub !
The editor always runs on your machine. In every mode, the UI appears in your own terminal (or your own VSCode). Nothing is ever installed on the remote server. What changes is only where the file lives and where you type the command.
flowchart TD
Q1{"Where is the file?"}
Q1 -->|"On this machine"| M1["<b>Local</b><br/>psbite file.txt"]
Q1 -->|"On a remote server"| Q2{"Where are you typing?"}
Q2 -->|"At my own prompt"| M2["<b>Remote</b><br/>psbite file.txt -cn srv01<br/>bite file.txt -cn srv01"]
Q2 -->|"Inside the server,<br/>after psbite -es srv01"| M3["<b>Session</b><br/>psbite file.txt<br/>bite file.txt"]
style M1 fill:#4CAF50,stroke:#2E7D32,stroke-width:2px,color:#fff
style M2 fill:#207bcd,stroke:#1565C0,stroke-width:2px,color:#fff
style M3 fill:#8d2640,stroke:#6a1b32,stroke-width:2px,color:#fff
| π» Local file on this machine |
π Remote from your prompt |
π°οΈ Session from the remote prompt |
|
|---|---|---|---|
Start-PSBite (psbite)terminal editor |
β | β | β |
Edit-RemoteFile (bite)VSCode / Notepad |
β | β | β |
| Where the UI opens | Your terminal | Your terminal / Your VSCode | Your terminal / Your VSCode |
β Edit-RemoteFile is remote-only by design: it exists to bridge a remote file to a local
graphical editor. For a local file, just open it directly.
In Session mode you first enter the server, then call the commands from its prompt. Relative
paths are resolved on the remote side, so .\test.txt means what you expect:
psbite -es "server01"
[server01]: PS C:\> # Do any command you like
[server01]: PS C:\> # And you can edit when you need it
[server01]: PS C:\> psbite .\test.txtIt's like PSBITE is replacing the Enter-PSSession and you can edit files also from the psbite alias.
Here is a list of example that are typical use cases for the module.
Using PSBITE γ²
Edit a remote file with real-time synchronization
Start-PSBite -FilePath "C:\scripts\remote.ps1" -ComputerName "server01"Or drive PSBITE from inside a remote session, the editor still runs on your machine
psbite -es "server01"
[server01]: PS C:\> psbite .\remote.ps1Using Edit-RemoteFile γ²
Edit with bidirectional synchronization (remote changes are pulled to local)
Edit-RemoteFile -ComputerName "server01" -RemotePath "C:\Scripts\test.ps1" -DualSimple example of Edit-RemoteFile

Showing the Dual and DelTemp, used on a logs

To find more examples of how to use the module, please refer to the examples folder.
Alternatively, you can use the Get-Command -Module 'PSBITE' to find more commands that are available in the module. To find examples of each of the commands you can use Get-Help -Examples 'CommandName'.
.PARAMETER ComputerName
# Remote server name or FQDN
.PARAMETER RemotePath
# Full path to the file on the remote server
.PARAMETER LocalTempDir
# Local temporary directory for file synchronization (default: $env:TEMP\RemoteEdit)
.PARAMETER UseSSL
# Use SSL for WinRM connection (default: true)
.PARAMETER Credential
# Credentials to use for the remote connection (default: current user)
.PARAMETER SkipCertificateCheck
# Skip SSL/TLS certificate verification, needed for self-signed certificates
.PARAMETER DelTemp
# Delete temporary file when finished (default: false - file is preserved)
.PARAMETER Dual
# Enable bidirectional synchronization - monitors both local and remote file changes
.PARAMETER Silent
# Minimal output - show only essential connection and monitoring messages
.PARAMETER Verbose
# Enable verbose output for debugging and detailed information. SO AJ :-)
.EXAMPLE
Edit-RemoteFile -ComputerName "server01" -RemotePath "C:\Scripts\test.ps1"
# Edit a remote PowerShell script with SSL and unidirectional sync
.EXAMPLE
Edit-RemoteFile -ComputerName "server01" -RemotePath "C:\Scripts\test.ps1" -Dual
# Edit with bidirectional synchronization (remote changes are pulled to local)
.EXAMPLE
Edit-RemoteFile -ComputerName "server01" -RemotePath "C:\Scripts\test.ps1" -Silent
# Edit with minimal output showing only essential messages
.EXAMPLE
Edit-RemoteFile -ComputerName "server01" -RemotePath "C:\Scripts\test.ps1" -DelTemp
# Edit and delete temporary file when finished
.EXAMPLE
Edit-RemoteFile -ComputerName "server01" -RemotePath "C:\Scripts\test.ps1" -Verbose
# Edit with verbose output showing file paths
.EXAMPLE
Edit-RemoteFile -ComputerName "lab01" -RemotePath "C:\Scripts\test.ps1" -Credential $cred -SkipCertificateCheck
# Edit on a host using explicit credentials and a self-signed certificate.PARAMETER FilePath
# Path to the file to edit (local or remote). Can be relative or absolute for local but must be absolute when using the remote.
.PARAMETER ComputerName
# Remote computer name for remote editing (optional)
.PARAMETER UseSSL
# Use SSL for remote connection (default: true)
.PARAMETER Credential
# Credentials to use for the remote connection (default: current user)
.PARAMETER SkipCertificateCheck
# Skip SSL/TLS certificate verification, needed for self-signed certificates
.PARAMETER EnterSession
# Enter an interactive session on -ComputerName instead of opening a file (alias: es)
# In this mode -ComputerName is positional, so: psbite -es server01
.EXAMPLE
Start-PSBite -FilePath "C:\test.txt"
# Edit a local file
.EXAMPLE
Start-PSBite -FilePath "C:\scripts\remote.ps1" -ComputerName "server01"
# Edit a remote file with real-time synchronization
.EXAMPLE
Start-PSBite -ComputerName "server01" -EnterSession
# Enter server01, then edit from the remote prompt with: psbite .\test.txt
.EXAMPLE
psbite -es server01
# Same thing, short form: ComputerName is positional when entering a session
.NOTES
# Controls:
- i : Enter INSERT mode
- Esc : Enter NORMAL mode
- y : Yank (copy) line
- dd : Delete line
- p : Paste line
- :w : Save file
- :q : Quit
- :q! : Quit without saving
- :wq : Save and quitThe local and remote modes are driven from your own prompt: you name the server, PSBITE goes and
gets the file. Session mode is the other way around. You enter the remote server like with
Enter-PSSession, and from there you call the PSBITE commands, which still execute on your
machine against the remote path.
Start-PSBite -ComputerName "server01" -EnterSession
psbite -es "server01" # same thing, short form
[server01]: PS C:\> psbite .\test.txt # PSBITE editor, in your terminal
[server01]: PS C:\> bite C:\logs\app.log # VSCode / Notepad, on your desktop
[server01]: PS C:\> exitA few things worth knowing:
- Both
Start-PSBite/psbiteandEdit-RemoteFile/biteare defined inside the session. - The remote prompt stays blocked while the editor is open.
-ComputerNameis positional here, but stays named in the editing modes, sopsbite some-file.txtis always a local edit and never a connection attempt.- The session's own connection options are reused by the commands called inside it, so a host
needing explicit credentials or a self-signed certificate works the same way:
psbite -es "lab01" -Credential $cred -SkipCertificateCheck
Nothing is installed or configured on the remote server, everything is set up from local code. It works by defining those commands in the session so that calling them raises an event back to your host, which then runs the real command locally.
β οΈ Any code running in that remote session can invoke the callbacks, so only use it against hosts you trust.
Three ways to edit covers when to reach for each one. This is how they differ internally: they don't use the same method to work. PSBite is a VI like that capture the key touched to do action where Edit-RemoteFile monitor the file to take action.
| Start-PSBite | Edit-RemoteFile |
|---|---|
| πΉ Built-in editor | π External monitoring |
| β¨οΈ Responds to keystrokes | ποΈ Monitors the file |
| π Direct editing | π Change detection |
| πΎ AutoSave timer | π Polling timestamp |
| π₯οΈ Terminal interface | π VSCode/Notepad |
| π» Local, π remote and π°οΈ session | π remote and π°οΈ session only |
Since I was using core server, as soon as you need to manipulate file, logs or create file without GUI it was honestly a nightmare for me. I was not able to find something like nano built-in or even depending on VSCode. Because I'm working in a high secure area, we cannot afford to install cosmetic or non approved software like Vim on each servers. This is where the creation of this module started, because custom and selfmade PowerShell module are already running why not creating mine that can benefit my daily work and help the community ?
It was like a challenge after attempting PSConf, I wanted to make something that was able to make me proud and ready to myself go on stage next time.
Then Edit-RemoteFile came alive in parallel for the same reasons, mainly for internal usage but finally integrated to PSBite because it's working not the same way and can also benefit to other users.
See Function Dependencies to understand link between each functions.
Coder or not, you can contribute to the project! We welcome all contributions.
If you don't code, you still sit on valuable information that can make this project even better. If you experience that the product does unexpected things, throw errors or is missing functionality, you can help by submitting bugs and feature requests. Please see the issues tab on this project and submit a new issue that matches your needs.
If you do code, we'd love to have your contributions. Please read the Contribution guidelines for more information. You can either help by picking up an existing issue or submit a new one if you have an idea for a new feature or improvement.
Thanks to Marius for his job on PsModule Framework used to built the skeleton of PSBITE.
Thanks to Jordan Borean for the session callback mechanism behind the session mode, shared in issue #13 and vendored under the MIT License, see THIRD_PARTY_NOTICES.md.
Thanks to my colleagues who challenged me, helped me publish it and using it daily.







