# AI use cases for Vicoa (vicoa-ai/vicoa) Repo: [vicoa-ai/vicoa](https://github.com/vicoa-ai/vicoa) | Use cases: 4 | Page: https://dedupedai.com/use-cases/vicoa-ai-vicoa/ Vicoa is an open-source orchestrator that runs a team of coding agents from desktop, mobile, and remote machines, and can be self-hosted. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run several coding agents on one repo at once: https://dedupedai.com/use-cases/vicoa-ai-vicoa/run-parallel-coding-agents-on-one-repo/ - Check and prompt running agents from your phone: https://dedupedai.com/use-cases/vicoa-ai-vicoa/steer-agent-sessions-from-phone/ - Run coding agents on a VPS or remote server: https://dedupedai.com/use-cases/vicoa-ai-vicoa/run-agents-on-a-remote-server-or-vps/ - Self-host the full Vicoa stack with Docker: https://dedupedai.com/use-cases/vicoa-ai-vicoa/self-host-the-vicoa-stack/ ## How to run several coding agents on one repo at once with Vicoa Repo: [vicoa-ai/vicoa](https://github.com/vicoa-ai/vicoa) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Start multiple agents on separate git worktrees so they can edit the same project without conflicts. **Who it is for:** A developer with a git project who wants Claude Code, Codex, and Cursor to work on different tasks at the same time. **The problem:** Running several coding agents in one folder causes them to overwrite each other and makes it hard to see what each one is doing. **The outcome:** Each agent works on its own git worktree and branch, and all sessions appear in one list you can check from one place. ### Steps 1. Install and sign in to each agent CLI you plan to use, for example `claude`, `codex`, or `cursor-agent`. 2. Install the Vicoa CLI with `npm i -g @vicoa/cli`. 3. Open Vicoa Desktop, click **New Session**, pick the machine, pick an agent, and enter the first prompt for that task. 4. Repeat the New Session step for each agent and task, choosing a different agent or prompt each time. 5. Open the single session list to check each agent's status, and review changes in the inline diffs. ### Prompt to paste into your agent ```text Using the vicoa-ai/vicoa repo, set up three coding sessions on , each with a different task and agent (Claude Code, Codex, and Cursor). Confirm that each session runs on its own git worktree and branch and that all three appear in the Vicoa session list. Report the session names and their status. ``` ### Caveat Each agent still needs its own installed and signed-in CLI, and Vicoa launches those CLIs with your existing credentials. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vicoa-ai-vicoa/run-parallel-coding-agents-on-one-repo/ ## How to check and prompt running agents from your phone with Vicoa Repo: [vicoa-ai/vicoa](https://github.com/vicoa-ai/vicoa) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Start a session on your laptop, then follow and prompt it from the Vicoa mobile app. **Who it is for:** A developer who leaves a long agent task running and wants to answer its questions or see when it finishes without returning to the desk. **The problem:** Coding agents often stop to ask for a decision, and you miss the prompt when you are away from your computer. **The outcome:** You get notified when an agent needs a decision or finishes, and you can reply from your phone with the same session synced. ### Steps 1. Install and sign in to Vicoa Desktop from https://vicoa.ai/download. 2. Click **New Session**, pick the machine and agent, and enter your first prompt. 3. Install the Vicoa iOS or Android app and sign in with the same account. 4. Wait for the push notification, then open the session on your phone to read the conversation and reply. 5. Use the dictation or @files features on your phone if you want to speak or reference a file. ### Prompt to paste into your agent ```text Using the vicoa-ai/vicoa repo, start a coding session on with the Claude Code agent and a prompt to . Confirm the session appears in the Vicoa mobile app under the same account and that a notification arrives when the agent asks a question or finishes. Report the session status seen on the phone. ``` ### Caveat The README says the agent machine must have a supported agent CLI installed and signed in, so the phone can only steer sessions that run on that machine. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vicoa-ai-vicoa/steer-agent-sessions-from-phone/ ## How to run coding agents on a VPS or remote server with Vicoa Repo: [vicoa-ai/vicoa](https://github.com/vicoa-ai/vicoa) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Connect a remote Linux machine so agents run there while you start them from your desktop or phone. **Who it is for:** A developer whose code lives on a VPS or remote server and who wants agents to run close to that code. **The problem:** Agents on a laptop cannot easily work on code that lives on a remote server. **The outcome:** The remote machine appears as a choice when you start a session, and the agent runs on it next to the code. ### 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 to paste into your agent ```text Using the vicoa-ai/vicoa repo, connect the VPS at as a Vicoa machine and start a Codex session on . 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. Risk, credentials: The agent CLI and its login live on the remote server, so keep that server access restricted and use your own keys. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vicoa-ai-vicoa/run-agents-on-a-remote-server-or-vps/ ## How to self-host the full Vicoa stack with Docker with Vicoa Repo: [vicoa-ai/vicoa](https://github.com/vicoa-ai/vicoa) | Difficulty: Advanced | Time: 2 hours | Basis: From the README Run the Vicoa backend, web app, and database on your own infrastructure using Docker. **Who it is for:** A team or individual that wants to keep sessions and account data on its own servers instead of a hosted service. **The problem:** Teams that need control over where agent sessions and messages are stored have no hosted-only option they can accept. **The outcome:** The full stack runs on your own machine or server, reachable through the Vicoa web app and clients you configure. ### Steps 1. Clone the repository with `git clone https://github.com/vicoa-ai/vicoa` and change into the `vicoa` folder. (inferred, check the README) 2. Run `cp .env.example .env` and set passwords and public URLs in the `.env` file. 3. Run `./backend/scripts/generate-jwt-keys.sh selfhost/keys` to create the signing keys. 4. Run `docker compose -f docker-compose.selfhost.yml up -d` to start the stack. 5. Follow SELF_HOSTING.md for the remaining configuration and checks. ### Prompt to paste into your agent ```text Using the vicoa-ai/vicoa repo, self-host the Vicoa stack on by following SELF_HOSTING.md. Confirm that the Docker containers started with `docker compose -f docker-compose.selfhost.yml ps` and that the web app loads at the URL you set. Report the running services and the URL. ``` ### Caveat The README gives only the core Docker commands and points to SELF_HOSTING.md for the full setup, so plan for that file's steps. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/vicoa-ai-vicoa/self-host-the-vicoa-stack/