Vibecode TeamViewer
track this build5 steps, step by step0%KINDA · weekend project
If you only need to reach your own machines, most of TeamViewer's value is reproducible: screen capture, a WebRTC pipe, and synthetic mouse and keyboard events are all solved problems with libraries. An agent can wire that into a working host agent plus browser viewer in a weekend, and on your own LAN it will feel fine. What breaks is everything outside your control: connecting through hostile double NAT without your own TURN server, waking a sleeping box, keeping latency sane over mobile networks, and surviving OS permission prompts on macOS after every update. It also stops being a support tool, because the whole point of TeamViewer for helping your parents is that they can install one thing and read you a nine digit number. Build it for your own boxes, keep paying if you support other people's.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of TeamViewer. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # TeamViewer indie build ## Goal Build the smallest trustworthy replacement for the core TeamViewer workflow for one developer or a tiny team. ## Scope A host agent on each of your machines streams its screen over WebRTC to a password-protected browser viewer that injects your mouse and keyboard events back. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Connections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure - Native clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support - The support workflow: a one-click download and a session code a non-technical person can read to you over the phone - Unattended access extras: wake on LAN, reboot and reconnect, multi-monitor switching, file transfer, session recording, printing - Commercial licensing, audit logs, and the corporate compliance story that makes IT allow it at all If those capabilities are essential, use TeamViewer instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a self-hosted personal remote desktop system: a host agent I run on machines I own, and a browser viewer I open to control them. Stack, no substitutions: - Node 20 + TypeScript for both host agent and signaling server. - WebRTC via the werift library on the host side, plain browser WebRTC on the viewer side. - ffmpeg (spawned as a child process) for screen capture and H.264 encoding. - @nut-tree-fork/nut-js for mouse and keyboard injection on the host. - Signaling over WebSocket (ws), single small server, no framework. - Viewer is one static HTML file with vanilla JS and a canvas/video element. No React, no build step for the viewer. Structure: - /signal: WebSocket signaling server. Hosts register with an ID and a shared secret from .env. Viewers authenticate with the same secret, then get relayed SDP and ICE. - /host: the agent. Captures the primary display with ffmpeg (avfoundation on macOS, gdigrab on Windows, x11grab on Linux), pipes encoded video into a WebRTC track, opens a data channel, and applies incoming input events with nut-js. - /viewer: static page. Shows available hosts, connects, renders the video track, captures mouse move/down/up/wheel and keydown/keyup, normalizes coordinates to the remote resolution, sends them over the data channel. Rules: - All config in .env: SIGNAL_URL, SHARED_SECRET, HOST_ID, TURN_URL, TURN_USER, TURN_PASS. Ship .env.example. Never hardcode secrets. - No accounts, no database, no telemetry, no cloud services beyond the signaling server and TURN that I run. - Target 1080p at 25fps with a tunable bitrate and a keyframe interval short enough to recover fast. Prefer latency over quality. - Data channel messages are small JSON objects, unordered, unreliable for mouse moves and ordered/reliable for clicks and keys. - Include a --view-only flag on the host that ignores all input events. - Log connection state transitions clearly so I can tell whether ICE failed or the encoder died. Explicitly out of scope: file transfer, clipboard sync, multi-monitor selection, mobile clients, unattended wake, NAT traversal magic beyond standard STUN/TURN. Deliverables: working code, one README with exact setup commands per OS, the macOS Screen Recording and Accessibility permissions steps, and a coturn config snippet I can drop on a VPS. ## Required capabilities - Node 20 on every machine you want to control - ffmpeg installed on each host - A cheap always-on VPS for signaling and a coturn TURN server - Screen Recording and Accessibility permissions on macOS, or an X11/Wayland session that allows input injection on Linux - A domain with TLS, because getUserMedia and secure contexts will fight you otherwise ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of TeamViewer. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # TeamViewer indie build ## Goal Build the smallest trustworthy replacement for the core TeamViewer workflow for one developer or a tiny team. ## Scope A host agent on each of your machines streams its screen over WebRTC to a password-protected browser viewer that injects your mouse and keyboard events back. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Connections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure - Native clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support - The support workflow: a one-click download and a session code a non-technical person can read to you over the phone - Unattended access extras: wake on LAN, reboot and reconnect, multi-monitor switching, file transfer, session recording, printing - Commercial licensing, audit logs, and the corporate compliance story that makes IT allow it at all If those capabilities are essential, use TeamViewer instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a self-hosted personal remote desktop system: a host agent I run on machines I own, and a browser viewer I open to control them. Stack, no substitutions: - Node 20 + TypeScript for both host agent and signaling server. - WebRTC via the werift library on the host side, plain browser WebRTC on the viewer side. - ffmpeg (spawned as a child process) for screen capture and H.264 encoding. - @nut-tree-fork/nut-js for mouse and keyboard injection on the host. - Signaling over WebSocket (ws), single small server, no framework. - Viewer is one static HTML file with vanilla JS and a canvas/video element. No React, no build step for the viewer. Structure: - /signal: WebSocket signaling server. Hosts register with an ID and a shared secret from .env. Viewers authenticate with the same secret, then get relayed SDP and ICE. - /host: the agent. Captures the primary display with ffmpeg (avfoundation on macOS, gdigrab on Windows, x11grab on Linux), pipes encoded video into a WebRTC track, opens a data channel, and applies incoming input events with nut-js. - /viewer: static page. Shows available hosts, connects, renders the video track, captures mouse move/down/up/wheel and keydown/keyup, normalizes coordinates to the remote resolution, sends them over the data channel. Rules: - All config in .env: SIGNAL_URL, SHARED_SECRET, HOST_ID, TURN_URL, TURN_USER, TURN_PASS. Ship .env.example. Never hardcode secrets. - No accounts, no database, no telemetry, no cloud services beyond the signaling server and TURN that I run. - Target 1080p at 25fps with a tunable bitrate and a keyframe interval short enough to recover fast. Prefer latency over quality. - Data channel messages are small JSON objects, unordered, unreliable for mouse moves and ordered/reliable for clicks and keys. - Include a --view-only flag on the host that ignores all input events. - Log connection state transitions clearly so I can tell whether ICE failed or the encoder died. Explicitly out of scope: file transfer, clipboard sync, multi-monitor selection, mobile clients, unattended wake, NAT traversal magic beyond standard STUN/TURN. Deliverables: working code, one README with exact setup commands per OS, the macOS Screen Recording and Accessibility permissions steps, and a coturn config snippet I can drop on a VPS. ## Required capabilities - Node 20 on every machine you want to control - ffmpeg installed on each host - A cheap always-on VPS for signaling and a coturn TURN server - Screen Recording and Accessibility permissions on macOS, or an X11/Wayland session that allows input injection on Linux - A domain with TLS, because getUserMedia and secure contexts will fight you otherwise ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of TeamViewer. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # TeamViewer product brief ## Problem If you only need to reach your own machines, most of TeamViewer's value is reproducible: screen capture, a WebRTC pipe, and synthetic mouse and keyboard events are all solved problems with libraries. An agent can wire that into a working host agent plus browser viewer in a weekend, and on your own LAN it will feel fine. What breaks is everything outside your control: connecting through hostile double NAT without your own TURN server, waking a sleeping box, keeping latency sane over mobile networks, and surviving OS permission prompts on macOS after every update. It also stops being a support tool, because the whole point of TeamViewer for helping your parents is that they can install one thing and read you a nine digit number. Build it for your own boxes, keep paying if you support other people's. ## Product outcome A host agent on each of your machines streams its screen over WebRTC to a password-protected browser viewer that injects your mouse and keyboard events back. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 on every machine you want to control - ffmpeg installed on each host - A cheap always-on VPS for signaling and a coturn TURN server - Screen Recording and Accessibility permissions on macOS, or an X11/Wayland session that allows input injection on Linux - A domain with TLS, because getUserMedia and secure contexts will fight you otherwise ## Explicit non-goals for v1 - Connections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure - Native clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support - The support workflow: a one-click download and a session code a non-technical person can read to you over the phone - Unattended access extras: wake on LAN, reboot and reconnect, multi-monitor switching, file transfer, session recording, printing - Commercial licensing, audit logs, and the corporate compliance story that makes IT allow it at all ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a self-hosted personal remote desktop system: a host agent I run on machines I own, and a browser viewer I open to control them. Stack, no substitutions: - Node 20 + TypeScript for both host agent and signaling server. - WebRTC via the werift library on the host side, plain browser WebRTC on the viewer side. - ffmpeg (spawned as a child process) for screen capture and H.264 encoding. - @nut-tree-fork/nut-js for mouse and keyboard injection on the host. - Signaling over WebSocket (ws), single small server, no framework. - Viewer is one static HTML file with vanilla JS and a canvas/video element. No React, no build step for the viewer. Structure: - /signal: WebSocket signaling server. Hosts register with an ID and a shared secret from .env. Viewers authenticate with the same secret, then get relayed SDP and ICE. - /host: the agent. Captures the primary display with ffmpeg (avfoundation on macOS, gdigrab on Windows, x11grab on Linux), pipes encoded video into a WebRTC track, opens a data channel, and applies incoming input events with nut-js. - /viewer: static page. Shows available hosts, connects, renders the video track, captures mouse move/down/up/wheel and keydown/keyup, normalizes coordinates to the remote resolution, sends them over the data channel. Rules: - All config in .env: SIGNAL_URL, SHARED_SECRET, HOST_ID, TURN_URL, TURN_USER, TURN_PASS. Ship .env.example. Never hardcode secrets. - No accounts, no database, no telemetry, no cloud services beyond the signaling server and TURN that I run. - Target 1080p at 25fps with a tunable bitrate and a keyframe interval short enough to recover fast. Prefer latency over quality. - Data channel messages are small JSON objects, unordered, unreliable for mouse moves and ordered/reliable for clicks and keys. - Include a --view-only flag on the host that ignores all input events. - Log connection state transitions clearly so I can tell whether ICE failed or the encoder died. Explicitly out of scope: file transfer, clipboard sync, multi-monitor selection, mobile clients, unattended wake, NAT traversal magic beyond standard STUN/TURN. Deliverables: working code, one README with exact setup commands per OS, the macOS Screen Recording and Accessibility permissions steps, and a coturn config snippet I can drop on a VPS. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted TeamViewer capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# TeamViewer indie build ## Goal Build the smallest trustworthy replacement for the core TeamViewer workflow for one developer or a tiny team. ## Scope A host agent on each of your machines streams its screen over WebRTC to a password-protected browser viewer that injects your mouse and keyboard events back. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Connections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure - Native clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support - The support workflow: a one-click download and a session code a non-technical person can read to you over the phone - Unattended access extras: wake on LAN, reboot and reconnect, multi-monitor switching, file transfer, session recording, printing - Commercial licensing, audit logs, and the corporate compliance story that makes IT allow it at all If those capabilities are essential, use TeamViewer instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a self-hosted personal remote desktop system: a host agent I run on machines I own, and a browser viewer I open to control them. Stack, no substitutions: - Node 20 + TypeScript for both host agent and signaling server. - WebRTC via the werift library on the host side, plain browser WebRTC on the viewer side. - ffmpeg (spawned as a child process) for screen capture and H.264 encoding. - @nut-tree-fork/nut-js for mouse and keyboard injection on the host. - Signaling over WebSocket (ws), single small server, no framework. - Viewer is one static HTML file with vanilla JS and a canvas/video element. No React, no build step for the viewer. Structure: - /signal: WebSocket signaling server. Hosts register with an ID and a shared secret from .env. Viewers authenticate with the same secret, then get relayed SDP and ICE. - /host: the agent. Captures the primary display with ffmpeg (avfoundation on macOS, gdigrab on Windows, x11grab on Linux), pipes encoded video into a WebRTC track, opens a data channel, and applies incoming input events with nut-js. - /viewer: static page. Shows available hosts, connects, renders the video track, captures mouse move/down/up/wheel and keydown/keyup, normalizes coordinates to the remote resolution, sends them over the data channel. Rules: - All config in .env: SIGNAL_URL, SHARED_SECRET, HOST_ID, TURN_URL, TURN_USER, TURN_PASS. Ship .env.example. Never hardcode secrets. - No accounts, no database, no telemetry, no cloud services beyond the signaling server and TURN that I run. - Target 1080p at 25fps with a tunable bitrate and a keyframe interval short enough to recover fast. Prefer latency over quality. - Data channel messages are small JSON objects, unordered, unreliable for mouse moves and ordered/reliable for clicks and keys. - Include a --view-only flag on the host that ignores all input events. - Log connection state transitions clearly so I can tell whether ICE failed or the encoder died. Explicitly out of scope: file transfer, clipboard sync, multi-monitor selection, mobile clients, unattended wake, NAT traversal magic beyond standard STUN/TURN. Deliverables: working code, one README with exact setup commands per OS, the macOS Screen Recording and Accessibility permissions steps, and a coturn config snippet I can drop on a VPS. ## Required capabilities - Node 20 on every machine you want to control - ffmpeg installed on each host - A cheap always-on VPS for signaling and a coturn TURN server - Screen Recording and Accessibility permissions on macOS, or an X11/Wayland session that allows input injection on Linux - A domain with TLS, because getUserMedia and secure contexts will fight you otherwise ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# TeamViewer product brief ## Problem If you only need to reach your own machines, most of TeamViewer's value is reproducible: screen capture, a WebRTC pipe, and synthetic mouse and keyboard events are all solved problems with libraries. An agent can wire that into a working host agent plus browser viewer in a weekend, and on your own LAN it will feel fine. What breaks is everything outside your control: connecting through hostile double NAT without your own TURN server, waking a sleeping box, keeping latency sane over mobile networks, and surviving OS permission prompts on macOS after every update. It also stops being a support tool, because the whole point of TeamViewer for helping your parents is that they can install one thing and read you a nine digit number. Build it for your own boxes, keep paying if you support other people's. ## Product outcome A host agent on each of your machines streams its screen over WebRTC to a password-protected browser viewer that injects your mouse and keyboard events back. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 on every machine you want to control - ffmpeg installed on each host - A cheap always-on VPS for signaling and a coturn TURN server - Screen Recording and Accessibility permissions on macOS, or an X11/Wayland session that allows input injection on Linux - A domain with TLS, because getUserMedia and secure contexts will fight you otherwise ## Explicit non-goals for v1 - Connections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure - Native clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support - The support workflow: a one-click download and a session code a non-technical person can read to you over the phone - Unattended access extras: wake on LAN, reboot and reconnect, multi-monitor switching, file transfer, session recording, printing - Commercial licensing, audit logs, and the corporate compliance story that makes IT allow it at all ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a self-hosted personal remote desktop system: a host agent I run on machines I own, and a browser viewer I open to control them. Stack, no substitutions: - Node 20 + TypeScript for both host agent and signaling server. - WebRTC via the werift library on the host side, plain browser WebRTC on the viewer side. - ffmpeg (spawned as a child process) for screen capture and H.264 encoding. - @nut-tree-fork/nut-js for mouse and keyboard injection on the host. - Signaling over WebSocket (ws), single small server, no framework. - Viewer is one static HTML file with vanilla JS and a canvas/video element. No React, no build step for the viewer. Structure: - /signal: WebSocket signaling server. Hosts register with an ID and a shared secret from .env. Viewers authenticate with the same secret, then get relayed SDP and ICE. - /host: the agent. Captures the primary display with ffmpeg (avfoundation on macOS, gdigrab on Windows, x11grab on Linux), pipes encoded video into a WebRTC track, opens a data channel, and applies incoming input events with nut-js. - /viewer: static page. Shows available hosts, connects, renders the video track, captures mouse move/down/up/wheel and keydown/keyup, normalizes coordinates to the remote resolution, sends them over the data channel. Rules: - All config in .env: SIGNAL_URL, SHARED_SECRET, HOST_ID, TURN_URL, TURN_USER, TURN_PASS. Ship .env.example. Never hardcode secrets. - No accounts, no database, no telemetry, no cloud services beyond the signaling server and TURN that I run. - Target 1080p at 25fps with a tunable bitrate and a keyframe interval short enough to recover fast. Prefer latency over quality. - Data channel messages are small JSON objects, unordered, unreliable for mouse moves and ordered/reliable for clicks and keys. - Include a --view-only flag on the host that ignores all input events. - Log connection state transitions clearly so I can tell whether ICE failed or the encoder died. Explicitly out of scope: file transfer, clipboard sync, multi-monitor selection, mobile clients, unattended wake, NAT traversal magic beyond standard STUN/TURN. Deliverables: working code, one README with exact setup commands per OS, the macOS Screen Recording and Accessibility permissions steps, and a coturn config snippet I can drop on a VPS. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted TeamViewer capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
Because remote access is only worth anything when it connects on the first try from a network you have never seen, to a machine you cannot physically touch, running an OS version you did not choose. TeamViewer sells that reliability plus the legal cover to use it at work. Personal self-hosted remote desktop is genuinely pleasant right up until you are in an airport and your TURN server is the thing that died.
xConnections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure
xNative clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support
xThe support workflow: a one-click download and a session code a non-technical person can read to you over the phone
xUnattended access extras: wake on LAN, reboot and reconnect, multi-monitor switching, file transfer, session recording, printing
xCommercial licensing, audit logs, and the corporate compliance story that makes IT allow it at all
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced TeamViewer ($24.9/mo) with one prompt"
Vibecode TeamViewer
Kinda. The core of TeamViewer is buildable in a weekend with the prompt on this page, but there are real gaps: Connections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure, Native clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support. Read the honest list above before committing.
How much does TeamViewer cost?
TeamViewer costs about $24.9/month (TeamViewer Remote Access, checked 2026-08-18), which is $298.79999999999995 per year.
What do I lose by replacing TeamViewer?
Honestly: Connections that just work through carrier grade NAT, corporate firewalls, and proxies without you operating relay infrastructure; Native clients for Windows, macOS, Linux, iOS, and Android, plus mobile device support; The support workflow: a one-click download and a session code a non-technical person can read to you over the phone; Unattended access extras: wake on LAN, reboot and reconnect, multi-monitor switching, file transfer, session recording, printing; Commercial licensing, audit logs, and the corporate compliance story that makes IT allow it at all. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to TeamViewer?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.