DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run coding agents on a VPS or remote server with Vicoa

Connect a remote Linux machine so agents run there while you start them from your desktop or phone.

Credentials. The agent CLI and its login live on the remote server, so keep that server access restricted and use your own keys.

Who it is forA developer whose code lives on a VPS or remote server and who wants agents to run close to that code.

The problemAgents on a laptop cannot easily work on code that lives on a remote server.

The outcomeThe remote machine appears as a choice when you start a session, and the agent runs on it next to the code.

What you need first

  • At least one supported agent CLI installed and signed in on the machine that runs agents
  • A Vicoa account for the desktop and mobile apps
  • Node.js 18+ for the npm CLI, or pip on Intel Macs or old glibc systems

Steps

  1. On the VPS, install the Vicoa CLI with npm i -g @vicoa/cli (Node.js 18+ required), or use pip install vicoa on systems where npm is not suitable.
  2. Install and sign in to the agent CLI you want to use on the VPS, such as claude or codex.
  3. Run vicoa daemon on the VPS to connect that machine to your account.
  4. On your desktop or phone, click **New Session**, pick the VPS as the machine, the agent, and enter your prompt.

Prompt for your agent

Using the vicoa-ai/vicoa repo, connect the VPS at <server-address> as a Vicoa machine and start a Codex session on <remote-project-path>. Confirm the VPS appears as a machine option and the session starts there. Report the machine name and session status.

Caveat. The README only says to connect a machine with the daemon; check the remote-session docs for any firewall or network setup it may need.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page