RootRemDesk: a guide for the server owner
RootRemDesk is the privileged executor for a Linux server you own. TvijoTerm is its separate browser terminal for the owner. Reading this guide does not require GitHub access. Source and package access must be arranged separately; there is no verified public installer.
Current offer: 10 USDT per month. Root MCP connection through Tvijo and payment activation are not available yet. This guide describes local setup; it does not grant a server, subscription or production access.
1. Obtain the installation package
Use the Tvijo request form to ask whether a private-source owner pilot or installation package can be provided. Availability must be confirmed by the team. Before installation, confirm your Linux host, the delivery method and the package checksum. The repository does not need to become public for an owner to receive a package.
Do not treat the DSHREM balance top-up or a donation as a RootRemDesk subscription. There is no active RootRemDesk checkout on this page.
2. Build and check locally
If you have source access, use the repository's build instructions on a trusted machine. The smoke check uses a temporary directory and does not perform privileged production actions.
make test
make build
make smoke
3. Configure the host policy
Review the supplied policy with the server owner. Choose the host identifier and the exact permitted actions. Keep the signing key private and outside the AI client's reach.
The privileged daemon listens on a local Unix socket. It does not expose an HTTP endpoint. For a local owner check, restrict the socket to the owner; do not make it world-readable or expose it with a public shell proxy.
- Only actions declared in the host policy are available.
- Privileged AI actions require an approval ticket bound to the host, action, parameters and expiry.
- Health checks and an audit journal provide evidence; a successful build alone is not a deployment receipt.
4. Verify the local executor
After creating the configuration and key using the delivered package's instructions, start the daemon in one console and check it from a second. Check the audit output before adding further actions.
- A missing configuration, key or permission is a reason to stop and fix that prerequisite.
- Do not add a general shell action merely to make a check pass.
sudo ./bin/remdeskrootd -policy /etc/remdeskroot/policy.json
sudo ./bin/remdeskrootctl health -socket /run/remdeskroot/exec.sock
5. Set up TvijoTerm on your own server
Use the delivered TvijoTerm binary and installer, and compare their checksum with the package receipt. Installation is performed from the server console. The terminal listener stays closed outside an owner-opened access window.
Run pairing from the server console. Compare the TLS certificate fingerprint, open the one-time pairing link on your device and complete authenticator setup. Treat the pairing link and authenticator secret as credentials; never paste them into an AI chat.
- A login requires the paired device and an authenticator code.
- The browser terminal is a full owner shell; only use a trusted device.
- Close the access window when finished. Revoke a lost device from the server console.
tvijoterm pair
tvijoterm open 30m
tvijoterm status
tvijoterm close
6. Connect an AI client when the service is released
RootRemDesk enrollment and the customer Root MCP connection are not enabled yet. Do not paste a guessed endpoint into ChatGPT or Claude. When the connection is available, use the exact endpoint and authorization flow shown by Tvijo Connections.
The existing RemDesk panel and its limited workspace connection are separate. They do not activate RootRemDesk or grant a client full root access.
Request the package or ask a setup question · Open RemDesk panel
Reviewed 6 November 2026 against the RootRemDesk and TvijoTerm source documentation. Account provisioning and authenticated installation were not exercised by this publication.