-
Notifications
You must be signed in to change notification settings - Fork 0
Remote j3w1zsh Hosts
Remote access uses private Tailscale SSH plus tmux. It does not expose a public SSH port, change router forwarding, migrate credentials, or alter host power policy.
On native Arch or WSL:
j3w1zsh remote setup-hostThis is the only flow that offers to install Tailscale. It requires explicit confirmation, enables tailscaled, and starts user-owned Tailscale authentication.
On Termux:
j3w1zsh remote configure-client --host HOST --user USER
j3w1zsh remote status --json
j3w1zsh remote attach [SESSION]Settings are J3W1ZSH_REMOTE_HOST, J3W1ZSH_REMOTE_USER, and J3W1ZSH_REMOTE_ATTACH_COMMAND. Host, user, command, and session tokens are strictly bounded before SSH. tma attaches an additional tmux client; it never disconnects a client already attached from another device. Session deletion always targets the exact name and requires confirmation.
Interactive tma rows use real tab delimiters between the exact session name and display-only window, attachment, and creation metadata. Enter and Ctrl-X consume only the first exact field; metadata is never parsed to reconstruct a name. Direct tma SESSION, attached and detached picker rows, allowed punctuation, multi-client attachment, cancellation, and confirmed exact-session kill share that contract on WSL, native Arch, and Termux.
j3w1zsh 1.0.0 documentation — one shell. every machine. zero compromise. — MIT licensed.
- Getting Started
- Installation Methods
- CLI and Help
- Package Layers and Presets
- Theme Architecture
- Native Arch Linux
- Arch WSL 2
- Termux on Android
- Remote Hosts
- Workspace Schema v2
- Planning
- Updating
- Migration
- Configuration
- Architecture
- Security
- Backup and Recovery
- Troubleshooting
- Maintenance and Releases
- Agent Guide
- Sources