WorkByte (cloud)
=================================

The backend runs in the cloud, so there is nothing to install or configure here:

    https://api-ai.workbyte.in

WHAT RUNS WHERE
  Cloud   chat, projects, your account and your data       (https://api-ai.workbyte.in)
  HERE    the AI provider you choose, the sandbox that runs media/scripts, every
          build, and every file the agent writes

  Nothing you make is executed on someone else's computer, and generated files are
  served straight off this machine.

HOW TO RUN
  1. Unzip anywhere.
  2. Double-click  Start-WorkByte.bat
     First run prepares the local engine and sandbox - it takes a few minutes and
     needs WSL2. Later runs are quick.
  3. Sign in with Google.
  4. Add your AI provider when asked (see below).

YOU BRING THE AI
  WorkByte runs on YOUR AI provider, not ours. On first launch it asks you to add one:
  OpenAI, OpenRouter, Groq, Anthropic, Ollama, or any OpenAI-compatible endpoint.
  Your API key is encrypted before it is stored, and usage is billed to your own
  account - nothing routes through anyone else's. Until you add a provider, the app
  will tell you so instead of trying to answer.

  You can change it any time in  Settings -> LLM Provider.

YOUR CODE STAYS ON YOUR MACHINE
  WorkByteBridge.exe ships inside app\ and starts with the app. It is how the agent
  reads and writes files on THIS computer - your projects are never uploaded to run
  somewhere else. Grant Desktop Access in Settings or the bridge stays read-only.

WHAT'S INSIDE
  app\                 the WorkByte desktop app + WorkByteBridge.exe
  wb-engine.ps1        keeps the container engine (WSL2 + containerd) alive
  sandbox\             your own sandbox: image tar + k3s manifest + provisioning
  Start-WorkByte.bat   the launcher

REQUIREMENTS
  WSL2. Windows 10 2004+ and Windows 11 have it; wsl --install if not.
  Without it the local sandbox cannot start and you can switch to the shared cloud
  sandbox in Settings -> Sandbox, but then media and scripts run off-device.

WINDOWS FIREWALL
  You should not see a firewall prompt: the bridge listens on 127.0.0.1 only and
  dials out to the backend. If Windows does ask, allowing it on private networks is
  enough - it never needs a public-network rule.

TROUBLESHOOTING
  "No AI provider is set up yet"     -> Settings -> LLM Provider, add one.
  The agent cannot see your files    -> Settings -> grant Desktop Access.
  Everything fails to load           -> check https://api-ai.workbyte.in is reachable from this network.
  Generated images/video don't open  -> the local sandbox is not running:
                                        powershell -File sandbox\wb-local-sandbox.ps1 -Status
  Containers die after the machine idles -> the engine keepalive stopped:
                                        powershell -File wb-engine.ps1 -Status

Built: 2026-08-14 09:13
